Requirements planning andLifecycle estimation

Question 1

Feasibility stage requirements gathering

Answer 1

1. TOR from pre-project
2. Themes and Epics develop
3. Clarify project vision

Question 2

Foundations requirements gathering

Answer 2

1. Bring together PRL sufficent to estimate timeboxes
2. Develop objectives and acceptance criteria
3. Emergence of plans that are practicable

Question 3

Requirements during time boxes

Answer 3

1. Small usuable subset of business functionality
2. Follow MoSCoW

Question 4

Estimating within DSDM

Answer 4

1. Need to be realistic
2. Precise and accurate as is necessary
3. People who do the work should do the estimating
4. Estimates should be revaildated throughout project
5. Contingency managed within MoSCow
6. Techniques - Planning Poker - Estimating Workshops
7. Agile BA to analyse and make visable the MoSCoW priorities

Question 5

PRL requirements

Answer 5

1. High level creation during feasability
2. Refined during Foundations
3. Persists through projects

Question 6

Elicitation (requirement lifecycle)

How to

Answer 6

1. Face to face convesation
2. Observation
3. Faciliated Workshops
4. Demonstrations of working elements of the solution
5. Scenarios
6. Modelling and prototyping

Question 7

Analysis (requirement lifecycle)

How to

Answer 7

1. Realistic
2. Unambiguous
3. Feasible
4. Congruent
5. Relevant

Question 8

Validation (requirement lifecycle)

Answer 8

1. Applies to individual and the whole set of requirements
2. Requirements must be testable
3. Measureable acceptance criteria for each requirement agreed with stakeholders

Question 9

Documentation in analysis process

Requirement lifecycle

Answer 9

1. Help manage complexity
2. Prove something has been done
3. To record information for future use
4. To pass a message from one person to another

Question 10

Management in analysis (requirement lifecycle)

Managing change to requirements

Answer 10

1. Once a requirement has been identified, its inclusion within the final product or its de-scoping should be traceable
2. Enables stakeholders to know what is, and is not contained in the final solution.
3. Prevents requirements being missed by accident or new requirements being brought into the projet without consideration of their impact.

Question 11

Benefits of planning poker

Answer 11

1. Reduces peer pressure
2. Create forum for discussing and understandin requirements
3. Allows several people to estimate
4. Those doing the work will be estimating