2.  Probably the most time-consuming project management activity.  Continuous activity - Plans must be regularly revised.  Various different types of plans may be developed to support the main software project plan that is concerned with schedule and budget.

3.  The project plan sets out: ◦ The resources available to the project ◦ The work breakdown ◦ A schedule for the work

4.  Introduction.  Activity organization.  Risk analysis.  Hardware and software resource requirements.  Work breakdown.  Project schedule.  Monitoring and reporting mechanisms.

5.  Activities in a project should be organized to produce tangible outputs for management to judge progress.  Milestones are the end-point of a process activity.  Deliverables are project results delivered to customers.  The waterfall process allows for the straightforward definition of progress milestones.

6.  Split project into tasks and estimate time and resources required to complete each task.  Organize tasks concurrently.  Minimize task dependencies to avoid delays.  Dependent on project managers intuition and experience.

8.  Used to be 40-20-40% rule ◦ Analysis/Design: 40-50% ◦ Coding: 15-20% ◦ Testing/Debugging; 30-40%  Now approximately: 60-15-25% rule  Save 2-3% for Project Planning and some % for reviews

9.  Graphical notations used to illustrate the project schedule.  Show project breakdown into tasks. Tasks should not be too small. They should take about a week or two.  Activity charts show task dependencies and any critical paths.  Bar charts show schedule against calendar time.

14.  Microsoft Project : PERT (program evaluation and review technique) and GANTT charts  Uses ◦ effort estimates, decomposition of product function, process model, project type, task set, task network ◦ determine critical paths, time estimates, boundary times (earliest and latest start times, earliest and latest end times, float times) ◦ produce a timeline or GANTT chart ◦ should also allocate resources

15.  Tracking ◦ conduct periodic status meetings: report progress and problems ◦ evaluate results of all reviews ◦ milestones accomplished by scheduled date? ◦ Compare dates ◦ informal meetings on subjective assessments  Control ◦ light if everything going well ◦ if not: diagnose problem, reassign resources, redefine schedule

16.  It is essential to have ◦ A word processor; and ◦ A spreadsheet  Tool that automate estimation of effort ◦ FP calculator and UCP calculator on my web page  Management tools assist with planning and monitoring ◦ MacProject ◦ Microsoft Project

17.  IS A DELIVERABLE  TURN IN TO ME!  http://www.rspa.com/docs/Projectplan.html http://www.rspa.com/docs/Projectplan.html

18.  Risk management is concerned with identifying risks and drawing up plans to minimise their effect on a project.  A risk is a probability that some adverse circumstance will occur ◦ Project risks affect schedule or resources; ◦ Product risks affect the quality or performance of the software being developed; ◦ Business risks affect the organisation developing or procuring the software.

20. l Identify risks and assess probability and seriousness of each risk.

21.  Consider each risk and develop a strategy to manage that risk.  Avoidance strategies ◦ The probability that the risk will arise is reduced;  Minimisation strategies ◦ The impact of the risk on the project or product will be reduced;  Contingency plans ◦ If the risk arises, contingency plans are plans to deal with that risk;