Session 2.6 - First Meeting, Data, and Project Start
Chapter 3: Launching a Team Project | Duration: 1 hr
Learning Objectives
By the end of this session, you will be able to:
- Run the first weekly team meeting using the WEEK script
- Define data deliverables and deadlines for status tracking
- Explain the purpose of the project notebook and what goes into it
- Use the TSPi support tool to capture plan/actual data
- Begin the STRAT script with the team prepared
Introduction
After launch steps, teams immediately establish their weekly cadence and data habits. The first meeting sets the pattern for communication, tracking, and accountability.
First Team Meeting
Held during launch to agree on goals and meeting mechanics. Follow the WEEK script (Table 3.5):
- Review goals and commitments
- Share individual WEEK forms (status/variances)
- Discuss risks, issues, and needed help
- Confirm next steps and deadlines
Keep it Short
Weekly meetings are the backbone of communication; time-box them and come prepared with data.
Data Requirements
Agree on what data each member provides to the planning manager and by when. Typical weekly data:
- Time, size, and defect logs (plan vs. actual)
- Updated TASK and SCHEDULE for personal work
- WEEK form summarizing progress and issues
Pick a consistent day; without timely data, neither the team nor instructor can assess status.
Project Notebook
The project notebook (Appendix G) is the central repository for all key project information. The team leader maintains it; everyone contributes artifacts.
What Goes In
- Goals, plans, status reports
- Meeting minutes, issues, risks
- Inspection/test records
- Baselined artifacts and changes
Why It Matters
- Single source of truth for the team
- Evidence for reviews and grading
- Supports continuity across cycles
TSPi Support Tool
The support tool helps with planning, data entry, and tracking; it can auto-produce project summary forms if all time/size/defect data are entered.
Usage Tips
- Enter plan and actual data promptly to avoid gaps
- Use tool outputs for WEEK and instructor reports
- Validate data accuracy—tool amplifies bad inputs
Project Start (STRAT Script)
With launch complete, the team begins the STRAT script: define strategy, size estimates, and cycle content. Enter with:
- Roles assigned and goals agreed
- Meeting cadence and data deadlines set
- Project notebook initialized
- Support tool ready for plan and data capture
Summary
- First weekly meeting (WEEK script) sets the tone for communication and accountability.
- Data timeliness is critical for status tracking—pick a day and stick to it.
- Project notebook stores all key artifacts; the support tool streamlines data handling.
- With launch done, begin STRAT with clear roles, goals, cadence, and tooling.