Final Project Status Presentation May 1, 2003

1
Final Project Status PresentationMay 1, 2003

• This presentation will probably involve audience
  discussion, which will create action items. Use
  PowerPoint to keep track of these action items
  during your presentation
• In Slide Show, click on the right mouse button
• Select Meeting Minder
• Select the Action Items tab
• Type in action items as they come up
• Click OK to dismiss this box
• This will automatically create an Action Item
  slide at the end of your presentation with your
  points entered.

• Project Name
• your projects web page URL
• Presenter Names

Guidelines Presentation is to me, not the
customer Every member of the team will present at
least 1 slide. Each slide should take about 3
minutes to present.
2
Context and Objectives

• The customers problem/need
• High-level product development goals
• Specific development objectives summarized

3
Accomplishments/Progress

• List achievements and progress items
• Highlight those celebration events and other
  things that made progress possible
• Expected customer satisfaction rating and trend

4
Final Statistics and Data

• Scope - stories delivered over the 3 iterations
• Significant scope changes from customer
• Total hours worked on project
• Quality measures - total of defects found,
  fixed, still open
• Performance to schedule plan - ahead, behind,
  internal slips
• Product size - classes, SLOCs, screens,
  test cases, etc.

5
Issues and Risk Remaining

• List deficiences and problems remaining to be
  addressed
• List corrective actions suggested
• Address implications
• List outstanding technical issues that need to be
  solved
• Summarize their impact on the project
• List any dubious technological dependencies for
  project, e.g. external technology included in
  product
• Indicate source of doubt
• Summarize actions recommended

6
Lessons Learned

• Development process lessons
• XP lessons
• Customer interaction lessons
• IDE tools experiences
• Final do differentlies list

7
Future Work

• Customer usage and evolution requirements
  anticipated
• Additional functionality needed
• List goals for any known follow-on work
• Specific items that will be done
• Issues that will be resolved