Chapter 6 - Strategy Analysis

Chapter 6 - Strategy Analysis 


Analyzing current state include: Purpose is 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 should include business needs, organizational structure  and culture, capabilities and processes, technology and infrastructure, polices, business architecture, internal assets, external influences.

Future State: Future State describes the purpose to determine the set of necessary conditions to meet the business need. Basic elements of future state are  business goals and objective, Scope of solution space, constraints, organizational structure and culture, capabilities and processes, technology and infrastructure, polices, business  architecture, internal assets, identify assumptions, potential value.

Assessing Risk: Assessing risk includes purpose to understand the undesirable consequences of internal and external forces on the enterprise during a transition to, or once in, the future state.

Change Strategy: Change strategy is undertaken to develop and assess alternative approaches to the change, and then select the recommended approach.

Chapter 4 - Elicitation and Collaboration

Chapter 4 - Elicitation and Collaboration

4.1 Purpose for Elicitation: Understand the scope of elicitation, select appropriate techniques and planning supporting resources 

4.2 Purposes for conducting Elicitation: Draw out, explore and identify information relevant to change

4.3 Purpose to confirm the results: Check the accuracy and consistency of the information gathered during the session.

• Business analysts must communicate appropriate information to stakeholders at the right time and in formats that meet their needs. Consideration is given to expressing the information in language, tone, and style that is appropriate to the audience. Communicating information does not simply involve pushing information out and assuming it was received and understood. Business analysts engage stakeholder to ensure they understand the information and gain agreement.

• Stakeholders Collaboration: Lends to many collaboration opportunities between groups of stakeholders on the business analysis work products. Stakeholders hold various degrees of influence and authority over the approval of work products, and are also an important source of needs, constraints, and assumptions.

Chapter 5: Requirements Life Cycle Management

Chapter 5:  Requirements Life Cycle Management

Requirements Life Cycle Management describes the tasks that business analysts perform in order to manage and maintain requirements and design information from inception to retirement.  It involves a level of control over requirements and over how requirements will be implemented in the actual solution to be constructed and delivered. It also helps to ensure that business analysis information is available for future use. 

The Requirements Life Cycle Management knowledge area includes the following tasks: 

• Trace Requirements: analyzes and maintains the relationships between requirements, designs, solution components, and other work products for impact analysis, coverage, and allocation. 

• Maintain Requirements: ensures that requirements and designs are accurate and current throughout the life cycle and facilitates reuse where appropriate. 

• Prioritize Requirements: assesses the value, urgency, and risks associated with particular requirements and designs to ensure that analysis and/or delivery work is done on the most important ones at any given time. 

• Assess Requirements Changes: evaluates new and changing stakeholder requirements to determine if they need to be acted on within the scope of a change. 

• Approve Requirements: works with stakeholders involved in the governance process to reach approval and agreement on requirements and designs.