![]() ![]() The customer and the sponsor form a part of the Delivery Team. In the Adaptive Life Cycle, Customer Involvement is the key to successful Projects. The iterations are very rapid and time bound. This approach to Project Management is a combination of both the Iterative and Incremental models. These methods are also known as change-driven or Agile methods. The Adaptive Project Management Life Cycle 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. Each incremental functionality is verified by the customer and hence the relative risk in managing large and complex projects is substantially reduced. The Incremental model is much better equipped to handle change. It supports prototyping and customer interaction is quite high in the build phase of the Project. Large and complex projects greatly benefit from following this model. The process is repeated till the exit criteria for the product or deliverable is fully met. The approach is cyclic in nature and each cycle delivers an added functionality. In this kind of approach the product is developed over a series of incremental steps. The Incremental Project Management Life Cycle It allows a relatively better insulation to changes over the Traditional approach. It can be adopted for less complex and small projects where the deliverables are fairly understood. ![]() It is clear from the above figure that the Iterative Cycle is nothing but a series of mini-waterfalls. Truly speaking this approach was just a baby step in the evolution of project management Life Cycles. In this approach, the processes in each phase are iterated till the phase exit criteria are met. This approach evolved to counter the existing constraints in the traditional approach especially where there was a need to adapt to changes. The Iterative Project Management Life Cycle ![]() This is one of the primary factors which resulted in the evolution of newer approaches which were more focused on Change. 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. There is a high level of emphasis on Documents and document sign offs. This type of approach suits well to small projects with minimal complexity and where the product to be delivered is fairly well understood.Īs depicted in the above figure, exit criteria have to be satisfied before commencing into the successor phase. Work performed in each phase is distinct from the predecessor or the successor phase. ![]() In this type of model, the phases defined may have sequential or overlapping relations or even a combination of both. PMBOK® Guide 5 refers to this method as the ‘Predictive Life Cycle’. This is also known as the Waterfall method. The Traditional Project Management Life Cycle 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. Further the Project Management Life Cycle to be adopted is frequently part of the Organizations’ Project Management Standards. The phases and the relationships together form the Project Management Life Cycle. Project Phases are generally sequential in nature but may have overlapping relationships. 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. Preparing for PMP® Certification? Take this test to know where you stand!Ī Project typically has a number of Phases. 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. Unfortunately, there is no Utopia and Project Managers globally have to be on their toes to deal with changing scenarios. Projects will have no defects and will be accepted by the Customers on Delivery. There will be no failed Projects and no reworks required. 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. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |