• Question: I am the cornerstone of agile, breaking work into manageable chunks. What am I?
• Answer: User Story
• Question: I help teams visualize their work and progress, standing tall with colorful sticky notes. What do they call me?
• Answer: Kanban Board
• Question: I’m a daily gathering where teams sync up, discuss roadblocks, and plan the day ahead. What’s my name?
• Answer: Daily Standup
• Question: I measure the team’s velocity, guiding them on their journey. What metric am I?
• Answer: Burndown Chart
• Question: I encourage continuous improvement by reflecting on successes and failures. What ritual am I?
• Answer: Retrospective
• Question: I represent the prioritized list of work items, guiding the team towards their goal. What list am I?
• Answer: Product Backlog
• Question: I am a framework that values individuals and interactions over processes and tools. What’s my name?
• Answer: Agile Manifesto
• Question: I ensure that the team is building the right thing, validating assumptions early and often. What practice am I?
• Answer: User Acceptance Testing
• Question: I’m a technique for breaking down complex tasks into smaller, more manageable parts. What technique am I?
• Answer: Decomposition
• Question: I’m a strategy for releasing software frequently, delivering value to users incrementally. What strategy am I?
• Answer: Continuous Deployment
• Question: I facilitate collaboration between development and operations teams, ensuring seamless delivery. What practice am I?
• Answer: DevOps
• Question: I’m a technique for estimating the size of work items using relative comparison. What technique am I?
• Answer: Planning Poker
• Question: I advocate for self-organizing teams, empowering individuals to make decisions and take ownership. What principle am I?
• Answer: Empirical Process Control
• Question: I encourage frequent feedback from stakeholders, enabling course correction and validation. What practice am I?
• Answer: Iterative Development
• Question: I’m a mechanism for limiting work in progress, optimizing flow and reducing multitasking. What mechanism am I?
• Answer: WIP Limit
• Question: I promote transparency by making work visible and understandable to all stakeholders. What concept am I?
• Answer: Information Radiator
• Question: I’m a technique for breaking down work items into smaller, more manageable tasks. What technique am I?
• Answer: Work Breakdown Structure
• Question: I facilitate rapid feedback loops by automating the testing and deployment process. What practice am I?
• Answer: Continuous Integration
• Question: I emphasize collaboration, communication, and trust within cross-functional teams. What value am I?
• Answer: Individuals and Interactions

• Question: I’m a technique for breaking down large projects into smaller, more manageable iterations. What technique am I?
• Answer: Iterative Development
• Question: I represent the maximum amount of time a task should take, guiding teams towards efficiency. What am I?
• Answer: Timebox
• Question: I’m a ceremony where teams review their progress and adjust their course. What’s my name?
• Answer: Sprint Review
• Question: I’m a method for prioritizing work based on value and risk. What method am I?
• Answer: MoSCoW Method
• Question: I promote flexibility and responsiveness to change, even late in the development process. What principle am I?
• Answer: Responding to Change over Following a Plan
• Question: I’m a strategy for breaking down silos and fostering collaboration across teams. What strategy am I?
• Answer: Cross-Functional Teams
• Question: I ensure that the team is delivering working software at the end of each iteration. What am I?
• Answer: Increment
• Question: I’m a technique for identifying potential risks and mitigating them early in the project. What technique am I?
• Answer: Risk Assessment
• Question: I’m a ceremony where the team plans their work for the upcoming iteration. What’s my name?
• Answer: Sprint Planning
• Question: I emphasize the importance of simplicity in design and development. What principle am I?
• Answer: Simplicity–the Art of Maximizing the Amount of Work Not Done
• Question: I facilitate frequent communication and collaboration through short, focused meetings. What am I?
• Answer: Daily Scrum
• Question: I’m a framework for scaling agile practices across large organizations. What framework am I?
• Answer: Scaled Agile Framework (SAFe)
• Question: I encourage teams to deliver a potentially shippable product increment at the end of each sprint. What principle am I?
• Answer: Deliver Working Software Frequently
• Question: I’m a technique for breaking down complex tasks into smaller, more manageable parts. What technique am I?
• Answer: Decomposition
• Question: I emphasize the importance of customer collaboration throughout the development process. What principle am I?
• Answer: Customer Collaboration over Contract Negotiation
• Question: I’m a metric for measuring the team’s productivity and efficiency. What metric am I?
• Answer: Velocity
• Question: I ensure that the team is building the right thing by validating assumptions with real users. What practice am I?
• Answer: User Testing
• Question: I’m a technique for breaking down work into smaller, more manageable tasks. What technique am I?
• Answer: Task Breakdown
• Question: I emphasize the importance of self-organizing teams in achieving project success. What principle am I?
• Answer: Build Projects around Motivated Individuals
• Question: I’m a strategy for reducing risk and uncertainty by delivering a minimal viable product early. What strategy am I?
• Answer: Minimum Viable Product (MVP)

Another Agile riddles

• Question: I’m a practice that involves breaking down barriers between development and operations teams. What practice am I?
• Answer: DevOps
• Question: I’m a technique for managing work in progress to optimize flow and minimize bottlenecks. What technique am I?
• Answer: Kanban
• Question: I’m a framework that encourages teams to inspect and adapt their processes continuously. What framework am I?
• Answer: Scrum
• Question: I’m a ceremony where the team reflects on their performance and identifies areas for improvement. What’s my name?
• Answer: Sprint Retrospective
• Question: I’m a principle that values working software as the primary measure of progress. What principle am I?
• Answer: Working Software over Comprehensive Documentation
• Question: I’m a technique for estimating the effort required to complete a task using story points. What technique am I?
• Answer: Agile Estimation
• Question: I’m a strategy for ensuring that the team has a shared understanding of project requirements. What strategy am I?
• Answer: User Story Mapping
• Question: I’m a metric for measuring the team’s ability to deliver value to customers consistently. What metric am I?
• Answer: Cycle Time
• Question: I’m a technique for prioritizing work based on the value it delivers to the customer. What technique am I?
• Answer: Value-Based Prioritization
• Question: I’m a practice that involves breaking down work items into smaller, more manageable tasks. What practice am I?
• Answer: Task Decomposition
• Question: I’m a principle that emphasizes the importance of delivering working software frequently. What principle am I?
• Answer: Deliver Working Software Frequently
• Question: I’m a technique for ensuring that the team has a shared understanding of project goals and objectives. What technique am I?
• Answer: Vision Statement
• Question: I’m a strategy for reducing risk by delivering a small, working product increment early in the project. What strategy am I?
• Answer: Minimum Marketable Product (MMP)
• Question: I’m a metric for measuring the amount of work completed in each iteration. What metric am I?
• Answer: Sprint Velocity
• Question: I’m a technique for visualizing the flow of work and identifying bottlenecks in the process. What technique am I?
• Answer: Value Stream Mapping
• Question: I’m a principle that emphasizes the importance of allowing teams to self-organize and make decisions. What principle am I?
• Answer: Self-Organizing Teams
• Question: I’m a practice that involves automating repetitive tasks to improve efficiency and reduce errors. What practice am I?
• Answer: Continuous Integration
• Question: I’m a technique for breaking down work items into smaller, more manageable tasks. What technique am I?
• Answer: Work Breakdown Structure (WBS)
• Question: I’m a strategy for delivering value to customers early and often by releasing small, incremental updates. What strategy am I?
• Answer: Continuous Delivery

• Question: I’m a practice that involves breaking down large projects into smaller, more manageable tasks. What practice am I?
• Answer: Agile Decomposition
• Question: I’m a technique for visualizing and tracking the progress of work items through various stages. What technique am I?
• Answer: Agile Board
• Question: I’m a principle that emphasizes the importance of responding to change over following a plan. What principle am I?
• Answer: Agile Adaptability
• Question: I’m a strategy for delivering value to customers by releasing small, incremental updates frequently. What strategy am I?
• Answer: Agile Iteration
• Question: I’m a ceremony where the team demonstrates the working software to stakeholders. What’s my name?
• Answer: Agile Showcase
• Question: I’m a metric for measuring the team’s ability to deliver value to customers consistently. What metric am I?
• Answer: Agile Efficiency
• Question: I’m a technique for managing and prioritizing the backlog based on value and effort. What technique am I?
• Answer: Agile Prioritization
• Question: I’m a principle that values face-to-face communication as the most efficient and effective method. What principle am I?
• Answer: Agile Communication
• Question: I’m a practice that involves continuously testing and validating assumptions with real users. What practice am I?
• Answer: Agile Validation
• Question: I’m a technique for breaking down work items into smaller, more manageable tasks. What technique am I?
• Answer: Agile Breakdown
• Question: I’m a strategy for ensuring that the team delivers a potentially shippable product increment at the end of each iteration. What strategy am I?
• Answer: Agile Delivery
• Question: I’m a principle that emphasizes the importance of allowing motivated individuals to make decisions. What principle am I?
• Answer: Agile Empowerment
• Question: I’m a technique for managing and resolving conflicts within the team effectively. What technique am I?
• Answer: Agile Conflict Resolution
• Question: I’m a strategy for minimizing risk and uncertainty by delivering small, incremental changes. What strategy am I?
• Answer: Agile Risk Reduction
• Question: I’m a ceremony where the team plans their work for the upcoming iteration. What’s my name?
• Answer: Agile Planning
• Question: I’m a principle that emphasizes the importance of simplicity in design and development. What principle am I?
• Answer: Agile Simplicity
• Question: I’m a technique for ensuring that the team has a shared understanding of project requirements. What technique am I?
• Answer: Agile Collaboration
• Question: I’m a strategy for delivering value to customers early and often by releasing small, incremental updates. What strategy am I?
• Answer: Agile Delivery
• Question: I’m a practice that involves breaking down work items into smaller, more manageable tasks. What practice am I?
• Answer: Agile Breakdown

Getting over with Agile riddles

• Question: I’m a practice that involves continuous integration of code changes to ensure software stability. What practice am I?
• Answer: Agile Continuous Integration
• Question: I’m a technique for estimating the effort required to complete a task using a Fibonacci sequence. What technique am I?
• Answer: Agile Fibonacci Estimation
• Question: I’m a principle that emphasizes the importance of delivering value to customers early and often. What principle am I?
• Answer: Agile Early Value Delivery
• Question: I’m a strategy for ensuring that the team delivers a potentially shippable product at the end of each iteration. What strategy am I?
• Answer: Agile Incremental Delivery
• Question: I’m a ceremony where the team reflects on their performance and identifies areas for improvement. What’s my name?
• Answer: Agile Retrospective
• Question: I’m a metric for measuring the team’s progress towards completing the project scope. What metric am I?
• Answer: Agile Burnup Chart
• Question: I’m a technique for prioritizing work based on the value it delivers to the customer. What technique am I?
• Answer: Agile Value-Based Prioritization
• Question: I’m a principle that emphasizes the importance of face-to-face communication within the team. What principle am I?
• Answer: Agile Face-to-Face Communication
• Question: I’m a practice that involves breaking down work items into smaller, more manageable tasks. What practice am I?
• Answer: Agile Task Breakdown
• Question: I’m a strategy for managing project risks by delivering incremental value early and often. What strategy am I?
• Answer: Agile Risk Management
• Question: I’m a principle that emphasizes the importance of adapting to changing requirements throughout the project. What principle am I?
• Answer: Agile Adaptability
• Question: I’m a technique for visualizing and prioritizing work items based on their dependencies. What technique am I?
• Answer: Agile Dependency Mapping
• Question: I’m a strategy for ensuring that the team has a shared understanding of project goals and objectives. What strategy am I?
• Answer: Agile Vision Alignment
• Question: I’m a ceremony where the team plans their work for the upcoming iteration. What’s my name?
• Answer: Agile Sprint Planning
• Question: I’m a principle that emphasizes the importance of delivering working software frequently. What principle am I?
• Answer: Agile Frequent Delivery
• Question: I’m a technique for managing and resolving conflicts within the team effectively. What technique am I?
• Answer: Agile Conflict Resolution
• Question: I’m a strategy for minimizing risk and uncertainty by delivering small, incremental changes. What strategy am I?
• Answer: Agile Risk Reduction
• Question: I’m a practice that involves breaking down work items into smaller, more manageable tasks. What practice am I?
• Answer: Agile Task Decomposition