ProjectSchedulingandTracking-UniversityofMichigan.ppt

Project Scheduling and Tracking CIS 375 Bruce R. Maxim UM-Dearborn What does the customer want to know? Do you understand my needs? Can you design a system to help me? How long will it take? How much will it cost? Scheduling Principles - 1 Compartmentalization the product and process must be decomposed into a manageable number of activities and tasks Interdependency tasks that can be completed in parallel must be separated from those that must completed serially Time allocation every task has start and completion dates that take the task interdependencies into account Scheduling Principles - 2 Effort validation project manager must ensure that on any given day there are enough staff members assigned to completed the tasks within the time estimated in the project plan Defined Responsibilities every scheduled task needs to be assigned to a specific team member Scheduling Principles - 3 Defined outcomes every task in the schedule needs to have a defined outcome (usually a work product or deliverable) Defined milestones a milestone is accomplished when one or more work products from an engineering task have passed quality review Step 1List the Deliverables Documents. Demonstration of function. Demonstration of subsystem. Demonstration of accuracy. Demonstration of reliability, security, or speed. Step 2Define the Milestones Completion of an activity or deliverable (must be measurable). Activities must have definite a start and stop. A milestone is point in time not a time period like an activity. Step 3Work Breakdown Structure Create the work breakdown structure Separate the project into phases composed of steps Subdivide steps into activities as needed Project Effort Distribution Generally accepted guidelines are: 02-03 % planning 10-25 % requirements analysis 20-25 % design 15-20 % coding 30-40 % testing and debugging Defining a Task Set Consider project type. Degree of rigor. Review rigor adaptation criteria. Determine task selector value. Consider concept