9 September

1
9 September

• Scheduling (cont.)
• Contract

2
Pert Charts
3
CPM Critical Path Method

• Alternative to PERT
• Dupont 1957
• Graphical view of project
• Predicts time required to complete
• Shows which activities are critical to
  maintaining the schedule

4
Planning

• PERT

• CPM

• Identify the specific activities and milestones.
• Determine the proper sequence of the activities.
• Construct a network diagram.
• Estimate the time required for each activity.
• Determine the critical path.
• Update the PERT chart as the project progresses

• Specify the individual activities.
• Determine the sequence of those activities.
• Draw a network diagram.
• Estimate the completion time for each activity.
• Identify the critical path (longest path through
  the network)
• Update the CPM diagram as the project progresses.
  

5
Gantt Charts

• Milestone charts
• Invented by Harvey Gantt in 1916
• Advantages
• Less detailed
• Amenable to management overlays

6
Gantt Chart
7
Gantt Chart with Overlays
8
Scheduling Steps and Tools

• Put together minimal solution
• Primary requirements
• Start with external commitments
• Product descriptions
• Milestones
• Introduce internal milestones
• Work breakdown structure
• Product Flow
• PERT Chart, Gantt chart
• Focus on the risks
• Add next level of features where possible
• Secondary requirements

9
Software Sources

• Open source tools
• dmoz.org/Computers/Software/Project_Management/Ope
  n_Source/

10
What needs to be in the plan?

• Code
• Design
• Test
• Documentation
• Learning
• Presentation and demo prep
• Reviews

11
Reviews and Inspections

• Why?
• Developer cant correct unseen errors
• More eyes to catch problems
• Earlier is cheaper
• Integration fix typically 3-10 times the cost at
  design
• Difference in terms
• Review implies completed work, often reviewed by
  someone at a different level
• Inspection implies peer review of work in progress

12
Inspections

• Introduced by Michael Fagin in 76 (IBM Systems
  Journal)
• Formalized process
• Specific roles and steps
• Heavy preparation and follow-up
• Used for documents and code

13
Where We Are

• Understand project
• Concept
• Personas and user stories
• Use cases
• Requirements
• Functional Spec
• How much can be accomplished
• Project plan
• Commitment contract