Endeavor Debrief Team

Definition

Endeavor Debrief Team (a.k.a., Project Postmortum Team): the team that meets to capture lessons learned during an endeavor, typically after it has completed

As illustrated in the preceding figure, the Endeavor Debrief Team method component is part of the following inheritance hierarchy:

The typical team-specific responsibilities of an Endeavor Debrief Team are to:

Determine and document those aspects of the endeavor the went well.
Determine and document those aspects of the endeavor that could be improved during similar future endeavors.

An endeavor debrief team typically inherits the general team responsibilities from the team method component.

An Endeavor Debrief Team typically consists of one or more persons that played each of the following roles (as appropriate) during the endeavor:

Analyst:
- Metrics Analyst
- Security Analyst
- User Analyst (a.k.a., user researcher)
Architect:
Content Workers:
Designer:
- GUI Designer (a.k.a., Visual Designer)
- Hardware Designer
- Software Designer
Domain Expert (a.k.a., Subject Matter Expert)
Engineer:
- Database Engineer
- Hardware Engineer
- Integration Engineer (a.k.a., Build Master)
- Internationalization Engineer
- Process Engineer (a.k.a., Methodologist)
- Programmer
- Quality Engineer
- Requirements Engineer
- Reuse Engineer
- Reuse Librarian
- Security Engineer
- Test Engineer (a.k.a., Tester)
  - Test Monitor
- Toolsmith
- Usability Engineer
Manager:
Post-Development Role:
Strategist:
Trainer
Technical Writer

An Endeavor Debrief Team typically performs the following team-specific tasks an incremental, iterative, parallel, and time-boxed manner:

An endeavor debrief team typically inherits the common team tasks from the team method component.

An Endeavor Debrief Team typically produces all or part of the following work products:

The scope of this team includes all aspects of the endeavor including producers, work units, work products, stages, and languages.
This team usually has a very short duration of only at most a few days due to its limited objectives and large size.
Where practical, most members of the endeavor team should also be members of the endeavor debrief team so that lessons learned are not lost. However, this is often not practical because certain endeavor team members have since moved on to new endeavors or even left the development organization. Such individuals should document their lessons learned upon leaving the endeavor.