5: EA - Enterprise Analysis Flashcards
How business need can be generated?
New business needs can be generated in several different ways:
- From the top down - the need to achieve a strategic goal
- From the bottom up - a problem with the current state of a process, function or system
- From middle management - a manager needs additional information to make sound decisions or must perform additional functions to meet business objectives
- From external drivers - driven by customer demand or business competition in the marketplace
What is the acronym for Enterprise Analysis
Need Gapshirt And Suit Case N = Define Business Need G = Assess Capability Gaps A = Define Solution Approach S = Define Solution Scope C = Define Business Case
What state of Requirement is the input for Define Business Need?
Requirement [Stated]
What are the elements of Define Business Need?
- Business Goals and Objectives
- Business Problem or Opportunity
- Desired Outcome
How to assess the objective, as describe din Define Business Need task of Enterprise Analysis?
Assessing objectives that they are SMART.
S = Specific M = Measurable A = Achievable R = Relevant T = Time-bounded
What are the element of Assess Capability Gaps?
- Current Capability Analysis
- Assessment of New Capability Requirements
- Assumptions
What are the element of Determine Solution Approach?
- Alternative Generation
- Assumptions and constraints
- Ranking and Selection of approaches
What is the special technique for Determine Solution Approach task?
Feasibility Analysis
What is formal Feasibility analysis? and when it is used?
Formal Feasibility analysis is special techniques used during Determine Solution Approach task.
Formal feasibility studies use reliable data and apply statistics and market research to identify and analyze potential solution options.
Which Stakeholder is responsible to assess feasibility of solution approaches?
Implementation SME will be needed to assess the feasibility of possible approaches.
What are the element of Determine Solution Scope task?
- Solution Scope Definition
- Implementation Approach
- Dependencies
What is the special technique used for Determine Solution ScopeTask?
Problem or Vision statement
What does Problem or Vision statement states?
A problem or vision statement states the business need, identifies key stakeholders, and briefly describes the positive impact that meeting the business need will have on those stakeholders.
Which Stakeholder is responsible for definition of the project scope?
Project Manager
Project Manager assist with the development of the overall solution scope, which will be used as an input into the Project Charter.
What does project scope constitute?
Defines what must be delivered in order to meet the business need, and the effect of the proposed change initiative on the business and technology operations and infrastructure.
What are the elements of Define Business Case?
- Benefits
- Costs
- Risk Assessment
- Results Measurement
What are different types of Risk should be considered while Defining Business case for Enterprise Analysis KA?
The risk assessment should consider
1. Technical risks
(whether the chosen technology and
suppliers can deliver the required functionality),
2. Financial risks
(whether costs may exceed levels that make the
solution viable or potential benefits may disappear)
3. Business change and organizational risks
(whether the organization will make the changes
necessary to benefit from the new solution).
How Business Case is useful for Project Manager?
The project manager will use the business case as an input for a project charter.
What does a Business case consist of ?
Business Case presents the information necessary to support a go/no go decision to invest and move forward with a proposed project.
How the Define solution scope (task) and implementation approach (element) is different from Allocate Requirements (7.2)?
Define solution scope (task) and implementation approach (element) describes how business requirements are allocated for implementation by a project.
See Allocate Requirements (7.2) for a discussion of how stakeholder and solution requirements are allocated to solution components and releases.
