1 / 34

Welcome page

Welcome page. Outline. Introduction Status on each role Special topic. Brief Intro. Team 2 McCabe C yclomatic Complexity A nalyzer. Planning . Planning . Team Earned Value. Why are we behind schedule. The team didn’t close some of the 1st week tasks because the plan was delayed

ollie
Download Presentation

Welcome page

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Welcome page

  2. Outline Introduction Status on each role Special topic

  3. Brief Intro Team 2 McCabe Cyclomatic Complexity Analyzer

  4. Planning

  5. Planning

  6. Team Earned Value

  7. Why are we behind schedule • The team didn’t close some of the 1st week tasks because the plan was delayed • Some examples are: • Risk meeting X 6 • LogD-LogT week_1 X6

  8. Team Planned Hours versus Actual Hours

  9. Team SUMS Estimates versus Actual

  10. How are we spending our time?

  11. Quality

  12. Quality - Goal Goal • In 66% of inspections we meet our goal to find more than 3 defects/hour

  13. Quality - Inspections • We were able to almost eliminate typo defects • We get an overall defect reduction over time

  14. Quality - goal • Almost all inspections achieved our goal Goal

  15. Quality - Goal Goal • In 66% of inspections we meet our goal to spend at least half of DLD time inspecting it. • Concern: are we spending too much? Maybe the goal must be upper bounded too.i.e. 0.5<x<1

  16. Process

  17. Process • Process Analysis • Meeting Process • 75% of times, the planned time for the meetings have been exceeded. • But, we have improved the meeting process comparing to the first cycle. • Risk Management Process • Risk Management formally started during the 2nd cycle • Planned :Risk Meetings on every Status Meeting • Actual: Risk Meetings 50 % of times

  18. Development

  19. Development contd. Development Report

  20. Support

  21. Top Risks

  22. Configuration and Reuse Reuse Configuration

  23. Special Topic: Peer Reviews Helped us to: • Objectively understand roles’ goals • Promote team jellying (candid environment)

  24. Special Topic: Peer Reviews. cont • Great for constant improvement • We want to get better so we measure “You cannot improve what you cannot measure” (Rosso-Llopart, 2009)

  25. Questions?

  26. Backup Slides

  27. Team Earned Value By Week

  28. Role: Team Lead

  29. Role: Process Manager

  30. Process • Process Analysis • Meeting Process • Meetings: LAUNCH, STRAT, PLANNING, Weekly STATUS • 2 of 14 meetings have no planned time for the entire project. • But, none of meetings for the 2nd cycle had no planned time. • 75% of times, the planned time for the meetings have been exceeded. • But, we have improved the meeting process comparing to the first cycle. • Risk Management Process • Risk Management starts from the 2nd cycle. • 4 risks • Planned to have Risk Meetings after every Status Meeting, but actually have the Risk Meetings 50 % of times

  31. Process • PIPs • 3 PIPs from the 1st cycle

  32. Quality Overview • Our inspections are meeting our quality goals • Adjust quality goals according with our current data • It’s dificult to track quality without updated data

  33. Development contd. Strategy Changes • Task planning • Adjust plan according to Cycle 1 data • Detailed Design • Write pseudo codes in the design • Designers = implementer • Experiments on critical functionality to design more objectively/accurately • Alternative Strategy • McCabe: use tree parser

More Related