DOC PREVIEW
ODU CS 350 - Lecture Notes

This preview shows page 1-2-15-16-17-32-33 out of 33 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 33 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 33 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 33 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 33 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 33 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 33 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 33 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 33 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

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 - 1Exam 1, in-class Thursday, March 16Open-book, open-notesA take-home component will be available on Thursday also, due next week.Announcements - 2Team member requests:If you have requests for team members, please send them to me by this Friday, March17.Target team size is 5You 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 5ReadingTeam Software Process text, Ch. 1, 2, 3TopicsIntro to TSPiWhat’s coming in the rest of the semester?Some problems and warningsQuandaryMost 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 overviewi stands for instruction.Subset of TSPFocus:Based on PSP•Scripts, measurements, metricsTeams & rolesDifferent members responsible for different parts of joint projectDevelop 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 failRarely for technical reasonsInternal politicsTeam does not bindFail to develop rapport with customersPeople will fight over meaningless issuesPressure is a problemHaving a plan of action helps•Know real issues that must be resolved rather than worrying about imaginary problemsCommon team problemsIneffective leadershipFew people are natural leaders, but can get better with practiceBeneficial to have effective examples (people)Some people don’t know how to compromiseLack of participationProcrastination/lack of confidencePoor qualityFunction creepPoor peer evaluationTeam definitionFor TSPi, a team consists ofat least 2 people (TSP designed for 5), whoare working toward a common goal, whereeach member is assigned specific responsibilities and wheresuccessful completion of project requires team members to contribute.Jelled teamsWhole greater than sum of partsGreat satisfaction for membersNecessary conditionsTask to be performed clearTeam responsible clearly identified•Including who is and is not on teamTeam has control over tasksCan 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 teamsCommon goalsAssigned rolesMost people want to contribute.Each person needs specific task to complete that he/she understands, andPeer pressure has an effect.Need plansStrategy for achieving goalsCommunicationWeekly meetings – if possible part of recitation timeLaunching a new teamDefining goals for team and team membersDefining rolesHow the group is to be organizedEstablish responsibilities of each role•Just makes is easier and quicker to divide up workStill, everybody develops and tests code, everybody manages some aspect of the projectAssigning rolesGoal considerationsAggressive but realisticHere, we want to stretch your abilities, but not crush youAvoid timid, safe goals•Should strive to achieve, but cannot be punished severely if not achieved•They matter (but they don’t)Identifying team goalsWrite them downDecide how to measureExplain why you picked themGive copy to other team members and to instructorHave the support manager put a copy in the project notebookGeneral comments on goalsShould relate to how a user will perceive the product:QualityUtilityCostsWhen availableIn 350, instructor and grader are the customersPossible goalsAttempt 1:Produce a quality productRun a well-managed projectExtend project beyond minimalThese may seem too vague, but if concrete measurements are


View Full Document

ODU CS 350 - Lecture Notes

Download Lecture Notes
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Lecture Notes and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Lecture Notes 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?