Business Analysis Articles

Aug 13, 2017
1312 Views
0 Comments
Business analysis is a broad discipline and we have a whole range of tools and techniques at our disposal. We may get involved within projects, but also outside of them. Many BA teams are actively seeking earlier engagement—when we are engaged prior to a project being initiated we can work wit...
Business analysis is a broad discipline and we have a whole range of tools and techniques at our disposal. We may get involved within projects, but also outside of them. Many BA te...
Scope creep (also known as feature creep, requirements creep, featuritis, and creeping featurism), however, refers to the uncontrolled growth of functionality that the team attempt...
Disbenefits are changes to on-going operating costs as a result of a project; they could be perceived as positive or negative. These disbenefits are included in defining the Total ...

Latest Articles

Jul 27, 2016
6275 Views
30 Likes
0 Comments
Opportunities abound for new and experienced analysts to advance their careers if they are willing to increase their knowledge of analytics, metrics, and Business Intelligence. In the meantime, following these five steps will help get you and your organization on your way to being a well-measured one.
Jul 24, 2016
15050 Views
51 Likes
0 Comments
Business analysts’ performance and how we could measure it appeared to be a hot topic of interest for the Business Analysis community.   “If you can’t measure it, you can’t manage it” (Peter Drucker) – this statement hides lots of questions for the Business Analysis managers, like what to measure, how to assess, quantifiable or qualifiable metrics to use? 
8169 Views
46 Likes
0 Comments
Often I come across situations where a BA is unprepared or under-prepared in approaching the requirements elicitation process. This leads to irritated business users, incomplete requirements, significant delays, reworks, and poor opinion about BA's in general. I decided to put together a list of prerequisites that a BA must complete before commencing requirements elicitation process.
Jul 13, 2016
6530 Views
2 Likes
0 Comments
Once requirements analysis is completed, Business Analyst has all the information needed for a well-running function. Further actions for design, development, test and eventually roll-out are conduct accordingly. Usually and unfortunately, because of the rush of ongoing project execution no one thinks about the roll out activities until the end of the project plan and when the PM starts to drill down the roll out plan in details, project team face with the big nasty surprise of new requirements necessary for the selected software changeover (a.k.a. software adoption) strategy. Cost increase, delays, unmet deadlines create the nightmare one by one.  
Jul 10, 2016
9046 Views
15 Likes
1 Comments
Many organizations in the last year moved to Agile and eliminated the business analyst role. With the migration to the cloud the role of the business analyst is still being questioned. If you want to know what a business analyst can offer in this fast changing IT world as you migrate to the cloud; here are the answers
Jul 04, 2016
18775 Views
148 Likes
6 Comments

With the rise in popularity of agile methods, business analysts and product owners often use the term “agile requirements” to label their work.  We do not care for the term “agile requirements” because it implies that the requirements for an agile project are somehow qualitatively different from those for projects following other life cycles. A developer needs to know the same information to be able to correctly implement the right functionality regardless of the life cycle being used.

Jun 29, 2016
5809 Views
8 Likes
0 Comments
I have had the opportunity in my career to move, not only, from industry to industry, but from company to company. I have been a consultant as well as a full time employee throughout my career. As companies merge and/or begin to grow talent is needed and could come from anywhere. New/outside talent can bring in fresh wave of diverse perspectives and ideas. However, there should be some caution taken, if you are that new person entering into the organization. Whether you are a consultant, temporary employee or full time employee, here are 5 pitfalls that I have found in my career that can either make you or break you as you enter into new companies.
Jun 26, 2016
4215 Views
2 Likes
1 Comments

The Business Analyst is in a great position to constantly focus on the desirability of the product.  A well-defined requirement elicitation process must be focused on defining the problem the business is trying to solve for our customers. If defining the problem is the first step in your requirement process you are on the way to guaranteeing that the delivered product will provide value to your customers. Throughout the development process you will be able to monitor if the product is actually solving the problem. Additionally, your requirements should be directly related to solving the problem. It is a BA’s job to question the value of every proposed requirement that product owners want to add. If the requested feature or function is not directly related to solving the problem then it should be taken out of scope. 

Jun 19, 2016
8103 Views
49 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
12252 Views
44 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
9792 Views
12 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
6674 Views
13 Likes
1 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
5342 Views
2 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
8502 Views
6 Likes
4 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
7089 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.
Page 5 of 60First   Previous   1  2  3  4  [5]  6  7  8  9  10  Next   Last   





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