In Utopia, for Projects being implemented, there will be no change in specifications, scope, cost or resources, throughout the Life Cycle of the Project after the Project Management Plan is base lined and signed off. There will be no failed Projects and no reworks required. Projects will have no defects and will be accepted by the Customers on Delivery. Unfortunately, there is no Utopia and Project Managers globally have to be on their toes to deal with changing scenarios. This article attempts to equip Project Managers with the knowledge of various Project Life Cycle Approaches so as to help them deal with changes on their Projects.
A Project typically has a number of Phases. The number of phases, their need for the Project and the level of control required over each phase are primarily defined by the nature of the Project, the complexity of the same and the industry to which the Project has to cater to.
Project Phases are generally sequential in nature but may have overlapping relationships. The phases and the relationships together form the Project Management Life Cycle. Further the Project Management Life Cycle to be adopted is frequently part of the Organizations’ Project Management Standards. In real life, a Project Manager may not have a say in the Life Cycle approach to be adopted, but understanding the different approaches and methodologies can help a Project Manager better adapt to changes.
This is also known as the Waterfall method. PMBOK 5 refers to this method as the ‘Predictive Life Cycle’. In this type of model, the phases defined may have sequential or overlapping relations or even a combination of both. Work performed in each phase is distinct from the predecessor or the successor phase. This type of approach suits well to small projects with minimal complexity and where the product to be delivered is fairly well understood.
As depicted in the above figure, exit criteria have to be satisfied before commencing into the successor phase. There is a high level of emphasis on Documents and document sign offs. Major constraints in following this kind of Life Cycle Approach or model is the incapability of the model to adapt to changes without resulting in major reworks or workarounds. This is one of the primary factors which resulted in the evolution of newer approaches which were more focused on Change.
This approach evolved to counter the existing constraints in the traditional approach especially where there was a need to adapt to changes. In this approach, the processes in each phase are iterated till the phase exit criteria are met. Truly speaking this approach was just a baby step in the evolution of project management Life Cycles.
It is clear from the above figure that the Iterative Cycle is nothing but a series of mini-waterfalls. It can be adopted for less complex and small projects where the deliverables are fairly understood. It allows a relatively better insulation to changes over the Traditional approach.
In this kind of approach the product is developed over a series of incremental steps. The approach is cyclic in nature and each cycle delivers an added functionality. The process is repeated till the exit criteria for the product or deliverable is fully met. Large and complex projects greatly benefit from following this model. It supports prototyping and customer interaction is quite high in the build phase of the Project.
The Incremental model is much better equipped to handle change. Each incremental functionality is verified by the customer and hence the relative risk in managing large and complex projects is substantially reduced. On the downside, there is a possibility of gold plating, wherein the functionalities not really required end up being built into the Product or Deliverable.
These methods are also known as change-driven or Agile methods. This approach to Project Management is a combination of both the Iterative and Incremental models. The iterations are very rapid and time bound. In the Adaptive Life Cycle, Customer Involvement is the key to successful Projects. The customer and the sponsor form a part of the Delivery Team. Sometimes in Agile approaches, the phases may not be clearly defined. It relies heavily on customer feedback and the ability of the team to quickly work on the feedback and incorporate the same into the Project. Communication and Collaboration are of paramount importance in implementing Projects using the Agile methodologies.
An Agile approach is suitable for complex projects where the requirements are absolutely unclear, but it is possible to define incremental requirements. Some of the major challenges in adopting the Agile approach are required high levels of Customer Involvement (which may not always be possible or practical). Also, having a Virtual Team may work against the required enhanced collaborative approach.
Project Management Life Cycles have thus evolved from the need of to deliver successful projects. The ability of the Project Team or Organization, to adapt to a particular framework of Project Life Cycle considering the nature of the Project, goes a long way in delivering the Right Product, Result or Service. The Project Management Institute, PMI, has played a significant role in advocating the different Project Management Life Cycle methodologies. The Project Management Body of Knowledge is regularly updated. The PMBOK5 has for the first time, included brief write-ups on the different Project Management Life cycle approaches being followed worldwide for Project Implementation.
Happy learning! We wish you good luck in your PMP certification journey!
Projects being implemented, there will be no change in specifications, scope, cost or resources, throughout the Life Cycle of the Project after the Project
Yogeeta Deshmukh, PMP has over 17 years’ experience in Leading IT Teams across Industry Verticals like Aluminium, Automobile Components and Pharmaceutical. She is currently working as General Manager, IT for Pharmaceutical Manufacturing Organization with a Global Presence.
Disclaimer: "PMI®", "PMBOK®", "PMP®", "PMI-RMP®", "CAPM®" and "PMI-ACP®" are registered marks of the Project Management Institute, Inc.
The Swirl logoTM is a trade mark of AXELOS Limited.
ITIL® is a registered trade mark of AXELOS Limited.
PRINCE2® is a Registered Trade Mark of AXELOS Limited.
MSP® is a Registered Trade Mark of AXELOS Limited
Certified ScrumMaster® (CSM) and Certified Scrum Trainer® (CST) are registered trade marks of SCRUM ALLIANCE®
Professional Scrum Master is a registered trademark of Scrum.org
The APMG-International Finance for Non-Financial Managers and Swirl Device logo is a trade mark of The APM Group Limited.
The Open Group®, TOGAF® are trademarks of The Open Group.
IIBA®, the IIBA® logo, BABOK® and Business Analysis Body of Knowledge® are registered trademarks owned by International Institute of Business Analysis.
CBAP® is a registered certification mark owned by International Institute of Business Analysis. Certified Business Analysis Professional, EEP and the EEP logo are trademarks owned by International Institute of Business Analysis.
COBIT® is a trademark of ISACA® registered in the United States and other countries.
CISA® is a Registered Trade Mark of the Information Systems Audit and Control Association (ISACA) and the IT Governance Institute.
CISSP® is a registered mark of The International Information Systems Security Certification Consortium ((ISC)2).
CISCO®, CCNA®, and CCNP® are trademarks of Cisco and registered trademarks in the United States and certain other countries.