5/29/2007SE TSP Launch1 Team Software Project (TSP) May 29, 2007 Launch/Strategy Team Formation

5/29/2007SE TSP Launch2 Class Agenda Recap Team Exercise Team exercise discussion Team Launch & Strategy Project Plan Commitment Goal Setting Next Week

5/29/2007SE TSP Launch3 May 22 Class Recap Course objectives Constraints Team roles Team project Other questions?

Team Exercise

5/29/2007SE TSP Launch5 Launching a Project – Goals Typical Project Goals Customer Needs Target Market Date Functionality Goal Setting Unrealistic Goals = demotivator Aggressive but realistic = ideal Cisco Strategy “Under-commit, exceed customer expectations” But, A reputation for “sandbagging” can be very dangerous

5/29/2007SE TSP Launch6 Goal Setting Use a confidence level to set goals (e.g. 90%) SMART Goals Specific Measurable Actionable Realistic Timely

5/29/2007SE TSP Launch7 TSPi Team Goals Produce a quality product Percent of defects found before the first compile: >80% Number of defects found in system test: 0 Requirements functions included at project completion: 100% Run a productive & well managed product Error in estimated product size: <20% Error in estimated development hours: <20% Percent of data recorded & entered in project notebook: 100% Finish on Time: Days early or late in completing the development cycle: <4

5/29/2007SE TSP Launch8 Commitment What is it? A promise! Commitment pitfalls Frequently implied (assumed commitment) Frequently given even though intent is not a commitment

5/29/2007SE TSP Launch9 Team Meeting Meeting Objective Synchronize on upcoming activities, assess status, raise issues, assign action items, discuss resolutions Gather & analyze the team’s data for prior week and to date Interval Once a week (for formal meeting) Follow WEEK script (modified) Capture Discussions Decisions Action Items Issues Risks Data (ala WEEK form) Output Weekly minutes document TASK & SCHEDULE forms (when applicable) Updated Project Notebook

5/29/2007SE TSP Launch10 TSPi Tool

5/29/2007SE TSP Launch11 TSP Development Phase Preliminary Plan Documentation: Conceptual Design (in Project Plan) STRAT form (in Project Plan) ITL log (Risks & Issues – extended version)

5/29/2007SE TSP Launch12 Development Strategy Why Plan? Common understanding of objective & work required Basis for tracking work completion Provides assessment of effort required & if objectives are achievable

5/29/2007SE TSP Launch13 Development Approach Waterfall Iterative Build one, throw it away Rapid Application Design (RAD) Extreme Programming (XP)

5/29/2007SE TSP Launch14 Strategy Assessment Development Approach / Conceptual Design High Level System Architecture (components) Size estimate (LOC, FP) Effort (staff hours, days, weeks) Time (calendar time) Functionality Risks Configuration Management Process – next week

5/29/2007SE TSP Launch15 Risks Defined: Issues – will happen Risks – may or may not happen To avoid or control risks In advance, determine: –Mitigation strategy –Contingency Plan –Likelihood & Impact (e.g. high, med, low)

5/29/2007SE TSP Launch16 Risk Mitigation Strategies Iteration Reduce feature commitment Prototype Push out schedule Control adders & changes

5/29/2007SE TSP Launch17 Due Next Week Project Plan –Early draft due by COB Friday for review with instructor –Reviewed draft due by start of Tuesday’s class Weekly Meeting kick-off –Document in notes Presentation (brief) –Functionality (required) –Development approach, estimates, etc. (pick a couple to talk about) Note: text deviation- CM plan not due yet

5/29/2007SE TSP Launch18 Team Project Project Roadmap Need statement Roles Schedule Forms & Quality Records