Posts

Chapter 3 - Scoping the Business Problem - posted by Paramjeet Kaur Toor

 Setting the Scope We have to understand business process and aim of organization to make a scope. we need to find what our owner is doing and how our product will benefit them. There are different parts of business that we should understand like "the Work" that define precise scope of work and parts of organization that are included in work. In addition, there is scope for owner's work that involve work that owner want to change or improve. Stakeholders Stakeholders are those who are interest in and affected by the output or result of project. Therefore, a single project involve many stakeholders to complete a project. For example sponsor, customer, suppliers, consultants, manager, opponents etc. Some of important stakeholder discussed below: The Sponsor: A sponsor is a person who represents owner's interest to other stakeholder and provide budget for developing the resources of project. It means sponsor pays for development of product. a project can not go ...

Chapter 2 – The Requirements Process - Posted by Liliane Castano Marino

Image
According to chapter 2 of the Mastering the requirements process book, the first step of the Volere requirements process is the Project Blastoff.  It might last a few hours or several days it all depends on the size of the project and the amount of uncertainty. Key Purpose – The key purpose of the project blastoff is to build the foundation for the requirements discovery and ensure that all the needed components for a successful project are in place.   It identifies the purpose of the result the project is trying to achieve and the stakeholders. Main deliverables: 1)      Purpose of the project The blastoff group confirms the goals of the project. In order to determine where to start the requirements gathering, the BA must understand what the project is trying to achieve. 2)      Project Scope The scope must be set and understood by the project team. Identifies boundaries on what part of the business to s...

Chapter -1 from book Mastering The Requirements Process

Image
  Some Fundamental Truths                                                                                              post by Paramjeet Kaur Toor Some Fundamental Truths are: 1. Requirements are not really about requirements Requirements are what you are going to build that can be software, hardware or any service so these are developed to be confirm about our specific output. Therefore, requirements activity is not just write them on paper but focus on problem and finding its solution is most important. 2. If we must build software, then it must be optimally valuable for its owner. It our primary job to meet the product/service' s qualities to owner's expectation who is paying for it. Therefore, people must know ...

Chapter 6: Strategy Analysis

Image
posted by Liliane Castano Marino According to chapter 6 of the BABOK,   t he Strategy Analysis knowledge area describes the work that must be executed to describe the tasks used to identify the business need, address that need, and align the change strategy within the enterprise. The Strategy Analysis knowledge area is composed of the following tasks: 1)        Analyze Current State At this point, it is important to understand the reasons why an enterprise needs to change some aspect of how it operates and what would be directly or indirectly affected by the change.   It is also important to set a baseline and context for the change. 2)      Define Future State The purpose of defining future state is to determine the set of necessary conditions to meet the business need and define what parts of the enterprise need to change in order to meet the goals and objectives set. 3)      As...

Chapter 4: Elicitation and Collaboration

Image
posted by Liliane Castano Marino According to chapter 4 of the BABOK,   t he Elicitation and Collaboration knowledge area describes the work of business analysts to understand stakeholder needs, concerns and the environments in which they work or operate.   In this area of knowledge, the business analysts extracts the information necessary to assertively understand the change and what really needs to be done.   It is an ongoing work as long as business analysis work is occurring. The Elicitation and Collaboration knowledge area is composed of the following tasks: 1)        Prepare for Elicitation At this point, it is important to establish what information will be needed, which stakeholders will be involved, which work products will be produced and which techniques will be most appropriated to reach the required results. The professional who does business analysis needs to go far beyond interviews and questionnaires. BABOK points...

Requirements life cycle management

Tasks of requirements life cycle management: post by Paramjeet Kaur Toor 1.Trace Requirements:  Trace requirements are for ensuring that requirements and designs of different stages are aligned to one another and for managing the effects of change. Trace requirements traces each requirements. These requirements enables:  faster and easier  analysis of any impact  more reliable discovery of inconsistencies and gaps in requirements  deeper understanding into the scope   reliable assessment of which requirements have been addressed and which have not. Guideline and tools:  These tools provide good benefits when there is large number of requirements to trace.  Domain Knowledge : for supporting traceability of requirements, business domain knowledge is much important. Information Management Approach : provides decisions from planning activities concerning the traceability approach. Legal/Regulatory Information : describes rules ...

Chapter 3: Business Analyst Planning and Monitoring By, Hassan Kamara

Image
Business Analysis Planning and Monitoring According to chapter 3 of the BABOK, the tasks of business analysis planning and monitoring are presented to coordinate the efforts of stakeholders and BA’s. The 5 main knowledge areas that will be covered are: Ø   Plan business analysis approach Ø   Plan stakeholder engagement Ø   Plan business governance Ø   Plan business analysis information management Ø   And identify business analysis performance improvements 1.       Plan business analysis approach. Plan business analysis approach can be defined to be the planning of business analysis work from selection or creation of a methodology to planning the individual tasks, activities and deliverables. BA’s also identify initial techniques that could be applied. The approach is used to define a method to conduct the business analysis activities. The approach should; align to the goals of he change, coor...