Planning Guideline

advertisement
Pittsburgh, PA 15213-3890
Assignment 2
Make a Project Plan
Sponsored by the U.S. Department of Defense
© 2001 by Carnegie Mellon University
July 2002
Teaching a Software Project Course
Overview
Assignment Objectives
Review of PLAN1 process
Produce size estimates
Produce the Task and Schedule Plans
Produce the Quality Plan
Produce individual engineer plans
Develop a configuration management plan
Description of assignment tasks
© 2001 by Carnegie Mellon University
Version #
Teaching a Software Project Course - page 2
Assignment Objectives
After completing the exercise, you will
• understand how a TSPi team develops a project plan
• have developed a plan for the FPM project
• have carried out steps from the PLAN1 script
• have used the TSPi tool to develop the plan
© 2001 by Carnegie Mellon University
Version #
Teaching a Software Project Course - page 3
Review of PLAN1 Process
Produce size estimates
Produce task and schedule plans
Produce the quality plan
Produce individual engineer plans
Produce a configuration management plan
© 2001 by Carnegie Mellon University
Version #
Teaching a Software Project Course - page 4
Produce Size Estimates
Produce the conceptual design
• objects for all cycles
Select a development strategy
• allocate objects to cycles
• produce a minimal working subset in the first cycle
• Development Manager leads
Produce preliminary size estimates
• estimate LOC in each class
• use size estimates as a basis for allocation of tasks to
cycles
• enter estimates on the STRAT form
© 2001 by Carnegie Mellon University
Version #
Teaching a Software Project Course - page 5
Produce Task and Schedule Plans
Use LOC estimates and LOC/hour rates for time
estimation on SUMS form
• use task list from STRAT
• students with PSP experience should estimate 50% of
their LOC/hour from PSP course
• otherwise use 5 LOC/hour for first cycle
Generate TASK and SCHEDULE forms
• estimate times based upon LOC and LOC/hour
estimates
• estimate time available for the team on the SCHEDULE
form
© 2001 by Carnegie Mellon University
Version #
Teaching a Software Project Course - page 6
Produce the Quality Plan
Estimate defect injection rates for each phase
Estimate yield for each phase
Generate a trial quality plan
Compare the quality plan with team goals
• examine produce quality at each phase of the project
• modify time planned for defect removal if quality goals
are not satisfied
Continue generating trial plans until quality goals are
satisfied
© 2001 by Carnegie Mellon University
Version #
Teaching a Software Project Course - page 7
Produce Individual Engineer Plans
Assign tasks based upon estimated task time and each
engineer’s available time.
Generate a TASK and SCHEDULE form for each
engineer.
Determine whether tasks are balanced across the team.
Modify task assignments until a balanced plan is reached.
© 2001 by Carnegie Mellon University
Version #
Teaching a Software Project Course - page 8
Produce a Software Configuration
Management Plan
Maintain copies of all product elements
Record changes to each Software Configuration Item
• by whom
• when
• what was changed
• why it was changed
Support Manager leads
© 2001 by Carnegie Mellon University
Version #
Teaching a Software Project Course - page 9
Description of Assignment 2, Part 1
Each team uses the TSPi tool to develop and document a
development plan for the FPM system
• enter product information
• estimate size of deliverables and complete the SUMS
form
• determine and allocate tasks, estimate times, and
complete the TASK form
• determine direct hours and complete the SCHEDULE
form
• make a quality plan and complete the SUMQ form
• complete the SUMP form
• review the plan and make adjustments as necessary
© 2001 by Carnegie Mellon University
Version #
Teaching a Software Project Course - page 10
Description of Assignment 2, Part 2
Each team develops and documents a configuration
management plan
• list the items to be part of the Software Configuration
Management system, e.g., strategy, plan, SRS, etc.
• describe how items in the system will be identified and
stored
• define a process for change control
© 2001 by Carnegie Mellon University
Version #
Teaching a Software Project Course - page 11
Download