LN15
LN15
LN15
Lecture Notes
The resulting information system is acceptable to the customer. The system was delivered on time. The system was delivered within budget. The system development process had a minimal impact on ongoing business operations.
Causes of Project Failure Failure to establish upper-management commitment to the project Lack of organizations commitment to the system development methodology Taking shortcuts through or around the system development methodology Poor expectations management Premature commitment to a fixed budget and schedule Poor estimating techniques Overoptimism The mythical man-month (Brooks, 1975) Inadequate people management skills Failure to adapt to business change Insufficient resources Failure to manage to the plan
Why is Software Project Management Difficult? Summerville (1992) The product is intangible Hard to monitor progress and assess quality No clear understanding of the underlying process Rely on process models Software systems are often one-off project Critical and innovative in nature Makes it hard to accumulate experience and to produce useful data
1/4
I S 460
Lecture Notes
Project Management Tools & Techniques A PERT chart is a graphical network model that depicts a projects tasks and the relationships between those tasks. Program Evaluation and Review Technique A Gantt chart is a simple horizontal bar chart that depicts project tasks against a calendar. Each bar represents a named project task. The tasks are listed vertically in the left-hand column. The horizontal axis is a calendar timeline. Joint Project Planning Strategy Joint project planning (JPP) is a strategy wherein all stakeholders in a project (meaning system owners, users, analysts, designers, and builders) participate in a one-to-three day project management workshop, the result of which is consensus agreement on project scope, schedule, resources, and budget. (Of course, subsequent workshops or meetings may be required to adjust scope, budget, and schedule.) Project Management Functions Scoping Planning Estimating Scheduling Organizing Directing Controlling Closing Activity 1: Negotiate Scope Scope defines the boundaries of a projectWhat part of the business is to be studied, analyzed, designed, constructed, implemented, and ultimately improved? Product Quality Time Cost Resources A statement of work is a narrative description of the work to be performed as part of a project. Common synonyms include scope statement, project definition, project overview, and document of understanding. Activity 2: Identify Tasks A work breakdown structure (WBS) is a hierarchical decomposition of the project into phases, activities, and tasks. Milestones are events that signify the accomplishment or completion of major deliverables during a project.
2/4
I S 460
Lecture Notes
Activity 3: Estimate Task Durations 1. Estimate the minimum amount of time it would take to perform the task. We'll call this the optimistic duration (OD). 2. Estimate the maximum amount of time it would take to perform the task. We'll call this the pessimistic duration (PD). 3. Estimate the expected duration (ED) that will be needed to perform the task. 4. Calculate the most likely duration (D) as follows:
Activity 4: Specify Intertask Dependencies Finish-to-start (FS)The finish of one task triggers the start of another task. Start-to-start (SS)The start of one task triggers the start of another task. Finish-to-finish (FF)Two tasks must finish at the same time. Start-to-finish (SF)The start of one task signifies the finish of another task. Scheduling Strategies Forward scheduling establishes a project start date and then schedules forward from that date. Based on the planned duration of required tasks, their interdependencies, and the allocation of resources to complete those tasks, a projected project completion date is calculated. Reverse scheduling establishes a project deadline and then schedules backward from that date. Essentially, tasks, their duration, interdependencies, and resources must be considered to ensure that the project can be completed by the deadline.
Activity 5: Assign Resources Peopleinclusive of all the system owners, users, analysts, designers, builders, external agents, and clerical help that will be involved in the project in any way, shape, or form. Servicesa service such as a quality review that may be charged on a per use basis. Facilities and equipmentincluding all rooms and technology that will be needed to complete the project. Supplies and materialseverything from pencils, paper, notebooks, toner cartridges, etc. MoneyA translation of all of the above into the language of accountingbudgeted dollars! Resource leveling is a strategy used to correct resource over-allocations by some combination of delaying or splitting tasks. There are two techniques for resource leveling: task delaying task splitting
Task Splitting and Delaying The critical path for a project is that sequence of dependent tasks that have the largest sum of most likely durations. The critical path determines the earliest possible completion date of the project. Tasks that are on the critical path cannot be delayed without delaying the entire project schedule. To achieve resource leveling, critical tasks can only be split.
3/4
I S 460
Lecture Notes
The slack time available for any noncritical task is the amount of delay that can be tolerated between the starting time and completion time of a task without causing a delay in the completion date of the entire project. Tasks that have slack time can be delayed to achieve resource leveling
Activity 6: Direct the Team Effort Supervision resources The DEADLINE A Novel About Project Management The One Minute Manager The Care and Feeding of Monkeys Stages of Team Maturity
Activity 7: Monitor and Control Progress Progress reporting Change management Expectations management Schedule adjustmentscritical path analysis (CPA) Activity Network Precedence relations among activities Two types of representations Activity on arrow (AOA) Event 2, Event 3, Activity(2,3)
Critical Path Analysis and Slack Time Using intertask dependencies, determine every possible path through the project. For each path, sum the durations of all tasks in the path. The path with the longest total duration is the critical path. Find slack times for non-critical tasks
4/4