Session 2.5 - Launch Scripts & Steps
Chapter 3: Launching a Team Project | Duration: 1 hr
Learning Objectives
By the end of this session, you will be able to:
- Describe the Cycle 1 launch script (LAU1) and its purpose
- Explain how later launches (LAUn) differ
- Complete the INFO form to support team/role assignment
- Summarize the instructor’s steps for product objectives and team setup
Introduction
Launch scripts standardize how teams start. LAU1 is used for the first cycle; LAUn is a streamlined version for later cycles once teams understand the process and product context.
Cycle 1 Launch (LAU1)
Course Overview
Instructor reviews TSPi objectives, grading (team + individual), expectations.
Student Information (INFO)
Collect schedules, role interests, background to form balanced teams.
Product Objectives
Instructor describes the product need statement; Q&A to clarify scope.
Team/Role Assignments
Teams formed, roles assigned; aim for exposure to multiple roles across cycles.
Team Goals
Review goal-setting process and TSPi standard goals.
First Team Meeting (preview)
Purpose and cadence of weekly meetings introduced.
Later Launches (LAUn)
LAUn repeats the essentials with less time: teams already know TSPi and the product need statement, so the focus shifts to role rotation, updated goals, and any changes in scope.
Key Differences
- Simpler steps; faster execution
- Role preferences considered for rotation
- Goals adjusted using data from prior cycles
- Product changes clarified if any
Student Information Form (INFO)
The INFO form gathers scheduling compatibility, role interests, background, and experience. This helps the instructor build teams that can meet and have complementary skills.
What to Provide
- Weekly availability
- Role preferences (review scripts before choosing)
- Experience/background
- Contact info
Why it Matters
- Enables balanced teams and workable meeting times
- Supports rotation across roles over three cycles
- Reduces scheduling conflict risk
Product Objectives
Instructor presents the product need statement (see Appendix A examples). Teams ask clarifying questions to ensure a shared understanding before planning.
Team & Role Assignments
Assignments usually happen at the second class meeting. Aim to keep teams together across cycles to build efficiency, unless major teamwork issues require changes. Rotate roles so each student gains diverse experience.
Guidelines
- Consider role preferences but maintain balance
- Keep functioning teams intact; fix dysfunctional teams quickly
- Ensure everyone experiences multiple roles across cycles
Summary
- LAU1 structures the first launch: overview, INFO, product objectives, team/role assignments, goals.
- LAUn streamlines later launches—focus on role rotation, updated goals, and changes.
- INFO form enables balanced teams and practical schedules.
- Instructor-led clarity on product and grading sets expectations before planning begins.