Requirements Life Cycle Management

This area revolves around managing all the tasks which are essential for the requirements such as planning, analyzing, managing etc. These tasks make sure that the business analysis information is up to date with the requirements and the solution or the end result is up to the mark.
The area includes the following tasks:

Trace Requirements - The goal of tracing is to ensure that requirements are connected to a business objective. In other words, traceability ensures that every requirement has a business purpose and that no requirement is superfluous.
Maintain Requirements - As a business analyst, you have to keep requirements up-to-date during and also after your required changes. This task makes sure that the changes are to be done are accurate and even if someone disagrees with the notion of the requirement it is acceptable for the actual change.
Prioritize Requirements - Not all requirements have the same priority – depending on the stakeholder and the benefits, you have to define the order in which the requirements should be implemented. The prioritization should be continuous to be able to react to changes. For example, the benefit, cost or risk might change over the course of the project.
Assess Requirement Changes - As a business analyst, you have to evaluate how the suggested changes will affect the requirements. This evaluation is only successful if new needs or solutions have been identified.
Approve Requirements - And then you have to accept or reject the requirements to continue processing the solution. This can occur formally or informally.

Comments

The Brown Cow Model

This model of work has four views of work which are What, Now, How and Future. The two horizontal and the vertical axes separate What from How, and Now from the Future. The Brown Cow Model illustrates four points of view that help to uncover the real business problem and identify useful innovations. The four quadrants which are - What-Now, What-Future, How-Now, and How-Future show the different viewpoints of work. Generally, it is not sufficient to have only two views of business - the "as is" and the "to be". To get a true light on the business problem and to ensure innovations, more views are necessary. Aziz

The Brown Cow Model in Agile

There are reports stating, “agile does not help in innovation”. As there is a pressure to develop anything, they can produce within the time allowed. The greatest pressure is for maintaining the speed of the project, not for its innovative solutions. When we talk about innovation it means new thinking. We do not mean that innovation is invention. Innovation is different thinking about the business problem with the intention of finding beneficial solutions. User stories that are not based on real business stories will always have a hard time being innovative. Without some innovative thinking, it is very easy to propose only that you increment something and let it go through it. When a BA investigates a business history, this professional needs to be purposely trying to encourage innovation. The Brown Cow Model illustrates the ability to analyze the same business history from several different points of view. From there, innovations are discovered t

Usability Requirements

Usability Requirements Ease of Use Requirements: This requirement deals with the aspect to make the product usable for the user. The product should have the following properties for the ease of use Efficiency of Use Ease of remembering Overall satisfaction Feedback Personalization and Internationizational Requirements: These requirements deal with the way the product can be changed or advanced related to the user's choices or preferences. The product could have the following personalized requirements: Language or spelling preferences Currency choices Personal Configuration options Learning Requirements: These consider how easy it is to learn to use the product or the service. These requirements may differ on the level of technology or any advancement involved in the product. Some services also require for the engineers or the user to train in a specific program to be able to efficiently use the service or the product. Understandability and Politeness Requiremen

Introduction to Business Analysis (Group 4)

Search This Blog