Presentations, Project Status Reporting, and Design Reviews

1
Presentations, Project Status Reporting, and
Design Reviews

• CS4911
• Fall 2006

2
Administration

• Grades WebCT
• Announcements/Questions Swiki
• Advisor meetings need to schedule or let me
  know name
• Teams that have advisors Earth Curator (5),
  Kids/Allergies(8), Wargame Simulation (11),
  Stinger Bus (18), Suntrust (24), 2110TA (25)
• Needing? Drivers Ed (26), Recruit (22), iPhoto
  (16), Web Submissions (13), Server Cluster (12)

3
Agenda

• Mid-Term Presentations (see webpage)
• Presentation Guidelines
• What is in a status report?
• Sample Contents
• Process Comments
• Final Presentations
• Design Reviews

4
Guidelines

• Each team has 15 minutes for midterm, 25-30
  minutes for final presentations
• Principle purpose of midterm is status, design
  review, Iter 1 demo and project description
• Principle purpose of final is project (Iter 3)
  demo, results, and conclusions
• Each team member must present at least once
• Attendance at presentations mandatory, miss
  yours 1 letter grade, miss others -5 pts per miss

5
Presentations

• Present Positive Image
• Know your audience
• Develop and follow a theme
• Open Body - Conclusion
• Careful with humor
• Watch mannerisms, posture
• Test your AV gear

6
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

7
Slides

• Legibility (8x rule)
• Images (relevant)
• Avoid ransom notes
• Avoid mixed metaphors
• Check details
• Correct Spelling
• Relevant/Correct Images
• Correct Charts

8
OR

• The 10/20/30 rule
• No more than 10 slides
• No more than 20 minutes
• No less than 30 pt fonts.

9
Midterm Presentation Content

• Introduction of team
• Team name, customer, faculty advisor, team
  members, their roles
• Product to be delivered
• Customer background, product context, tangible
  product to be developed
• Overview of requirements
• Design Alternatives, Design Selected, Rationale
• Project plan
• Project Backlog
• Iteration 1 Backlog
• Status
• Iteration 1 Demo

10
A Status Report shows

• Overview of project
• Planned vs. work to go (Burn Down Charts)
• Other Relevant Metrics
• Major Milestones Met or Missed (Burndown)
• Issues
• Show Stoppers
• It is NOT a what I did on my summer project
  save that for the final presentation!

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

• Planned
• Actual
• Projected

As of 1/15/2004
Total Project
Current Quarter
Hours Expended
13
Schedule (By Major Activity)
Design
Coding
Unit Test
Integration
As of 1/3/04
14
Resources (Person-Hours)
Cumulative Effort (Person Hours)
Time
Projected
Total Project Quarter
Actual
15
Product Burndown charts
Hours To Go
1 2 3 4 5
Sprint
16
Sprint Burndown Charts
Hours To Go
1 2 3 4 5
Weeks
17
Resources (Expenditures)
Cumulative Expenditures (Dollars)
Planned
Actual
Time
18
Expenditure by Category
Salary (Base)
Overtime
Equipment
Travel
Training
Supplies
Dollars ()
19
Features
100
Planned
Actual
Percent Complete
DB Design
Security
Reports
Feature Item
20
Defect Rate
Historical
Actual
Defects/KLOC
Time
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
Final Presentation Content

• Introduction of team
• Team name, customer, faculty advisor, team
  members, their roles
• Product to be delivered
• Customer background, product context, tangible
  product to be developed, main design question(s)
• Overview of requirements
• Product actually delivered
• Differences from plan reasons design resolution
  
• Process strengths and weaknesses
• Final Design
• Demo (Iteration 3)

24
Demo at your Final Presentation

• Your final presentation should include a demo of
  your product executing
• Script it
• Know exactly what you are going to show practice
  demo
• Have canned data available (not actual
  proprietary/personal data)
• Dont let demo be first time you try a feature
• Be sure your demo runs in the presentation
  environment

25
Presentation Conclusions

• Plan Presentation Sequence
• Practice (maybe in front of mirror)
• Check content
• Relax and be confident

26
Design Reviews

• Should follow on-line checklist
• Conducted at each major iteration design
• For this classReview with instructor at
  Iteration 2 will focus on VALIDATION section.
• Will post on Syllabus, so keep watching
• Let me know of restrictions
• Can also do on Tuesdays 10-1500