Project Life Cycles are diverse; they are generally shaped by the business requirements and organizational preference. However, the style of life cycle can also be considered - if requirements are well-known, plan-driven is good. If the project is going to be ambiguous at first, an iterative-incremental style is best. If Change is going to be major factor, Agile is considered.
Sequential Phases: We need to finish the menus, and then we can start training the staff. Overlapping Phases: We need to start moving the kitchen equipment through the back door before we finish the landscaping.
Predictive life cycle: Nuclear facility reclamation. You ramp down the facility. You then clean up the facility. Then you recover the landscape.
Iterative and Incremental: We develop a high-level plan for the new data center in order to gain consensus and start reserving funding. We then start planning the early phases, which will help us gather data for further planning. We then finish early phases, which give us the information required to finish planning the later phases.
Agile: We are performing a marketing campaign, and know our product will go through major changes as the consumers review our prototype. The prototype is an early sprint, and we learn from that in order to add to what we know about consumers and product manufacturing. This is all fed back quickly to product design, which is still ongoing. The Sprints are small groups of work, while Scrum is the enhanced communication that is required for all the diverse pockets of work to remain connected.
The Simplilearn community is a friendly, accessible place for professionals of all ages and backgrounds to engage in healthy, constructive debate and informative discussions. Get your pressing questions answered,
participate in monthly contests, create polls to get a feel for the market, build your network, and more! Pull up a chair and come join the discussion -today!