"Project and program management is the art and science of planning, controlling and tracking of activities and resources to achieve the organization’s strategic and business objectives."

Project behaviour during lifecycle

What is the behaviour of the curve during different time intervals, such as at (0), (0, 20-30%], (20-30%, 50%], (50%, 75%], and (75%, 100].





Brief analysis and points of discussion

Since a project has a temporary endeavor, the timeframe has to be finite. The broken lines in the graph represent finite areas such as phases or milestones. The black graph represents the estimated project plan schedule, the blue graph represents an early schedule, and the red graph represents a lagging schedule.

In an ideal situation the beginning is usually slow because people need to acquire confidence with the project, and once the schedule has achieved 20-30% of the work completed, the slope of the graph will change and will accelerate due to the confidence and knowledge acquired. At 70-80% the schedule has reached a very good level of control and will continue with confidence to full completion of the project.

What is the scenario before Time=0, i.e., before launching of the project?

In practice, most organizations don't really start from scratch when launching a project. Some pre-analysis work has been done in order to get an idea of what has to be done in terms of requirements, characteristics and resources needed for the project. With this information (although it's at high level), it's possible to make an estimation of the time and cost; decisions are usually taken after this information is available (or at least we reach a confidence level of 80%). The realization of a successful project will require commitments from the operating organization and all stakeholders.
Start of my discussion on Project and Program ManagementWhy do we need to implement project management?Defining a project
Project behaviour during lifecycleThe differences between Project, Operation and ProgramProject Variables
Project Manager's RoleProject Management Life CycleProject Environment
Project's Organizational Structures - FunctionalProject's Organizational Structures - MatrixProject's Organizational Structures - Team
Visualizing ProcessesStructuring into formsThe Earned Value method to keep track of project performance
TeleworkingProgram ManagementFunctional Analysis
The Needs/Requirements Life CycleUsing PERT for estimating tasksProject Cost
A simple way to software sizing measuresRisk ManagementWork Breakdown Structure (WBS)
WBS & OBS Matrix TableProject Estmating TechniquesProject Cost: building the project resource sheet
Validating The Project EstimateProject Scheduling by MilestonesProject Scheduling by Gantt Charts
Project Scheduling using PDM - Project Network DiagramProject Network Diagram AnalysisProject Opportunities from Cause-Effect Case Analysis
Build and Deploy a Project using OO technologyProject Network Diagram Information and DataA graphical representation of a typical project and product management approach and the relationship throughout their life cycle
A Global PMO Work ModelA Simple Method for Keeping Track of Project Performance using the Earned Value MethodMultiple Projects Performance Analysis using the Earned Value Method
Forecasting Project Costs using Variance AnalysisSizing Applications from User PerspectiveA Metric System for Measuring the Degree of Success of Managed Service Requests
Follow-Up: Estimating using PERT based on Beta Distribution ModelAn approach to a Cost Effective Software SolutionVisualizing the state of projects using geometric figures
A Project Management Method - Graphically