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

5757 Views
2 Likes
1 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. 

10491 Views
11 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
6141 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
7282 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
6470 Views
4 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
4910 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
5704 Views
20 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
7969 Views
5 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.

Apr 04, 2016
6117 Views
23 Likes
0 Comments
Do we “on board” new project team members? In today’s busy organizations individuals are shuffled around all the time being assigned and unassigned almost daily to projects. We employ the “sink or swim” mentality. New person it’s your job to figure it out and get it done.
Mar 27, 2016
7432 Views
6 Likes
0 Comments
Many skilled individuals do ask themselves: “How can I be sure, that I am doing well?” Especially in the business analysis sphere, the criteria of a quality job may be vague or only partly relevant.

In reality, what many people do is try to measure the quality of business analysis work through analyzing some aspects of BA artifacts they produce.
Mar 20, 2016
4900 Views
3 Likes
0 Comments
This article attempts to explore a theoretical interpretation of “User Experience”. It will explore the meaning of ‘User Experience’ itself by focusing on the user, the technology and the resulting experience from the two interacting with each other. It will define some user experience roles relating to associated professions, and also attempt to describe the single important dynamic of user experience.
Mar 13, 2016
8042 Views
16 Likes
0 Comments
You finally did it. You figured out the real business problem your project is meant to solve, and identified a solution that is far superior than the originally proposed. Now you just need to get buy-in from the project sponsor so the delivery team can alter their plans and set out to build the higher-value solution you devised. But there is one problem: the project sponsor was deeply involved in identifying the original solution and nurturing it. It’s his baby… and if you say it needs to be overhauled, you are basically saying his baby is ugly. Now what? How do you make sure your news aren’t received as an insult, and dismissed with defensiveness by the decision-maker?
Mar 06, 2016
7201 Views
9 Likes
2 Comments
Discovery of real needs is the responsibility of the business analyst. Choosing the optimal solution is usually the responsibility of the stakeholders. Working together, both parties can ensure that they are providing the maximum business value.
Feb 28, 2016
7879 Views
19 Likes
2 Comments
Requirements are inputs to achieve the project objectives that transcend from routine operations to enhance the value proposition of a business endeavour. Stakeholders invariably perceive an endeavour to be successful only if they are able to clearly correlate the derived outcome to predefined business requirements. Thus project success is best defined in terms of effective user requirements.
Feb 25, 2016
6388 Views
4 Likes
0 Comments
While others are moving forward introducing new banking products, the Americans find themselves in the role of constantly fighting fires. You cannot move forward until you put your house in order by bringing standard practices and discipline into your work effort. This is what happens when you treat system design as an art form, as opposed to a science.
Page 6 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