Objectives Project planning and scheduling

1 Objectives Project planning and 1. Introduce Project planning scheduling 2. Examine the stages of Project planning : Scoping Project planning Estimation Mel Rosso-Llopart Risk Analysis scheduling 3. Focus on some of the tools and techniques available to a Project planner Version Carnegie Mellon, 2005 1 Version Carnegie Mellon, 2005 2. Topics Software Project planning Goal is to establish a pragmatic strategy for controlling, planning tracking, and monitoring a complex technical Project Must deal with: Estimation of tasks . Project complexity: has a strong effect but is heavily Cost and time influenced by past practitioner experience Project size: as size increases the interdependency of planning and risk elements also grows. Watch out for scope creep (when customers change requirements mid-cycle). scheduling and why projects are late The degree of structural uncertainty: the degree to which requirements are solidified and the ease of functional scheduling and planning tools decomposition The purpose of Project planning is to ensure that the end Project tracking result is completed on time, within budget, and exhibits quality!

2 Version Carnegie Mellon, 2005 3 Version Carnegie Mellon, 2005 4. Steps in Project planning Scope Project Scope A bounded description of the data and control, function, Estimates Software performance, constraints, interfaces and reliability Risks Project Sufficient to determine Project feasibility and create an Schedule Plan initial plan Control strategy Scoping Techniques: FAST (Facilitated Application Specification Technique), QFD (Quality Scope understand the problem and the work that must be done. Function Deployment), Use-Cases Estimation how much effort? how much time? Risk what can go wrong? how can we avoid it? what can we do Scope is affected by: about it? Customers' needs Schedule how do we allocate resources along the timeline? Business context what are the milestones? Project boundaries Control strategy how do we control quality? how do we control Customers' motivation change? Likely paths for change Version Carnegie Mellon, 2005 5 Version Carnegie Mellon, 2005 6.

3 Page 1. Estimating Resources Estimating Resources - 2. Human Resources: Environmental Resources: Select skills required (both position and specialty, database The hardware and software tools required to develop software engineer). Requires an effort estimate the Project . Planner needs to provide a time window Reusable Software Resources: for booking them Off-the-shelf components (existing software acquired from 3rd party with no modification required). Full-experience components (previous Project code is similar and team members have full experience in this application area). Partial-experience components (existing Project code is related but requires substantial modification and team has limited experience in the application area). New components (must be built from scratch for this Project ). Version Carnegie Mellon, 2005 7 Version Carnegie Mellon, 2005 8. Estimating Cost and Effort Risk Analysis and Management Project scope must be explicitly defined.

4 If not, the Definition of Software Risk: Project may be infeasible Concerns future happenings. What risks might Task and/or functional decomposition is necessary cause the Project to go astray? Historical measures (metrics) are very helpful Involves change. How will changes in customer Triangulation: At least two different techniques should requirements, development technologies, target be used. Can be reconciled if they are within 20%. computers, and other entities affect timeliness Remember that uncertainty is inherent in early estimates and success? Viable Techniques: 1. Delay estimation until later in the Project (XP approach). Requires choice. What methods and tools should 2. Base estimates on similar projects that have already been be used, how many people should be involved to completed reduce risk? 3. Use relatively simple decomposition techniques (LOC or FP). Version Carnegie Mellon, 2005 9 Version Carnegie Mellon, 2005 10. Risk Analysis and Management-2 Risk Management Paradigm Questions: What can go wrong?

5 Control What is the likelihood? What will the damage be? track What can we do about it? RISK identify plan analyze Version Carnegie Mellon, 2005 11 Version Carnegie Mellon, 2005 12. Page 2. Risk (3xM) Mitigation, Monitoring, and Management scheduling Mitigation how can we avoid the risk? I love deadlines. I love the whooshing sound they Monitoring what factors can we track that make as they fly by. Douglas Adams will enable us to determine if the risk is The Schedule connects the scope, work estimates becoming more or less likely? and deadline into a network of SE tasks Management what contingency plans do Must Manage: we have if the risk occurs? Parallelism (tasks can be undertaken simultaneously). Dependency (task has an effect on subsequent tasks). Bad scheduling is a very destructive influence 90-90 Rule: First 90% of a Project is complete in 90% of the scheduled time. The other 10% is also completed in 90% of the time Version Carnegie Mellon, 2005 13 Version Carnegie Mellon, 2005 14.

6 Why Are Projects Late? Why Are Projects Late? - 2. An unrealistic deadline established by outsiders Technical difficulties that could not have been Changing customer requirements that are not foreseen reflected in the schedule Human difficulties that could not have been An honest underestimate of effort and/or foreseen resources required Miscommunication among Project staff Risks that were not considered when the Project Project management failing to recognize schedule started slippage and not taking corrective action Version Carnegie Mellon, 2005 15 Version Carnegie Mellon, 2005 16. Dealing with Unrealistic Tools and techniques for the Deadlines planner Any commander in chief who undertakes scheduling to carry out a plan which he considers defective is at fault; he must put forth his PERT Program Evaluation and Review reasons, insist on the plan being changed, Technique and finally tender his resignation rather Work Breakdown Structure (WBS). than be the instrument of his army's Gantt Chart Named after Henry Grant downfall.

7 Napoleon ETVX How do you track tasks Version Carnegie Mellon, 2005 17 Version Carnegie Mellon, 2005 18. Page 3. Define a Task Network scheduling Task (Activity) Network: a graphical representation of the task flow and interdependencies for a Project Program Evaluation and Review Technique (PERT) AKA. Critical Path Method (CPM) is a Project scheduling method that determines: Concept Scoping Risk Concept Critical Path (the chain of tasks that determine the duration Assess. Implement. of the Project ). Earliest Time that a task can begin if all preceding tasks are completed in the shortest possible time Concept Risk Concept Concept Integrate a, b, c Latest Time for task initiation that will not delay the Project planning Assess. Proof Implement. Latest and Earliest Finish for the overall Project Total Float (the maximum slippage without overall delay) Concept Risk Implementation: Assess. Implement. Automated tools customer Reaction Often use a task network as input Version Carnegie Mellon, 2005 19.

8 WBS Work break down structure Gantt chart What has to be done to complete the Project A Gantt chart provides a graphical illustration of a All the tasks in the Divide and conquer of the schedule that helps to plan, coordinate, and track problem specific tasks in a Project developed in 1917 by Henry L. Gantt Granularity equals level of WBS. A Gantt chart is constructed with a horizontal axis First level, high level tasks representing the total time span of the Project , Second level are those task that complete the broken down into increments (for example, days, first level weeks, or months) and a vertical axis Very similar to Outline for a paper representing the tasks that make up the Project Version Carnegie Mellon, 2005 21 Version Carnegie Mellon, 2005 22. Gantt Chart planning individual Task Work tasks w eek 1 w eek 2 w eek 3 w eek 4 w eek 5. Identify need and benefits Meet with customers Identify needs and Project constraints Establish product statement expressed as ETVX.

9 Milestone: product statement defined Define desired output/control/input (OCI). Scope keyboard functions Scope voice input functions Scope modes of interaction Scope document diagnostics Scope other WP functions Entry Criteria Document OCI. FT R: Review OCI with customer Revise OCI as required; Before starting Tasking Entry Criteria Milestone; OCI defined Exit Criteria Define the functionality/behavior Tasking Define keyboard functions Define voice input functions Decribe modes of interaction . Decribe spell/grammar check Decribe other WP functions FT R: Review OCI definition with customer Revise as required Milestone: OCI defintition complete Validation Isolate software elements Milestone: Software elements defined Validation Research availability of existing software Reseach text editiong components Research voice input components Exit Criteria Research file management components Research Spell/Grammar check components Milestone: Reusable components identified Define technical feasibility After finished Evaluate voice input Evaluate grammar checking Milestone: T echnical feasibility assessed Make quick estimate of size Create a Scope Definition Review scope document with customer Revise document as required Milestone: Scope document complete Version Carnegie Mellon, 2005 24.

10 Page 4. How do I get the tasks? Project planning process Project planning process (2). Divide and Conquer Divide Divide is easy Break Project up into tasks Conquer is hard Estimate the pieces . Bring it back together in stages (milestones). Tausworthe's Principal - The more milestones the more accurate the schedule Corollary - The more milestones, the less time to get work done Version Carnegie Mellon, 2005 25 Version Carnegie Mellon, 2005 26. Project planning process (3) Process (Lifecycle) activation Conquer Big bang Estimate completion of the divided tasks Waterfall Gather the tasks into a whole Cyclical (Spiral). Plan for testing against requirements Prototyping Plan for delivery of product Rapid Application Development We will talk more about these in the next lecture Version Carnegie Mellon, 2005 27 Version Carnegie Mellon, 2005 28. Resource Allocation Tracking the Schedule Use list of resources Use list of Critical dates WBS (Work Breakdown Structure) When do you need the resources Tasks from estimation When can you release the resources Development process being used Actuals vs.