WXGE 6103 Software Engineering Process and Practice Project

WXGE 6103 Software Engineering Process and Practice Project Management

Contents n n n Introduction Project Management Activities Project Planning Project Scheduling Risk Management

Introduction Successful project management means meeting all three goals (scope, time, and cost) – and satisfying the project’s sponsor! It is the project manager’s duty to balance these three often-competing goal!. 3

Project management n Def: ¨ activities involved to ensure that software is delivered on schedule, within budget and meet the requirements

Project Management Activities 1) Proposal Writing ¨ objectives of the project ¨ how it will be carried out ¨ cost and schedule estimates 2) Project Planning and Scheduling ¨ Identifying the activities, milestones, deliverables ¨ A plan to guide development towards the project goals

Project Management Activities 3) Project Costing ¨ Estimate the resources 4) Project Monitoring and Reviews (continues activity) ¨ Keep track of the progress ¨ Compare actual and planned progress ¨ Predict potential problems 5) Personnel Selection and Evaluation ¨ Select skilled staff with appropriate experience 6) Report Writing and Presentations ¨ Reporting on the project

Project Planning n n n Probably the most time-consuming project management activity Plans must be regularly revised Besides software project plan (concerned with schedule and budget) and need to produce other plans.

Types of project plan

Project planning process Establish the project constraints Make initial assessments of the project parameters Define project milestones and deliverables while project has not been completed or cancelled loop Draw up project schedule Initiate activities according to schedule Wait ( for a while ) Review project progress Revise estimates of project parameters Update the project schedule Re-negotiate project constraints and deliverables if ( problems arise ) then Initiate technical review and possible revision end if end loop

The project plan n The project plan sets out: ¨ The resources available to the project; ¨ The work breakdown; ¨ A schedule for the work.

Project plan structure n n n n Introduction. Project organisation. Risk analysis. Hardware and software resource requirements. Work breakdown. Project schedule. Monitoring and reporting mechanisms.

Activity Organization n Activities should be organised to produce tangible outputs to judge progress Milestones are the end-point of a process activity. At each milestone, there should be a formal output that can be presented to management. Deliverables are project results delivered to customers Milestones in the Requirement Engineering Process

Project Scheduling n n Split project into tasks/activities, dependencies and estimate time and resources required to complete each task Organize tasks concurrently to make optimal use of workforce Minimize task dependencies to avoid delays caused by one task waiting for another to complete Dependent on project managers intuition and experience Figure : Project scheduling process

Project Scheduling n Problem ¨ Estimating the difficulty of problems and the cost of its solution is hard ¨ Productivity is not proportional to the number of people working on a task ¨ Adding people to a late project makes it later because of communication overheads ¨ The unexpected always happens, hence allow contingency in planning

Project Scheduling n n Bar charts (Gantt chart) and activity network diagram are graphical notations used to illustrate the project schedule Show project breakdown into tasks. Min 1 week. Max 8 – 10 weeks. Activity network diagram show task dependencies and the critical path Critical path Minimum time required to finish the project can be estimated by the longest path (critical path) ¨ Delay in the completion of any critical activity causes project delays. ¨ n Gantt charts show schedule against calendar time

Project Scheduling Task durations and dependencies

Project Scheduling Activity Network diagram

Project Scheduling Activity Timeline / Bar Chart /Gantt Chart

Project Scheduling Staff Allocation

Risk Management n n n A risk is a probability that some adverse circumstances will occur. Risk management ¨ identify risks that may affect project schedule or sw quality ¨ produce plans to avoid the anticipated risks 3 categories of risk: ¨ 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

Software risks

Risk Management Process

Risk Management n Risk Management Process ¨ Risk Identification n ¨ Risk Analysis n ¨ Assess the likelihood and consequences of these risks Risk Planning n ¨ Identify project, product and business risks Draw up plans to avoid or minimise the effects of the risk Risk Monitoring n Monitor the risks throughout the project

Risk Identification Risk types:

Risk analysis Assess probability and seriousness of each risk. n Probability may be very low, moderate, high or very high. n Risk effects might be catastrophic, serious, tolerable or insignificant. n

Risk analysis

Risk analysis

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

Risk management strategies (i)

Risk management strategies (ii)

Risk monitoring Assess each identified risks regularly to decide whether or not it is becoming less or more probable. n Also assess whether the effects of the risk have changed. n Each key risk should be discussed at management progress meetings. n

Risk indicators