Jun 19, 2016
2264 Views
2 Likes
0 Comments
A bid is like a product that, once designed, the team must be able to deliver it. This delivery includes manufacturing the product, testing it, preparing the marketing for the product launch and finally launch it.  We propose a staged approach that replace guessing a number with qualitative investigation. The model suggested, distilled from experience, shows how estimates are transformed into effort and, ultimately, into a coherent story with a price tag attached.
Jun 12, 2016
4936 Views
7 Likes
0 Comments
Sequential Development is the traditional approach that allows the business analyst to perform business analysis during the initial phases of a business process. The novelty brought by Agile was that it challenged practitioners to perform business analysis throughout the entire development process. This is a fundamental difference between Agile and Sequential Development because Agile recommends the continual re-evaluation of the initial business analysis. The present article will discuss business analysis in Agile by focusing on Scrum implementation.
Jun 08, 2016
3673 Views
11 Likes
1 Comments
Since when were Business Analysts a one stop shop for all project needs? We are expected to be Superheros; well-rounded BAs as well as Change Managers, Test Analysts, Project Managers and Implementation Managers. The boundaries of these other disciplines is often unclear so this article seeks to explore the activities that fall into business analysis and those that should be undertaken within the other disciplines.
Jun 05, 2016
2927 Views
11 Likes
0 Comments

To be a great analyst, you’ll need to ask great questions. In order to ask great questions, you’ll need to remain inquisitive.  Fact of the matter is, that if you are performing any kind of analysis, you need to become very comfortable with asking difficult questions. Questions that make people uncomfortable and questions that might even potentially expose unpopular answers.

May 30, 2016
2062 Views
1 Likes
0 Comments
If you are looking for a specific decision to be made on a specific issue or capability, then getting the meeting down to a small core team is important in order to ensure the decision is being made quickly. This is where Minimally Viable People comes into the picture. Minimally Viable People is the concept that a small group performs better by making decisions with higher quality while being representative of the larger group.
May 23, 2016
3845 Views
6 Likes
2 Comments
So you’ve developed a set of requirements for some portion of your next systems development project. Now what? Experienced project managers and software developers understand the value of translating requirements into rational project plans and robust designs. These steps are necessary whether the next release represents 1 percent or 100 percent of the final product. As shown in Figure 1, requirements serve as the foundation for project plans, designs, code, and tests. In addition to these connections, there is a link between the requirements for the software to be built and other project and transition requirements. Those include data migrations, training design and delivery, business process and organizational changes, infrastructure modifications, and others.
May 18, 2016
3135 Views
8 Likes
0 Comments
I’ve been a Business Analyst for about 15 years now starting as a graduate back in the day. And while I do not consider that to be close to a career’s worth of experience I have certainly seen significant changes in the way business analysis is performed and the tools that are used thanks to the evolution of technology.
2719 Views
2 Likes
0 Comments

This article covers a trend in the industry that has been yielding great results for companies looking to deliver more successful projects. By cutting down on huge initiatives with outrageous requirements documents that just can't be managed and focusing on implementing features and functionality a piece at a time, companies can be sure to deliver more value to customers more often. 

3589 Views
9 Likes
0 Comments
Every software team talks about project scope and team members often complain about unending scope creep. Unfortunately, the software industry lacks uniform definitions of these terms, and the requirements literature is short on clear guidance regarding how to even represent scope. I confront scope head-on in this series of three articles...
May 01, 2016
2127 Views
4 Likes
0 Comments
Bias is seen in action through bad decisions, miscommunication, perceptual blindness, and alienation of groups with diverse thought. Here’s what the dictionary says about bias: “A preference or an inclination, especially one that inhibits impartial judgment.”
Apr 24, 2016
3694 Views
10 Likes
0 Comments
It is common for projects to be initiated based on blueprints. However, a blueprint is just a guide to the future state. Its intended purpose is to guide the subsequent analysis and design activities. It does not answer all the questions. The details of what, how, and why are left to requirements analysis.
Apr 20, 2016
2906 Views
3 Likes
0 Comments
It appears to me people still have trouble defining information requirements and, as such, they are at a loss as to how to build total systems. Thereby, they are content building either a single business process or a program. Therefore, here is the conceptual foundation for all system design. Information Driven Design begins with a simple concept...
Apr 18, 2016
1875 Views
5 Likes
0 Comments
Essentially, the IIBA® does not view “testing” as being part of the BA role. Obviously I disagree. When it comes to hours associated with test planning/strategies, the IIBA® should accept them as work experience in qualifying to sit for the CBAP® exam.
Apr 11, 2016
2931 Views
19 Likes
1 Comments

Being required to produce documents that create massive information bloat and don’t add value is frustrating as it slow projects down and creates additional project cost that isn’t needed. It’s a headache for Project Manager, Business Analyst and everyone on the team. What we need is the smallest set of information that can be verified and validated quickly that directly ensures the highest quality outcome of the project. 

Apr 06, 2016
3166 Views
3 Likes
1 Comments

Gathering and documenting requirements to develop software is often seen by business analysts as their core task. Actually, they are there to deliver value to the business—everything else is secondary.

Page 1 of 56First   Previous   [1]  2  3  4  5  6  7  8  9  10  Next   Last   




Latest Articles

Use Uncertainty to Win Business
Jun 19, 2016
0 Comments
A bid is like a product that, once designed, the team must be able to deliver it. This delivery includes manufacturing the product, testing it, prepar...

Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC