Key Agile Practices and Techniques

This guide is intended to break down key Agile Tools and Techniques from Exam Outline into easily digestible elements, helping practitioners of all levels navigate and apply these practices to their daily work.

Whether you’re new to Agile or looking to refresh your knowledge, this post will serve as a valuable resource to enhance your understanding and application of Agile techniques.

Agile Analysis and Design

• Product Roadmap – A high-level plan for product development.
  • High-level plan for product development.
  • Key milestones and deliverables mapped over time.
  • Aligns product vision with customer needs.
  • Adjusts based on evolving market demands.
  • Visual representation for stakeholders and team alignment.
• User Stories/Backlog – Short, descriptive requirements from the user’s perspective.
  • Short, descriptive requirements from the user’s perspective.
  • Prioritized by business value and urgency.
  • Continuously refined to adapt to changing priorities.
  • Used to define and break down work for each sprint.
  • Includes acceptance criteria and estimates.
• Story Maps – Visual representation of user stories organized by functionality.
  • Visual representation of user stories organized by functionality.
  • Helps prioritize and manage workflow.
  • Provides an understanding of the product’s functionality.
  • Allows for sequencing of features across sprints.
  • Focus on the customer journey to identify critical features.
• Progressive Elaboration Wireframes – Early-stage designs that evolve as more is learned.
  • Early-stage designs that evolve as more is learned.
  • Iterative sketches that guide feature development.
  • Serves as prototypes for user interface (UI) design.
  • Reduces ambiguity by visualizing product features.
  • Refined over time based on feedback and evolving requirements.
• Chartering – Creation of project vision, scope, and goals.
  • Creation of project vision, scope, and goals.
  • Defines roles and responsibilities of stakeholders.
  • Establishes governance and decision-making processes.
  • Clarifies boundaries and expectations for the project.
  • A tool to align teams on overall objectives.
• Personas – Fictional characters representing target users.
  • Fictional characters representing target users.
  • Based on research to reflect user needs and behaviors.
  • Helps to focus on user-centric design decisions.
  • Ensures the product meets the needs of different user types.
  • Provides empathy to the team by understanding user challenges.
• Modeling – Creating abstract representations of a system or process.
  • Creating abstract representations of a system or process.
  • Helps visualize relationships between system components.
  • Can include diagrams, flowcharts, and process models.
  • Used to communicate design ideas with stakeholders.
  • Serves as a tool for analysis and problem-solving.
• Workshops – Collaborative sessions for knowledge sharing and problem-solving.
  • Collaborative sessions for knowledge sharing and problem-solving.
  • Involve cross-functional teams and stakeholders.
  • Encourages active participation and brainstorming.
  • Used for decision-making and consensus building.
  • Can focus on refining product vision, backlog, or designs.
• Learning Cycle Plan – Plan for continuous learning and improvement.
  • Plan for continuous learning and improvement.
  • Iterative feedback loops to adapt to changes.
  • Regularly scheduled reviews of performance and processes.
  • Focuses on team development and knowledge sharing.
  • Adaptation of strategies based on learning outcomes.
• Collaboration Games – Structured activities to enhance team communication and cooperation.
  • Structured activities to enhance team communication and cooperation.
  • Promotes creativity and problem-solving.
  • Can be used for planning, retrospectives, and brainstorming.
  • Designed to foster team bonding and alignment.
  • Examples include the “Speed Boat” or “Product Box” game.

---

Agile Estimation

• Relative Sizing/Story Points/T-Shirt Sizing – Assigning size to user stories based on relative effort.
  • Assigning size to user stories based on relative effort.
  • T-shirt sizing uses small, medium, large for simplicity.
  • Story points offer a more precise measure of effort.
  • Encourages consensus-based estimation with the team.
  • Provides an abstraction from hours to reduce bias.
• Wide Band Delphi/Planning Poker – Expert consensus technique where estimations are anonymously shared.
  • Expert consensus technique where estimations are anonymously shared.
  • Planning Poker uses cards to encourage participation and prevent bias.
  • Aims to arrive at a group estimate through discussion.
  • Reduces estimation errors from individual biases.
  • Used to foster team collaboration and transparency.
• Affinity Estimating – Grouping similar stories for quick estimation.
  • Grouping similar stories for quick estimation.
  • Stories are sorted based on perceived size and complexity.
  • Focuses on speed over individual estimates.
  • Often used for large backlogs or initial project estimates.
  • Helps in generating a rough estimate with minimal effort.
• Ideal Time – Estimating effort based on an ideal, uninterrupted work period.
  • Estimating effort based on an ideal, uninterrupted work period.
  • Focuses on what would be achievable without distractions.
  • Can be converted into story points or other relative measures.
  • Helps to assess the true capacity of the team.
  • Assumes no time for interruptions, meetings, or context-switching.

---

Communications

• Information Radiator/Team Space/Agile Tooling – Visual boards and charts to track project progress.
  • Visual boards and charts to track project progress.
  • Information radiators provide real-time updates on the project.
  • Team space refers to a shared area for collaboration and interaction.
  • Agile tools like Jira or Trello aid in backlog management.
  • Promotes transparency and team alignment.
• Osmotic Communications for Co-located and/or Distributed Teams -Communication flow through proximity or casual interactions.
  • Communication flow through proximity or casual interactions.
  • Encourages constant sharing of information in the workspace.
  • Can be adapted for virtual teams using collaborative tools.
  • Reduces the need for formal meetings by fostering organic sharing.
  • Builds stronger relationships within distributed teams.
• Two-Way Communications (Trustworthy, Conversation Driven) -Open dialogue between team members and stakeholders.
  • Open dialogue between team members and stakeholders.
  • Focus on active listening and mutual respect.
  • Ensures that feedback is actionable and relevant.
  • Builds trust and transparency within teams.
  • Supports continuous improvement and adaptation.
• Social Media Based Communication: Uses platforms like Slack or Microsoft Teams for informal interaction
  • Uses platforms like Slack or Microsoft Teams for informal interaction.
  • Provides fast, asynchronous communication channels.
  • Encourages team collaboration beyond formal meetings.
  • Allows for real-time sharing of information and quick feedback.
  • Fosters community building and knowledge sharing.
• Active Listening: Fully focusing on the speaker to understand their message.
  • Fully focusing on the speaker to understand their message.
  • Involves asking clarifying questions and summarizing key points.
  • Encourages better communication and reduces misunderstandings.
  • Builds stronger relationships within the team.
  • Helps to ensure that all voices are heard.

---

Metrics

• Velocity/Throughput/Productivity/Cycle Time – Velocity measures the amount of work completed in a sprint.
  • Velocity measures the amount of work completed in a sprint.
  • Throughput measures the number of stories or tasks delivered.
  • Productivity looks at work output relative to input.
  • Cycle time measures the time taken from start to completion of a task.
  • Helps identify bottlenecks and inefficiencies in workflows.
• Lead Time – The total time taken from the request of a feature to its delivery.
  • The total time taken from the request of a feature to its delivery.
  • Provides insights into process efficiency.
  • Used to forecast project delivery times.
  • A critical metric for Agile planning and release cycles.
  • Influenced by the complexity of tasks and bottlenecks in the system.
• EVM for Agile Projects/Defect Rate – Earned Value Management (EVM) assesses project performance against scope, cost, and schedule.
  • Earned Value Management (EVM) assesses project performance against scope, cost, and schedule.
  • Measures actual progress and forecasts future trends.
  • Defect rate measures the number of defects relative to the product delivered.
  • A high defect rate indicates potential quality issues.
  • Helps with managing project scope and mitigating risk.
• Approved Iterations – Iterations that have been formally signed off or accepted.
  • Iterations that have been formally signed off or accepted.
  • Measures progress toward project goals.
  • Used to ensure alignment with stakeholder expectations.
  • Reflects team’s ability to meet iteration goals.
  • Can also indicate scope changes or project delays.
• Work in Progress – Regular reviews ensure progress is on track and feedback is gathered.
  • Tracks the number of tasks or features being worked on simultaneously.
  • Excessive WIP can cause bottlenecks and reduce efficiency.
  • Helps teams understand their capacity and avoid overcommitment.
  • Provides insights into team workflow and process limitations.
  • Often used in Kanban systems to limit work items.

---

Planning, Monitoring, and Adapting

• Reviews/Kanban Board/Task Board/Timeboxing – Iteration planning focuses on delivering work in smaller chunks.
  • Regular reviews ensure progress is on track and feedback is gathered.
  • Kanban boards visualize the flow of work.
  • Task boards help teams track individual tasks and progress.
  • Timeboxing limits the amount of time dedicated to specific tasks.
  • Ensures that work stays focused and deadlines are met.
• Iteration and Release Planning/Variance and Trend Analysis/WIP Limits
  • Iteration planning focuses on delivering work in smaller chunks.
  • Release planning organizes larger deliveries into versions or milestones.
  • Variance and trend analysis track progress against original plans.
  • WIP limits prevent teams from overcommitting and reduce multitasking.
  • Ensures continuous improvement through regular feedback.
• Daily Synchronization Meetings
  • Short, daily meetings for team members to align on priorities.
  • Focus on progress, challenges, and plans for the day.
  • Promotes team coordination and accountability.
  • Helps identify blockers early and ensures timely adjustments.
  • Encourages rapid communication and problem-solving.
• Burn Down/Up Charts/Cumulative Flow Diagrams/Backlog Grooming/Refinement
  • Burn down charts show work remaining in an iteration or release.
  • Burn up charts track the progress of completed work over time.
  • Cumulative flow diagrams visualize the status of work across stages.
  • Backlog grooming ensures the backlog remains prioritized and up-to-date.
  • Refinement involves breaking down backlog items into smaller, actionable tasks.
• Product-Feedback Loop
  • A continuous cycle where feedback from users informs development.
  • Helps teams adapt features to meet customer needs.
  • Ensures that the product aligns with business goals and user expectations.
  • Provides actionable insights for the next iteration or sprint.
  • Enhances collaboration between development teams and stakeholders.

---

Process Improvement

• Kaizen
  • Continuous, incremental improvement process.
  • Involves all team members in identifying and solving issues.
• Focuses on reducing waste and increasing efficiency.
• Regular small improvements can lead to significant changes.
• Often integrated into daily work routines.
• The Five WHYs
  • A technique used to explore the root cause of a problem.
  • Involves asking “why” five times to trace the cause of an issue.
  • Helps teams identify underlying issues rather than symptoms.
  • Encourages deeper thinking and analysis.
  • Promotes a culture of problem-solving and root-cause resolution.
• Retrospectives/Intraspectives
  • Retrospectives focus on reviewing team performance and processes.
  • Intraspectives are reflections within an individual or subgroup.
  • Used to identify what went well and areas for improvement.
  • Encourages continuous learning and adjustment.
  • Helps foster a culture of openness and trust within teams.
• Process Tailoring/Hybrid Models
  • Tailoring processes to fit specific project needs or constraints.
  • Hybrid models combine Agile practices with traditional methods.
  • Adapts Agile to various project environments and organizational cultures.
  • Customizes workflows to improve efficiency and effectiveness.
  • Balances flexibility with the need for structure and documentation.
• Value Stream Mapping
  • A visual representation of the flow of materials and information.
  • Identifies value-adding and non-value-adding activities.
  • Helps identify bottlenecks and inefficiencies in processes.
  • Used to optimize workflow and reduce waste.
  • Focuses on improving end-to-end delivery of value.

---

Product Quality

• Frequent Verification and Validation
  • Ensures product quality through continuous testing and feedback.
  • Verification checks if the product is built correctly (according to requirements).
  • Validation ensures the right product is being built to meet user needs.
  • Helps identify issues early in the development cycle.
  • Drives quality improvements and customer satisfaction.
• Definition of Done
  • A clear, agreed-upon set of criteria for when a task or feature is complete.
  • Ensures consistency and clarity across the team.
  • Prevents incomplete or low-quality work from being released.
  • Includes both technical and non-technical requirements.
  • Promotes accountability and transparency.
• Continuous Integration
  • A practice where code changes are frequently integrated into the shared repository.
  • Ensures early detection of integration issues.
  • Reduces the risk of defects by testing continuously.
  • Improves collaboration and reduces development time.
  • Facilitates quicker feedback loops for developers.
• Testing, Including Exploratory and Usability
  • Regular automated and manual testing to ensure product quality.
  • Exploratory testing involves unscripted testing based on tester knowledge.
  • Usability testing evaluates the product’s user-friendliness and effectiveness.
  • Continuous testing allows for early bug detection and fixes.
  • Ensures the product meets both functional and non-functional requirements.

---

Risk Management

• Risk Adjusted Backlog
  • Backlog items are prioritized based on risk and potential impact.
  • Helps address high-risk items early in the project.
  • Prioritization incorporates both business value and risk exposure.
  • Provides better visibility of risks throughout the development process.
  • Encourages proactive risk mitigation strategies.
• Risk Burn Down Graphs
  • Visualize the reduction of risks over time.
  • Track how identified risks are mitigated throughout the project.
  • Help teams focus on high-priority risks.
  • Provide insights into the overall risk exposure of the project.
  • Highlight trends and areas needing further attention.
• Risk-Based Spike
  • Temporary research or investigation to reduce uncertainty around high-risk areas.
  • Aimed at gathering enough information to proceed with confidence.
  • Helps validate assumptions and inform decisions.
  • Often results in the adjustment of product design or approach.
  • Mitigates project risks by resolving knowledge gaps early.
• Architectural Spike
  • A time-boxed investigation into architectural decisions.
  • Focuses on understanding technical uncertainties or challenges.
  • Helps to identify the most viable solutions for complex technical problems.
  • Typically used when new technologies or approaches are being considered.
  • Reduces the chance of costly architectural changes later in the project.

---

Value-Based Prioritization

• ROI/NPV/IRR
  • Return on Investment (ROI) measures the profitability of an investment.
  • Net Present Value (NPV) calculates the value of future cash flows.
  • Internal Rate of Return (IRR) measures the profitability of potential investments.
  • These metrics help prioritize initiatives with the highest financial value.
  • Provides a clear way to compare different project opportunities.
• Compliance
  • Ensuring that the project adheres to regulatory, legal, or industry standards.
  • Can affect product design, development processes, and delivery schedules.
  • Ensures the project meets external stakeholder expectations.
  • Often drives prioritization of features for compliance with laws.
  • Failure to comply can result in penalties, reputational damage, or delays.
• Customer Valued Prioritization
  • Prioritizing work based on customer feedback, needs, and pain points.
  • Ensures the most valuable features are delivered first.
  • Helps teams stay focused on delivering customer-centric outcomes.
  • Aligns the product vision with actual market demands.
  • Incorporates both current and potential customer needs.
• Requirements Reviews
  • Regular evaluations of requirements to ensure they are complete and accurate.
  • Helps identify changes, omissions, or ambiguities early.
  • Encourages communication between stakeholders to clarify expectations.
  • Reduces scope creep by refining requirements as the project evolves.
  • Ensures alignment between business goals and product features.
• Minimal Viable Product (MVP)
  • A version of the product with the smallest feature set necessary to satisfy early adopters.
  • Designed to test assumptions and gather customer feedback.
  • Focuses on delivering core value quickly and efficiently.
  • Reduces time to market and minimizes waste.
  • Provides a base for iterative development and improvement.
• Minimal Marketable Feature (MMF)
  • The smallest set of features that provide value to customers.
  • Focuses on delivering value rather than features.
  • Helps prioritize what to build next based on customer needs.
  • Ensures that each release is impactful and contributes to business goals.
  • Provides a scalable approach for progressive delivery.
• Relative Prioritization/Ranking
  • Comparing items against each other to determine priority.
  • Helps in deciding which features or tasks should be worked on next.
  • Balances business needs with technical feasibility.
  • A method of ranking backlog items based on value, risk, and urgency.
  • Promotes transparency and alignment among stakeholders.
• MoSCoW
  • A prioritization technique that categorizes items as Must-have, Should-have, Could-have, or Won’t-have.
  • Helps teams focus on critical features and functionalities.
  • Ensures that important items are delivered first.
  • Facilitates communication between stakeholders about priorities.
  • Provides a structured way to make trade-offs.
• Kano Analysis
  • A model used to prioritize features based on customer satisfaction.
  • Categorizes features into Basic, Performance, and Excitement attributes.
  • Helps identify which features will delight customers and which are expected.
  • Provides insights into how to maximize customer satisfaction.
  • Guides prioritization by balancing value, feasibility, and cost.

By embracing Agile practices and understanding their core components, teams can achieve higher productivity, better communication, and more effective decision-making.

Whether it’s through improving product quality, managing risks, or refining processes, these techniques empower teams to be adaptable and responsive to change.

Keep this guide as a handy reference to ensure your Agile journey stays on track and leads to continuous improvement and success.