- 2004 SEPG
"Launch Lessons Learned"
Publication History |
Background Required |
This paper was written and presented by
See the final slides for acknowledgements and credits to contributors.
- December 15, 2003: Draft
posted for peer review and comments
- March 9, 2004: Draft
posted for peer review and comments.
- March 10, 2004:
was presented at the
2004 Software Engineering Process Group Conference
(Note: slide section on non-developers
was dropped, and final set of Observations were skipped during actual presentation,
due to time restrictions.)
A minor further post-presentation update to expand the References is planned
(e.g., add a link to the
XP Evaluation Framework XP-EF which is referenced in the slides).
Resources: (Supplemental Materials)
- Excel workbook template for 'Coaching Post-Mortem'
- Coach's checklists for weekly
This paper assumes basic familiarity with the
(will also be
Corporate Research Scientific Publications
This tutorial summarizes "lessons learned" by a new TSP Coach during the first year.
Data collected by
students during their initial training is compared vs. data from
projects in which they participated.
In addition, the evolution of experiences from initial project launches through the most recent is examined.
The major 'lessons learned' topics covered are:
Launch Logistics (Before, During, and After);
Challenges in Applying Historical Data; and
Coaching Challenges and Observations.
Examples of issues to be analyzed include:
The previously planned topic of Including Non-Developers as Launch Participants
was eliminated due to limited presentation time. Look for it to be posted here separately in the near future
as supplemental material.
- To what extent is class data predictive of quality or productivity in real projects?
- In what areas did process compliance lessen over time, or improve with experience?
- Which roles required greatest or least coaching support in initial launches, and to what extent did that change in subsequent launches? Can any key factors in success be identified for each role?
- How did the effectiveness of risk management evolve as the teams gained experience on their TSP projects?
- In cases where there was a technology change from class to projects or between projects, how did the teams use their previous PSP data to help them estimate and plan with the new technology?