Project sponsors are interested to get the results they signed up for and they want to get some confirmation that their Project is on the right track. They are not that much interested in the Project Methodology that is used as long as they get the results they want on time.
The best time on agile projects to perform the Project Review is between one of the earlier sprints. The reason for this is that there is more time remaining to influence the project favorably. The Project Audit will be most effective when it is conducted by an outside facilitator. This ensures confidentiality for all stakeholders. The “venting“ that might happen during the process is an important part of the overall audit.
Some differences to traditional projects are
- Every sprint should have produced shippable code. What is the business value of the shipped features vs. the costs?
- How many tests were performed for the shippable code?
- How much technical documentation was created?
- How much End User Documentation was created?
- Determine goals of Project Review?
- Research the Agile Project
- What is the organizational attitude towards Agile?
- Measure how much work is completed in each sprint
(Burn up chart per sprint)
- Review the Product Backlog . How good are the functional
and non-functional requirements documented?
- Review Sprint Backlogs
- Get feedback about Daily Scrum Meetings
- Review existing Reports (e.g. how often is the Product Backlog
Burndown Chart updated)
- Review available documentation from previous Sprint Retrospective
meetings
- Conduct Interviews with all stakeholders (e.g. SCRUM
Master, Product Owner, Team)
3. Prepare Project Review Report
- Identify issues and challenges
- Identify lessons learned
- Prepare recommendations to address issues, challenges
and concerns
- Present report to Agile Team
Here is a link that has some more info on agile metrics
