Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
Develop the necessary understanding and skills to produce and manage a simple project schedule.
All technical projects involve 100s of small tasks Some tasks do no affect the project completion Other tasks are critical for project completion Project manager must:
define all project tasks build a network that depicts their interdependence identify the critical tasks track the progress of these tasks recognize the delay one day at a time one
Compartmentalization define distinct tasks Interdependency- parallel and sequential tasks Interdependency Time allocation - assigned person days, start time, ending time) Effort validation - be sure resources are available Defined responsibilities people must be
assigned
Defined Outcomes- each task must have an output Outcomes Defined milestones - review for quality
Software Process Management
If we fall behind schedule we can always add more programmers and catch to late in the project
The relationship between the number of people working in software project and overall productivity is not linear
Fewer people and longer time period is a better option for software development
Software Process Management
40-20-40
Front-end Analysis & Design
Coding
Back-end testing
1515-20%
construction activities
coding or code generation
3030-40%
RA RA
(20-25%) Testing Testing (30 - 40%)
SD
Milestones are objectively identifiable points in a project. They are generally associated with the completion of a major activity. It is often a good idea to associate them with deliverables.
For example, a milestone might be established at initial requirements sign-off. This checkpoint will come after the requirements documents have been produced, inspected, corrected and signed off on. The only rule for establishing a checkpoint is that you must be able to objectively determine if that milestone has been reached.
Feasibility report
Requirements definition
Architectural design
Requirements specification
Concept Development projects New Application Development Projects Application Enhancement Project Application Maintenance Project Reengineering Project
Software Process Management
Casual
Structured
Strict
Software Process Management
There are a number of activity network techniques which are similar in nature. The most commonly used include PERT (Project Evaluation and Review Technique) and CPM (Critical Path Method).
2
A 2d
C 2d
4
E 2d
1
B 2d
5
D 5d
4
E 2d
1
B 2d
5
D 5d
(PERT)
(CPM)
Both techniques (PERT and CPM) are driven by information already developed in earlier project planning activities: Estimates of efforts Decomposition of product function selection of appropriate process model and task set Decomposition of tasks
Both PERT and CPM provides quantitative tools to determine the critical path establish the most likely time estimated for individual tasks by applying statistical models calculate boundary time (window) for a particular task
By summing the earned values for the completed tasks we determine that at the end of week 2, the cumulative earned value (the percent complete) is 7.81+2.64+2.64+1.98+2.64+5.21=22.91%. Now, knowing the earned value the project group can determine if they are ahead, behind on on schedule to complete on time
It is argued that earned value provides accurate and reliable readings of performance as early as 15% into a project. This kind of quantitative project management is essential if projects are to be consistently delivered on time.
Project Tracking
Additional resources focussed on problem area Staff may be redeployed Project Schedule can be redefined
Software Process Management
Problem diagnosed