INTRODUCTION Successful software projects require Careful planning Good use of iterative approaches. Understanding Risks Assigning ressources Defining work structure Balancing the budget

Project Management - Outline Defining the Project Manager Role The Project Manager The Project Artifacts and Milestones Planning Projects Managing Iterations Managing Risks Software Engineering Process - with the UPEDUModule 5 - Project Management

Project Manager Role Plan and control all the activities Identify and solves problems early Decide on the tradeoffs ; Optimizes the performance of individual activities Software Engineering Process - with the UPEDUModule 5 - Project Management

Specify goal and objectives Strategies Policies Plan Specify goal and objectives Strategies Policies Plans (Task assign , schedule. etc) Procedures Software Engineering Process - with the UPEDUModule 5 - Project Management

Control (ensure Evrything OK) Using measurable objectives How far to completion Budget Quality Effect of change Team performance Taking corrective actions Redirecting the team towards original plan Modifying the original plan Software Engineering Process - with the UPEDUModule 5 - Project Management

Plans and Controls Planning Controlling Elaboration Transition Start 1/97 LCO 3/97 B u i l d # 1 2 5/97 LCS IOC 12/97 2/98 4/97 Planning 100 75 50 25 Completed (% of total) Controlling Elaboration Inception Transition Construction Software Engineering Process - with the UPEDUModule 5 - Project Management

Managing Expectations Why manage expectations? 1. People are not perfect. 2. People are not logical. 3. People perceive things differently. 4. Software engineers are people too. 5. Things happen. This is key on both the customer (especially) and the developer side. A new car! One of the keys to having a happy customer at delivery time is to manage their expectations of what they are to receive. Gause & Weinberg, 1989 Software Engineering Process - with the UPEDUModule 5 - Project Management

Project management A set of activities based on the iterations Risks are evaluated Project plan is dev (many iterations) Iteration plan is drawn up , updated , revisited before the start of the next iteration

Project Management Discipline Risk List Work Measurement Order Plan Develop Plan Phases Measurement Project and Iterations Plan Manager Project Planning Reviewer Review Software Development Plan

Software Development Plan Responsible for putting together , monitoring and updating the software dev plan. (content likely change drasttically throughout the project ) Risk List Project Manager Project Plan Measurement Plan Software Development Plan UPEDU GUIDELINE: Project Plan UPEDU GUIDELINE: Risk list Software Engineering Process - with the UPEDUModule 5 - Project Management

Software configuration Each iteration : requirement , analysis and Design, implementation , testing , project management Software configuration Change management Manager must define milestones (end of each iteration , end of each phase) to steer the progress of the project activities( enable to decide wheather OK , abortion or change should be done.

Major Milestones : progress ! Customer acceptance or end of life Product Release To the customer Product sufficiently mature for customers Initial Operational End product Milestone Commit resources for construction Lifecycle Architecture Milestone Commit resources for the elaboration phase Lifecycle Objective Milestone Inception Elaboration Construction Transition time Software Engineering Process - with the UPEDUModule 5 - Project Management

Project Management - Outline Defining the Project Manager Role Planning Projects Project Organization The Planning strategies The Project Plan Artifact Managing Iterations Managing Risks

Project organization is influenced by many factors: The Size of the Software Development Effort Formality, Standards, Process Rigidity. The Degree of Novelty First of its Kind, Evolution Cycle, Maintenance Type of Application Mission-critical, Performance, Memory constraints, The Current Development Process Process Maturity, Experience of the Developers and Managers Organizational Factors Team attitudes toward changes, Team enthusiasm toward the project Technical and Managerial Complexity Size of the team vs size of the project

Planning strategies - Top-Down Begins understanding general req and constraints. Then derives a macro-level budget and schedule and decompose this into lower-level budgets and intermidiate milestones Bottom-up Analysis of the micro-level budgets and schedules Add all the elements – high level budget and intermediate milestones.

Top-down and Bottom-up- Project Plan Iteration Plan Next Current Phases and major milestones What and when Iterations for each phase Number of iterations Objectives Duration Staffing profile Tasks Allocation to individuals/teams Major builds Coarse-Grained Plan Inter iteration Fine-Grained Plans Intra iteration Software Engineering Process - with the UPEDUModule 5 - Project Management

Project Plan Project Plan IT1 IT2 IT3 IT4 IT5 Iteration Plan Design Product Release Project Plan Project Planning Architecture Review ß1 ß2 IT1 IT2 IT3 IT4 IT5 Start Proposal 4/02 LCA IOC 2/03 1/02 3/02 7/02 12/02 Iteration Plan 4/02 5/02 Design Review Build #1 Build #2 Software Engineering Process - with the UPEDUModule 5 - Project Management

Bar / Gantt Chart Sample Actual Progress Ahead of Schedule Planned Progress Completed Task Behind Schedule Time Now

Typical project contains info about Work Structure : (WBS) project breaks to manageable tasks Schedule: the act of assessing the level of effort and ressources required Budget : allocate a certain cost to each activity in the WBS Resource Paul Mary Joe Sylvia Stefan Role Designer Use-Case Specifier System Analyst Implementer Architect Activities Define Operations Detail a Use Case Find Actors and Use Cases Perform Unit Tests Identify Design Mechanisms $$$ Software Engineering Process - with the UPEDUModule 5 - Project Management

Project Management - Outline Defining the Project Manager Role Planning Projects Managing Iterations The Definition of an Iteration Scope on an Iteration Iteration assessment Managing Risks

Managing iterations Best way of structuring software dev project is through an evolutionary dev plan (iterations ) Project manager must divide and organize the sequence of iterations according to specific objectives. Each iteration will have its share of requirements(objectives) , activities and risks. After completing an iteration, manager may find that previously identified risks are no more risks or new ones crop up. Should mitigate as many risks as possible

Iterations An iteration Process Disciplines Supporting Workflows Inception Elaboration Construction Transition Engineering Workflow Requirements Analysis & Design Implementation Test Config. & Change Mgmt Project Management Iterations Software Engineering Process - with the UPEDUModule 5 - Project Management

Scope of an Iteration depends on Factors How many iterations should be included in the project plan? How long should each iteration take to plan? Depends on a number of factors: Size of the system being built: The larger the system, the longer the duration. Number of people: The larger the number of people, the longer the duration.(overhead for planning the work) Low 3 0 1 1 1 Typical 6 1 2 2 1 High 9 1 3 3 2 Total I E C T UPEDU Concept: ITERATION Software Engineering Process - with the UPEDUModule 5 - Project Management

Objective evaluation-Metrics Meaning Progress Stability Modularity Quality Maturity Expenditures Size and complexity Rate of change in the project’s complexity or size Scope of change Number of errors Frequency of errors Project expenditures against plan Iteration assessment – using metrics Difficult to assess the whole project. One approach is to assess a project at each iteration. Manager must continuously (meatings) assess progress and risks to prevent any difficulties Successful iteration : risks reduced as planned , all functionalities implemented , quality objective met Software Engineering Process - with the UPEDUModule 5 - Project Management

Project Management - Outline Defining the Project Manager Role Planning Projects Managing Iterations Managing Risks Risk Definition Risk Strategies Risk Assessments

Managing risks Manager must : have a knowledge of the risks to be present have a knowledge of the info that could be missing . Have clear strategi to mitigate them Deal with problems (unavailabe ressources , funding of the project , scheduling)

Concepts Associated with Defining Risk Information missing on a given subject Indirect risk: Project has little or no control (client may lack financing , member may be sick) Direct risk Project has a large degree of control (inacurate scheduling , budget shortage) Risk attributes: Probability of occurrence Risk magnitude indicator: High, Significant, Moderate, Minor, Low UPEDU Concept: RISK Software Engineering Process - with the UPEDUModule 5 - Project Management

Risk Strategies-managing risks Risk Strategies are needed to be deployed once risks are identified and classified Risk acceptance live with it Risk avoidance reorganize the project to eliminate the risk (remove non critical minor functionality ) Risk mitigation ( through tests and prototypes) reduce the probability or impact Risk contingency (as result of a failure to mitigate) plan “Plan B” (ex : new iteration) Risk transfer sub-contract the risk Software Engineering Process - with the UPEDUModule 5 - Project Management

Risks assesments Monitoring through objective measurements should be done throughout the software dev life cycle. For every risk identified , its probability of occurence as well as its impact on the project must be established Mitigating and contingency strategies must be devised Keep up to date the risk list throughout the project