1. Project Management Inspections and Reviews 1 February

2. What you should be doing Update web site and functional spec per meeting Write a draft contract Post on web email me when you have it done and I will give you feedback as soon as possible Signed contracts due next week. You do not need to schedule a special meeting with clients to sign

3. Contract Content Key goals and requirements Deliverables Deliverable dates (milestones) Software Testing Documentation (user, administrative, maintenance) Client responsibilities Meetings (when and with whom) Constraints, risks and dependencies What needs to be included Template

4. Project Management Tools PERT Charts Gantt Charts

5. PERT Charts Critical path analysis or method Program Evaluation and Review Technique Also known as activity networks Developed by Navy in 1958 Three stages: Planning (tasks and sequence) Scheduling (start and finish times) Analysis (float and revisions) Two different models Activities are nodes (most common) or arcs

6. Pert Chart Activity Box

7. Pert Charts

8. 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

9. Planning: PERT and CPM 1. Identify the specific activities and milestones. 2. Determine the proper sequence of the activities. 3. Construct a network diagram. 4. Estimate the time required for each activity. 5. Determine the critical path. 6. Update the PERT chart as the project progresses. 1. Specify the individual activities. 2. Determine the sequence of those activities. 3. Draw a network diagram. 4. Estimate the completion time for each activity. 5. Identify the critical path (longest path through the network) 6. Update the CPM diagram as the project progresses.

10. Gantt Charts Milestone charts Invented by Harvey Gantt in 1916 Advantages Less detailed Amenable to management overlays

11. Gantt Chart

12. Gantt Chart with Overlays

13. Scheduling Steps and Tools Put together minimal solution Primary requirements Start with external commitments Product descriptions Milestones from contract Introduce internal milestones Work breakdown structure Product Flow PERT Chart, Gantt chart Focus on the risks Risks from contract Add next level of features where possible Secondary requirements

14. Project Plan for this project Use simple Excel spreadsheet (or equivalent)

15. What you should be able to tell from your project plan What is Joe working on this week? Who can help me if I run into trouble? If I have to choose an activity to be late, which one will impact the project more?

16. Software Sources Open source tools: dmoz.org/Computers/Software/Project_Management/Open_Source/

17. Reviews and Inspections

18. Why? Developer can’t 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

19. 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

20. Will you review or inspect? What will you review or inspect? How will you review or inspect?