Creating a Business Analysis Plan Flashcards
What are the 8 key components for an effective business analysis plan?
Roles and responsibilities Prioritization information Requirements traceability information Expected deliverables Technical Considerations Requirements communication plans Elicitation activity details Stakeholder analysis
What is the purpose of elicitation?
To draw our information from stakeholders to further understand the needs of the business, to address a problem or opportunity and the stakeholder’s preferences and conditions of the solution
What questions should you ask when planning elicitation?
How should we elicit information?
When, and from whom?
All elicitation activities…
Take time and money to perform // Sap the attention of limited resources
What should you consider when planning elicitation?
Often difficult for stakeholders to schedule availability on short notice
May need time for additional elicitation efforts, based on early results
Focus on rapid accumulation of information upfront can make structuring remaining elicitation easier
Where should you focus your elicitation efforts first?
Business Value
What are the other areas you should focus elicitation efforts?
Areas of risk
Technical hurdles
External dependencies
When should the methods for priotising requirements be in place?
Before elicitation
What are the features of a prioritization system?
Objectives, leads to equitable decision making and to greater stakeholder acceptance
What are the benefits of putting the methods for prioritisation before elicitation?
Everyone understands from the outset how objectives are going to be set
How some requirements won’t make the cut based on the objective system
Less likely to be upset if particular recommendations don’t make it
How often are requirement prioritised?
Varies by project life cycle
How can you prioritise requirements?
By Value Cost complexity Legal Considerations Risk
What is the purpose of traceability?
Documenting requirement relationships and is used in business analysis to maintain product scope
What are the steps for tracing requirements?
Requirement origin
Requirement implemented
Requirement test/verified
Requirement completed
What is the benefit of traceability?
Makes impact of potential changes easier to understand
