Comprehensive Study Guide for the Agile Practice Guide
Introduction to the Agile Practice Guide
Objective and Vision: The Agile Practice Guide was created as a collaborative effort between the Project Management Institute (PMI) and Agile Alliance. Its vision is to equip project teams with situational guidelines, tools, and a comprehensive understanding of various agile techniques to enable superior results.
Scope of Application: While originating in the software industry, agile has permeated manufacturing, education, healthcare, and other diverse fields. The guide is specifically designed to work hand-in-hand with A Guide to the Project Management Body of Knowledge (PMBOK® Guide) – Sixth Edition.
Target Audience: Essential for anyone interested in agile, particularly project managers accustomed to traditional environments who seek to adapt to agile methodologies.
Industry Expansion: Organizations value agile as a competitive advantage in fast-paced, complex environments where they must be quicker, more responsive, and flexible.
Definable Work vs. High-Uncertainty Work
Definable Work Projects: Characterized by clear procedures that have been successful in previous, similar projects (e.g., manufacturing a car or an appliance after the design is fixed). These projects have low levels of execution uncertainty and risk.
High-Uncertainty Work Projects: Involves new designs, problem-solving, and exploratory work (e.g., software systems engineering, product design). It requires subject matter experts (SMEs) to collaborate to create solutions.
Characteristics of Uncertainty: High rates of change, complexity, and risk. Traditional predictive approaches often fail here because they rely on upfront requirements and rigid change control. Agile approaches explore feasibility in short cycles to adapt based on feedback.
The Rise of Knowledge Work: As more definable work becomes automated, project teams are increasingly undertaking high-uncertainty work that requires agile techniques.
The Agile Manifesto and Mindset
The Agile Mindset: Ahmed Sidky’s model describes agile as a mindset defined by the four values of the Agile Manifesto, guided by twelve principles, and manifested through various practices.
Four Core Values of the Agile Manifesto (2001):
Individuals and interactions over processes and tools.
Working software over comprehensive documentation.
Customer collaboration over contract negotiation.
Responding to change over following a plan.
Twelve Principles of Agile:
Highest priority is customer satisfaction through early and continuous delivery of valuable software.
Welcome changing requirements, even late in development.
Deliver working software frequently (weeks to months, with a preference for shorter timescales).
Business people and developers must work together daily.
Build projects around motivated individuals; provide support and trust.
Face-to-face conversation is the most effective method for conveying information.
Working software is the primary measure of progress.
Agile processes promote sustainable development; maintaining a constant pace indefinitely.
Continuous attention to technical excellence and good design enhances agility.
Simplicity—the art of maximizing the amount of work not done—is essential.
Best architectures and designs emerge from self-organizing teams.
Regular reflection on effectiveness, followed by tuning and adjusting behavior.
Lean and the Kanban Method
Lean Heritage: Agile and the Kanban Method are descendents of lean thinking. They share concepts like focusing on value, small batch sizes, and the elimination of waste.
Kanban Method Definition: A system for scheduling inventory control and replenishment, inspired by lean manufacturing (applied at Toyota in 1953). It is less prescriptive than other agile approaches and acts as a "start-where-you-are" method.
Kanban Core Properties:
Visualize the workflow.
Limit Work in Progress (WIP).
Manage flow.
Make process policies explicit.
Implement feedback loops.
Improve collaboratively.
Project Life Cycles and Selection
Predictive Life Cycle: A traditional, sequential approach where planning occurs upfront, and execution is a single pass.
Iterative Life Cycle: Allows feedback for unfinished work to improve and modify it through successive prototypes or proofs of concept.
Incremental Life Cycle: Provides finished deliverables that the customer can use immediately.
Agile Life Cycle: Both iterative and incremental; work is refined and delivered frequently.
Hybrid Life Cycle: A combination of predictive, iterative, incremental, and/or agile approaches. Examples include:
Agile development followed by a predictive rollout.
Combined agile and predictive approach simultaneously (certain components agile, others predictive).
Predictive approach with small agile components to handle high-risk areas.
Stacey Complexity Model Factors: Projects are assessed based on Requirements Uncertainty and Technical Degree of Uncertainty. As uncertainty increases, adaptive (agile) approaches work better than linear ones.
Creating an Agile Environment: Servant Leadership
Definition of Servant Leadership: The practice of leading through service to the team, addressing their needs and development to enable high performance.
Core Responsibilities of a Servant Leader:
Purpose: Defining the "why" for the project.
People: Creating an environment where everyone can succeed.
Process: Focusing on results rather than following a "perfect" process.
Facilitation: Shifting from coordination to collaboration facilitation.
Removing Impediments: Partnering with departments (finance, change control, audit) to streamline bottleneck processes.
Role Evolution for Project Managers: In agile, project managers shift from being the center of coordination to being servant leaders who focus on coaching, fostering collaboration, and aligning stakeholder needs.
Team Composition and Success Attributes
Agile Team Size: Ideally ranges from three to nine members.
Dedicated Team Members: 100% dedication is preferred. Task-switching between two projects leads to productivity losses of to .
Colocation and Workspaces: Agile teams benefit from working in the same room. For distributed teams, tools like "fishbowl windows" (long-lived video links) and "remote pairing" help simulate colocation.
T-Shaped People vs. I-Shaped People:
I-Shaped: Deep specialization in one domain but rarely contributes elsewhere.
T-Shaped: Expertise in one area supplemented by less-developed skills in other areas and strong collaboration skills.
Broken Comb/Paint-Drip: Variations in depth of specialization across multiple skills.
Cross-Functional Teams: Consist of members with all skills (designers, developers, testers) needed to produce working results without external dependencies.
Delivering in an Agile Environment: Common Practices
Agile Chartering: Answers why the project is being done, who benefits, what "done" means, and how the team will work together (social contract).
Daily Standups: Timeboxed to 15 minutes. In iteration-based agile, members answer: what was completed, what is planned next, and what are the impediments.
Backlog Refinement: The progressive elaboration of requirements. Projects strive to spend no more than 1 hour per week on refinement to maximize work time.
Retrospectives: The most important practice. It involves looking at qualitative (feelings) and quantitative (metrics) data to find root causes and design countermeasures. Action items should be limited to the team's capacity to resolve them in the next period.
Spikes: Short intervals (timeboxed research/experiments) to prove viability, often used when the product owner is unsure of dependencies or risks.
Agile Execution and Value Delivery
Continuous Integration: Frequent incorporation of work into the whole product, followed by retesting.
Test-Driven Development (TDD): Defining tests before work begins so WIP is validated continuously.
Behavior-Driven Development (BDD): Using test-first principles and English-like scripts to design systems.
Minimum Viable Product (MVP): Delivery of a subset of the overall solution to allow customers to provide early feedback.
Acceptance Test-Driven Development (ATDD): The entire team discusses acceptance criteria before delivery to ensure the team writes only enough code to meet those criteria.
Measurements in Agile Projects
Predictive vs. Empirical: Agile favors empirical data over predictive metrics (like percent done).
Waterfall/Watermelon Projects: Projects that appear "green" on a status report until the very end when they suddenly turn "red" due to integration surprises.
Velocity: The sum of story point sizes completed in an iteration. Helps predict project duration based on the remaining backlog.
Flow-Based Metrics:
Lead Time: Total time from adding an item to the board to completion.
Cycle Time: Time required to process an item once work starts.
Response Time: Time an item waits in the "Ready" queue before work starts.
Agile Earned Value Equations:
Example: If a team planned 30 points and completed 25, .
Organizational Considerations for Agility
Organizational Change Management (OCM): Essential for addressing hurdles in transitioning. Accelerating delivery tests the organization's ability to incorporate output.
Culture: "Culture eats strategy for breakfast." Success depends on the commitment of the people. Agile requires an environment of safety, transparency, and honesty.
Agile Project Management Office (PMO):
Value-Driven: Operates like a consulting business tailoring efforts to project needs.
Invitation-Oriented: Invites those interested to engage with services rather than mandating them.
Multidisciplinary: Conversant in organizational design and change management.
Procurement and Contracts:
Fixed-Price Increments: Decomposing scope into microdeliverables (user stories).
Not-to-Exceed T&M: Setting a budget cap while allowing scope flexibility.
Early Cancellation: Allowing customers to buy out the remainder of a project for a fee once sufficient value is reached.
Scaling and Coordination
Frameworks for Scaling:
Scrum of Scrums (SoS): Representatives from multiple teams meet to coordinate work and remove blockers.
Scaled Agile Framework (SAFe®): Focuses on patterns for scaling across the entire enterprise.
Large Scale Scrum (LeSS): Designed to retain the simplicity of Scrum while scaling to multiple teams.
Disciplined Agile (DA): A process decision framework focusing on goal-driven, people-first, and enterprise-aware results.