Presentations, Project Status Reporting, Test Plans, Project History

1
Presentations, Project Status Reporting, Test
Plans, Project History

• CS3911
• Summer 2004

2
Agenda

• Mid-Term Presentations (see webpage)
• Presentation Guidelines
• What is a status report?
• Sample Contents
• Process Comments
• Final Presentations
• Test Plans
• Project Histories

3
Guidelines

• Each team has 15 minutes for midterm, 25-30
  minutes for final
• Principle purpose of midterm is status, for final
  is project presentation
• Each team member must present at least once
• Attendance at presentations mandatory, miss
  yours 1 letter grade, miss others -5 pts per miss

4
Presentations

• Present Positive Image
• Know your audience and your material
• Tell em what you are going to tell em, tell em,
  tell em what you told em
• Use logical sequence
• Watch mannerisms, posture
• Slide construction (Fonts, Art)
• Careful with humor
• Test your AV gear

5
Presentations (contd)

• Normally given by PM with support, but
• Backup slides
• Rehearse Stay within time limits
• Leave room for questions
• Be honest
• NEVER read slides
• Eye contact
• Transitions (Um so.yeah)

6
Here is my presentation

• Presentations are fun because they deal with lots
  and lots of material. Sometimes the material is
  interesting, but sometimes it is not. Sometimes
  it is longbut sometimes short.
• I like to write all my sentences on the slide so
  I can read them to you over and over and make my
  presentation as absolutely boring as possible.
• As I look and read you these slides, I can bore
  you more and more while avoiding any possible eye
  contact that might make it look like I am
  actually talking to you.
• Presentations are fun because they deal with lots
  and lots of material. Sometimes the material is
  interesting, but sometimes it is not. Sometimes
  it is longbut sometimes short.
• Presentations are fun because they deal with lots
  and lots of material. Sometimes the material is
  interesting, but sometimes it is not. Sometimes
  it is longbut sometimes short.
• Presentations are fun because they deal with lots
  and lots of material. Sometimes the material is
  interesting, but sometimes it is not. Sometimes
  it is longbut sometimes short.
• Presentations are fun because they deal with lots
  and lots of material. Sometimes the material is
  interesting, but sometimes it is not. Sometimes
  it is longbut sometimes short.

Here is an important diagram
Here is some text
Some more stuff
And this
7
Whats Wrong??
8
A Status Report shows

• Quick overview of project
• Planned vs. Actual
• Other Metrics
• Major Milestones Met or Missed
• Issues
• Show Stoppers
• It is NOT a what I did on my summer project
  save that for the final presentation!

9
The Project Managers Cube
Quality
Schedule
Feature Set
Resources
10
Schedule (Total)
.02 to .03 Development

• Planned
• Actual
• Projected

As of 1/15/2004
Total Project
Current Quarter
Hours Expended
11
Schedule (By Major Activity)
Design
Coding
Unit Test
Integration
As of 1/3/04
12
Resources (Man-Hours)
Cumulative Effort (Man Hours)
Time
Projected
Actual
Total Project Quarter
13
Resources (Expenditures)
Cumulative Expenditures (Dollars)
Planned
Actual
Time
14
Expenditure by Category
Salary (Base)
Overtime
Equipment
Travel
Training
Supplies
Dollars ()
15
Features
100
Planned
Actual
Percent Complete
DB Design
Security
Reports
Feature Item
16
Defect Rate
Historical
Actual
Defects/KLOC
Time
17
Other Metrics

• ECP Rates
• Outstanding ECP
• Productivity Rates
• Benchmarking Data (14/KLOC)
• Process Improvement Data
• Risk Data

18
Project Risk Summary

• Prevention
• Mitigation
• Elimination
• Risk Rapidly Changing Requirements
• Strategy Mitigation thru Customer Rep
• Results No schedule slip

Do not repeat entire risk plan. This is for
risks that actually happened.
19
Major Milestones Met

• M1.7 Critical Design Review 6/15/2002
• R3.4 Formal Code Review 7/1/2002

20
Milestones Missed

• C1.5 Customer Alpha Code Delivery 7/5/02
• Schedule slipped by 3 weeks, new delivery
  milestone 8/1/02
• Explanations

It is not necessarily bad to miss a MS. Its
just bad to miss and have no plan to recover
21
Issues

• Excessive Overtime Rate
• Design Element 1.3 Modification
• Expansion of Requirements by 25

These should be things that are affecting your
project , time, hours
22
Showstoppers

• Issue Main Development Server Hardware failure
• Action RAID Controller on order, expected
  delivery 7/12/02
• Impact DB Coding stopped for 2 weeks, Work
  shifted to v2 design

23
Conclusions

• Plan Presentation
• Practice (maybe in front of mirror)
• Check content
• Relax and be confident
• First Peer Eval Due Soon
• To advisor and instructor

24
Final Demo

• Plan and practice demo
• Have canned data
• Dont let demo be first time you try feature!
• Recover from errors confidently
• Be sure your demo runs in the presentation
  environment

25
Project Histories/Peer Eval

• AKA Post Mortem
• An analysis of your project experience
• Submit to advisor and instructor
• No set length
• Your chance to expound on your work and
  experiences in the project.
• Can show work by phase by member (or can use peer
  eval forms for privacy)
• Two peer evals they do affect your grade!!