CS 350, slide set 6Announcements - 1Announcements - 2ReadingTopicsQuandaryTSPi overviewTSPi Structure and flowTSPi Development Script - 1TSPi Development Script - 2TSPi Development Script - 3Why projects failCommon team problemsTeam definitionJelled teamsHow to build teamsLaunching a new teamGoal considerationsIdentifying team goalsGeneral comments on goalsPossible goalsGoals and metrics - 1Goals and metrics - 2Goals and metrics - 3TSPi team members - 1TSPi team members - 2Team member goalsExample role goalsLaunch scriptStudent information sheets - 1Group AssignmentsWeekly meeting scriptWeekly formsCS 350, slide set 6M. OverstreetOld Dominion UniversitySpring 2006Announcements - 1Exam 1, in-class Thursday, March 16Open-book, open-notesA take-home component will be available on Thursday also, due next week.Announcements - 2Team member requests:If you have requests for team members, please send them to me by this Friday, March17.Target team size is 5You need not identify 4 other people in order to send a request; smaller group requests are fine, but I will attempt to fill out as many groups as possible to size 5ReadingTeam Software Process text, Ch. 1, 2, 3TopicsIntro to TSPiWhat’s coming in the rest of the semester?Some problems and warningsQuandaryMost of the technology you will need to understand to be successful in your jobs doesn’t exist yet.Employers identify problem solving as the key employee skill.In some crucial ways, the main thing to learn is a process for dealing with new problems.TSPi overviewi stands for instruction.Subset of TSPFocus:Based on PSP•Scripts, measurements, metricsTeams & rolesDifferent members responsible for different parts of joint projectDevelop complete product in several complete cyclesTSPi Structure and flowNeeds statementCycle 1 LaunchStrategy 1Plan 1Requirements 1Design 1Implementation 1Test 1Postmortem 1Cycle 2 LaunchStrategy 2Plan2Requirements 2Design 2Implementation 2Test 2Postmortem 2Cycle 3 LaunchStrategy 3Plan 3Requirements 3Design 3Implementation 1Test 3Postmortem 3TSPi Development Script - 1Purpose Guide team through dev. software projectEntry Criteria Instructor to guide and support project Students know PSP Instructor has project description Instructor has described project objectivesExit Criteria Completed project Completed user documentation Completed and current project notebook Documented team evaluations and cycle reportsTSPi Development Script - 2Wk Step Activities1 Review Read TSP ch. 1 and 2.2 LAU1STRAT1 Assign teams and roles. Read TSP ch. 3, App B and one of ch. 11-15. Produce conceptual design, establish dev. strategy, make size estimates and assess risk. Read TSP ch. 4.3 PLAN1 Produce cycle 1 team and engineer plans Read TSP ch. 5 & App C.4 REQ1 Define and inspect cycle 1 requirements. Produce system test plan and support materials. Read TSP ch. 6 and test sections of ch. 9.4 DES1 Produce and inspect cycle 1 high-level design. Produce integration test plan and support materials. Read TSP ch. 7.TSPi Development Script - 3Wk Step Activiies5 IMP1 Implement and inspect cycle 1. Produce unit test plan and support materials. Read TSP ch. 8.6 TEST1 Build, integrate, and system test cycle 1. Produce user documentation for cycle 1. Read TSP ch. 9.7 PM1 Conduct a postmortem and write cycle 1 final report. Produce role and team evaluations for cycle 1. Read TSP ch 10, 16, 17, and 18.CYCLE 2 Repeat above for cycle 2 (we won’t have time for this).CYCLE 3 Repeat above for cycle 3 (we won’t have time for this).Why projects failRarely for technical reasonsInternal politicsTeam does not bindFail to develop rapport with customersPeople will fight over meaningless issuesPressure is a problemHaving a plan of action helps•Know real issues that must be resolved rather than worrying about imaginary problemsCommon team problemsIneffective leadershipFew people are natural leaders, but can get better with practiceBeneficial to have effective examples (people)Some people don’t know how to compromiseLack of participationProcrastination/lack of confidencePoor qualityFunction creepPoor peer evaluationTeam definitionFor TSPi, a team consists ofat least 2 people (TSP designed for 5), whoare working toward a common goal, whereeach member is assigned specific responsibilities and wheresuccessful completion of project requires team members to contribute.Jelled teamsWhole greater than sum of partsGreat satisfaction for membersNecessary conditionsTask to be performed clearTeam responsible clearly identified•Including who is and is not on teamTeam has control over tasksCan be dangerous to team members•Can’t “not do it” attitude•Hard on personal relationships (spouses, significant others)•See “Soul of a new machine” by Tracy Kidder•Identified as one of best 100 books of 20th centuryHow to build teamsCommon goalsAssigned rolesMost people want to contribute.Each person needs specific task to complete that he/she understands, andPeer pressure has an effect.Need plansStrategy for achieving goalsCommunicationWeekly meetings – if possible part of recitation timeLaunching a new teamDefining goals for team and team membersDefining rolesHow the group is to be organizedEstablish responsibilities of each role•Just makes is easier and quicker to divide up workStill, everybody develops and tests code, everybody manages some aspect of the projectAssigning rolesGoal considerationsAggressive but realisticHere, we want to stretch your abilities, but not crush youAvoid timid, safe goals•Should strive to achieve, but cannot be punished severely if not achieved•They matter (but they don’t)Identifying team goalsWrite them downDecide how to measureExplain why you picked themGive copy to other team members and to instructorHave the support manager put a copy in the project notebookGeneral comments on goalsShould relate to how a user will perceive the product:QualityUtilityCostsWhen availableIn 350, instructor and grader are the customersPossible goalsAttempt 1:Produce a quality productRun a well-managed projectExtend project beyond minimalThese may seem too vague, but if concrete measurements are
View Full Document