PMBOK 7. Project Performance Domain: Development Approach & Life Cycle
This domain relates focuses on how projects are structured and executed, emphasizes the importance of selecting appropriate development approaches and life cycles based on project characteristics and requirements.
Domain terminology
Deliverable — is a tangible or intangible good or service produced as a result of a project that is intended to be delivered to a customer (either internal or external). A deliverable could be a report, a document, a software product, a server upgrade or any other building block of an overall project. A deliverable may be composed of multiple smaller deliverables.
Development approach — A method used to create and evolve a product, service, or result during the project life cycle, such as a predictive, adaptive, or hybrid method. The development approach can demonstrate specific characteristics, such as being iterative or incremental.
Life Cycle — A standard project typically has four major phases (each with its agenda of tasks and issues): initiation, planning, implementation, and closure. These phases represent a project’s path from beginning to end and are generally referred to as the project’s “life cycle.”
Rhythm (Cadence) — this is a tact, the frequency of activities (or a set of them) throughout the project, expressed in the delivery of results.
PMBOK 7 integrates development approach and life cycle. These three functions include cadence (rhythm), approach to development, and life cycle. Accordingly, the main result of these functions fit into three main results:
- Development approaches are consistent with expected results
- Life cycle phases are obviously concerned with the delivery of business value from the beginning to the end of a project
- Life cycle phases facilitate both the necessary rhythm of delivery of results and the implementation of the approach to their development/obtainment.
In the end, it all comes down to the integration of this three functions.
Rhythm of delivery of results
It refers to the consistent and recurring pattern or pace at which project outcomes or deliverables are produced and provided throughout the project lifecycle. It emphasizes the importance of establishing a regular cadence or rhythm in delivering tangible results to stakeholders, ensuring continuous progress and alignment with project goals and objectives. This rhythm helps maintain momentum, manage stakeholder expectations, and facilitate effective communication and coordination within the project team.
Approaches to developing/obtaining a product/project result
It refer to the various methodologies, strategies, or techniques used to create or achieve the desired outcome of a project. These approaches encompass a range of methods, including predictive (waterfall), iterative, incremental, adaptive (agile), or hybrid approaches. The selection of the most suitable approach depends on factors such as project goals, complexity, uncertainty, stakeholder preferences, and organizational culture. Each approach has its own principles, practices, and processes tailored to address specific project requirements and challenges. The ultimate goal is to effectively manage the project’s development process to deliver high-quality results on time and within budget.
How to choose an approach to development / obtaining results (Agile, Waterfall, Hybrid?)
Choosing an approach to development or obtaining results (whether Agile, Waterfall, Hybrid, or another method) involves considering various factors to determine the most suitable approach for your specific project. Here’s a step-by-step guide on how to choose:
Understand Project Requirements: Begin by thoroughly understanding the project requirements, objectives, scope, and constraints. Consider factors such as project size, complexity, budget, timeline, technology, and stakeholder expectations.
Assess Risks and Uncertainty: Evaluate the level of uncertainty and volatility associated with the project. Agile methodologies are well-suited for projects with high levels of uncertainty and rapidly changing requirements, while Waterfall may be more appropriate for projects with stable requirements and low uncertainty.
Analyze Team and Organizational Capabilities: Assess the skills, expertise, and experience of your project team members. Consider their familiarity with different development methodologies and their ability to adapt to change. Additionally, evaluate your organization’s culture, structure, and policies, as they may influence the choice of approach.
Consider Stakeholder Preferences: Take into account the preferences and priorities of key stakeholders, including clients, sponsors, end-users, and project team members. Engage stakeholders early in the decision-making process to ensure alignment and buy-in.
Evaluate Project Constraints: Consider any constraints related to time, budget, resources, and regulatory compliance. Determine whether the chosen approach can effectively address these constraints while delivering value to the project.
Assess Flexibility and Adaptability: Evaluate the level of flexibility and adaptability required throughout the project lifecycle. Agile methodologies excel in environments where flexibility and responsiveness are essential, allowing for iterative development and frequent feedback. Waterfall may be more suitable for projects with well-defined requirements and rigid deadlines.
Explore Hybrid Approaches: Consider adopting a hybrid approach that combines elements of Agile and Waterfall methodologies to leverage their respective strengths. Hybrid approaches offer flexibility and customization, allowing you to tailor the development process to suit your project’s unique needs.
Seek Expert Advice: Consult with project management professionals, Agile coaches, and industry experts to gain insights and recommendations on selecting the most appropriate approach for your project.
Document the Decision: Document the rationale behind your choice of development approach, including the factors considered, key stakeholders involved, and expected benefits. Ensure that all project team members are aware of the selected approach and understand their roles and responsibilities.
By carefully considering these factors and engaging stakeholders in the decision-making process, you can choose an approach to development or obtaining results that aligns with your project’s goals, constraints, and context. Remember that the choice of approach may evolve over time as the project progresses and new information becomes available.
Project life cycle and phases
In the context of project management, the terms “predictive” and “adaptive” refer to different approaches to managing the project life cycle. Here’s how they relate to the project life cycle and its phases:
- Predictive Life Cycle:
- The predictive life cycle, also known as the traditional or waterfall approach, follows a sequential, linear progression through predefined phases.
- Each phase is typically well-defined with specific deliverables and objectives, and the project progresses from one phase to the next in a predetermined order.
- The phases are planned in advance, and changes to scope, requirements, or deliverables are minimized once the project execution begins.
- Examples of phases in a predictive life cycle may include initiation, planning, execution, monitoring and controlling, and closure.
2. Adaptive Life Cycle:
- The adaptive life cycle, also known as Agile or iterative approach, is characterized by flexibility, responsiveness, and iterative development.
- Instead of following a rigid sequence of phases, the adaptive life cycle allows for continuous refinement and adaptation based on feedback and changing requirements.
- Projects are divided into smaller iterations or increments, with each iteration delivering a usable product or increment of value.
- Feedback from stakeholders is solicited and incorporated regularly, allowing for adjustments to be made throughout the project’s lifecycle.
- Examples of approaches within an adaptive life cycle include Scrum, Kanban, and Extreme Programming (XP).
Both predictive and adaptive life cycles have their advantages and are suitable for different types of projects:
- Predictive Life Cycle: Suitable for projects with well-defined requirements, stable scope, and low uncertainty. It provides a structured approach and is often used in industries with strict regulatory requirements or when the project scope can be clearly defined upfront.
- Adaptive Life Cycle: Suitable for projects with evolving requirements, high uncertainty, and a need for rapid adaptation. It allows for flexibility, encourages collaboration, and is well-suited for innovative projects where requirements may change frequently.
In practice, many projects may incorporate elements of both predictive and adaptive approaches, using a hybrid approach to leverage the benefits of each based on the project’s specific needs and characteristics.
If you liked the article, you can support the author by clapping below 👏🏻 Thanks for reading!
