The purpose of the Trips-R-You Flight Booking Case Study is to provide an integrated, end-to-end set of requirement examples. In IIBA® BABOK® V3 terminology, end-to-end means from Business Requirements to Stakeholder Requirements to Solution and Transition Requirements. This case study, and associated artefacts, use the more traditional business terms Goals, High-level Requirements (HLRs), and Detail Requirements. Only functional requirements are addressed, and only within the context of a project chartered to deliver an IT-based solution.

Let us look at it from a different angle now and derive the requirements out of the customer journeys.  It is impossible to introduce a change... if the change is big and you try to implement it in one go.  This is the reason we tend to break any solution into smaller components. Each solution component should be small and independent enough to be changed individually in a controlled manner. So that eventually we will compose a new experience out of them. Pretty much like using a set of Lego blocks.

The question of how essential domain expertise is to a business analyst is a recurring debate in the BA community. One school of thought maintains that domain knowledge is not critical. A skilled BA, the thinking goes, can walk into nearly any project situation and do an effective job of exploring requirements, relying on previous experience and a rich tool kit of requirements techniques. The counterargument avers that an analyst who has deep subject matter knowledge can be far more effective than a more general practitioner.

I have experienced both situations, from inside a company as a regular employee and from the outside as a consultant. This article offers some thoughts about when domain knowledge is valuable, when it’s essential, when it’s not necessary, and when it can actually pose a risk.

Learning about mental models and how to apply them to their work is one of the best investments for business analysts interested in achieving the level of deep thinking that leads to better outcomes for their projects and organizations.

For the business, it means they not only need to understand the problem the customers are trying to solve - they need to understand that problem in a context and design a full end-to-end experience of solving it. Some people call this process “human-centered design”, some - just using common sense when designing stuff. 

Successful projects—and successful relationships—are based on realistic commitments, not on fantasies and empty promises. This article, adapted from the book Practical Project Initiation, presents several ways to improve your ability to make, and keep, achievable commitments... Unfulfilled promises ultimately lead to unhappy people and unsuccessful projects. Strive to build a realistic commitment ethic in your team—and in yourself.

Are you a Business Analyst (BA) wondering what User Experience (UX) Design is all about and how your involvement in a design project is likely to impact your usual role? If so, I’ve also been pondering the same question for some time.

The reason why top performing business analysts tend to be so effective in complex projects, even when their domain knowledge is limited, is because of their ability to see things from a higher angle and with more nuanced colors.

If someone said you could only perform a single quality practice on a software project, what would you choose? I’d pick peer reviews of requirements, which I believe are the highest-leverage quality practice we have available today.  In a peer review, someone other than the author of a work product examines the product for quality problems and improvement opportunities. Reviewing requirements is a powerful technique. Use them to identify ambiguous or unverifiable requirements, find requirements that aren’t sufficiently detailed yet, spot conflicts between requirements, and reveal numerous other problems.

As the business analyst (BA) role continues to evolve, the responsibilities continue to expand. One of the best ways for a business analyst to add value to a project is to understand the processes involved in both the project life cycle (PLC) and the software development life cycle (SDLC). Contrary to popular belief, the two life cycles are independent of one another, however, it's best that they are aligned.

The fact that software projects and tasks are reported to be “90 percent done” for a long time has become something of an industry joke. (A related joke states that the first half of a software project consumes the first 90 percent of the resources, and the second half consumes the other 90 percent of the resources.) This well-intentioned but misleading status tracking makes it difficult to judge when a body of work will truly be completed so you can ship the next product release to your customers. Here are several typical causes of “90 percent done” syndrome and a few possible cures.

 

Many professionals approach us after being unsuccessful in CBAP so we thought of doing some analysis to come up with the most common reasons of failure in CBAP.

There are many articles and blogs giving tips on how to pass the CBAP exam but on a first search, I didn't find any article explaining why people fail in CBAP. This will definitely help the CBAP aspirants to make sure that they don't repeat the mistakes.

Reuse is an eternal grail for those who seek increased software productivity. Reusing requirements can increase productivity, improve quality, and lead to greater consistency between related systems.

Reuse is not free, though. It presents its own risks, both with regard to reusing existing items and to creating items with good reuse potential. It might take more effort to create high-quality reusable requirements than to write requirements you intend to use only on the current project. In this article we describe some approaches an organization could take to maximize the reuse potential of its requirements.

The objective of this article is to provide business analysts with guidelines for distinguishing between high-level requirements (HLRs) and detail requirements (in IIBA® BABOK® V3 terms – Stakeholder requirements and Solution requirements respectively).

Unfortunately, business rules often are a mystery in business. Most of time they are undocumented and worst they are a figment of someone’s imagination - no basis. However, mystery or not, we need them in eliciting stakeholder requirements in order to understand how the business obligations are kept, constraints are enforced and how decisions are made. And just like news reporters, we need to confirm the business rules with a second (hopefully authoritative and documented) source. Furthermore we need business rules to ensure a quality product and/or process through testing.