- What does “lead time” measure in Kanban?
- The time to complete a single task
- The time from when a request is made until it’s delivered
- The time spent in meetings
- The time spent on testing
- What does “cycle time” measure in Kanban?
- The time to complete a single task
- The time from when a request is made until it’s delivered
- The time spent in meetings
- The time spent on testing
- What is “throughput” in Kanban?
- The number of tasks completed per unit of time
- The time spent on a single task
- The project budget
- The team’s communication frequency
- What is “velocity” in Scrum?
- The speed of the project manager
- The amount of work a team can complete in a Sprint
- The speed of the server
- The network speed
- What is the purpose of measuring “customer satisfaction” in Agile?
- To track team performance
- To ensure the delivered product meets customer needs
- To manage project risks
- To track project costs
- How is Agile used in software development?
- To create detailed upfront plans
- To deliver incremental software releases
- To minimize customer involvement
- To follow a strict project plan
- How is Agile used in marketing?
- To create long-term marketing plans
- To run short, iterative marketing campaigns
- To minimize customer feedback
- To follow a rigid marketing strategy
- How is Agile used in hardware development?
- To create detailed hardware specifications upfront
- To build and test hardware prototypes iteratively
- To minimize customer involvement
- To follow a rigid hardware development process
- How is Agile used in education?
- To follow a rigid curriculum
- To adapt teaching methods based on student feedback
- To minimize student involvement
- To create long-term lesson plans
- How is Agile used in construction?
- To follow a rigid construction plan
- To build and adapt construction plans based on site conditions
- To minimize stakeholder involvement
- To create long-term construction schedules
- What is servant leadership in Agile?
- Leading by giving orders
- Leading by supporting and empowering the team
- Leading by minimizing team involvement
- Leading by focusing on personal achievements
- What is a growth mindset in Agile?
- Believing abilities are fixed
- Believing abilities can be developed through dedication and hard work
- Minimizing learning opportunities
- Avoiding challenges
- What is the role of an Agile leader?
- To control the team
- To enable the team to self-organize
- To minimize team communication
- To focus on individual achievements
- What is the importance of transparency in Agile?
- To hide project issues
- To build trust and enable collaboration
- To minimize team communication
- To control team information
- What is the importance of continuous improvement in Agile?
- To maintain the status quo
- To adapt and improve processes over time
- To minimize changes
- To focus on individual achievements
- What is a common challenge when transitioning to Agile?
- Lack of team communication
- Resistance to change
- Over-documentation
- Rigid project plans
- What is a common challenge in scaling Agile?
- Lack of team collaboration
- Coordinating multiple teams
- Over-planning
- Minimizing customer feedback
- What is a common challenge in distributed Agile teams?
- Lack of face-to-face communication
- Over-communication
- Rigid project plans
- Minimizing team involvement
- What is a common challenge in Agile adoption?
- Lack of management support
- Over-planning
- Rigid project plans
- Minimizing customer feedback
- What is a common challenge with estimating in Agile?
- Over-estimating.
- Under-estimating.
- Inconsistent estimates.
- all of the above
- What is Jira used for in Agile?
- Project budgeting
- Issue and project tracking
- Risk management
- Team communication
- What is Confluence used for in Agile
- Project budgeting
- Knowledge sharing and collaboration
- Risk management
- Team communication
- What is Miro used for in Agile?
- Project budgeting
- Visual collaboration and brainstorming
- Risk management
- Team communication
- What is a retrospective technique?
- A method for planning sprints
- A method for reflecting on past sprints and identifying improvements
- A method for tracking project costs
- A method for communicating with customers
- What is a daily stand-up technique?
- A method for planning sprints
- A method for daily team coordination
- A method for tracking project costs
- A method for communicating with customers
- What is “systems thinking” in Agile?
- Focusing on individual tasks
- Understanding how different parts of a system interact
- Ignoring external factors
- Rigidly following a set process
- What is “emergent design” in Agile?
- Designing the entire system upfront
- Designing the system as it evolves
- Avoiding design altogether
- Following a pre-set design template
- What is “collective ownership” in Agile?
- Individual responsibility for all tasks
- Shared responsibility for all code and deliverables
- No responsibility for any tasks
- Responsibility only for assigned tasks
- What is “sustainable pace” in Agile?
- Working at a frantic pace continuously
- Working at a consistent and manageable pace
- Minimizing work effort
- Working only when deadlines are near
- What is “value stream mapping” used for in Agile?
- Tracking project budget
- Visualizing and optimizing the flow of value
- Documenting project risks
- Managing team communication
- What is Azure DevOps used for in Agile?
- Budget management
- Planning, development, and testing
- Risk assessment
- Customer communication
- What is Trello used for in Agile?
- Budget tracking
- Visual task management and collaboration
- Risk documentation
- Customer feedback collection
- What is Slack used for in Agile?
- Budget analysis
- Team communication and collaboration
- Risk mitigation
- Customer surveys
- What is GitLab used for in Agile?
- Budget forecasting
- Code repository management and CI/CD
- Risk monitoring
- Customer training
- What is a “definition of ready” in Agile?
- Criteria for when a task is finished
- Criteria for when a task is ready to be started
- Criteria for project closure
- Criteria for customer acceptance
- What is “Agile Release Train (ART)” in SAFe?
- A single Scrum team
- A long-lived team of Agile teams
- A project closure team
- A customer feedback team
- What is “Solution Train” in SAFe?
- A team that manages individual features
- A team that builds large and complex solutions
- A team that handles daily stand-ups
- A team that writes user stories
- What is “Portfolio Kanban” in SAFe?
- A Kanban board for individual tasks
- A Kanban system for managing portfolio initiatives
- A Kanban system for sprint planning
- A Kanban system for risk management
- What is “Lean UX” in Agile?
- A method for detailed UX design upfront
- A method for iterative UX design based on user feedback
- A method for avoiding UX design
- A method for rigid UX design
- What is “Business Agility”?
- Agile only for software development
- Applying Agile principles across the entire organization
- Avoiding any business planning
- Rigid business hierarchy
- How is AI impacting Agile practices?
- Reducing the need for iterative development
- Automating testing and data analysis
- Eliminating the need for team communication
- Removing customer feedback loops
- What is “Agile at scale” focusing on in modern practice?
- Keeping teams small and isolated
- Enabling large organizations to adapt quickly
- Maintaining rigid hierarchies
- Avoiding process change
- What is the role of “product discovery” in modern agile?
- Planning all features upfront
- Iteratively exploring and validating product ideas
- Avoiding user feedback
- Following a rigid roadmap
- What is “value stream management” focusing on in modern agile?
- Focusing on individual tasks
- Optimizing the entire flow of value to the customer
- Ignoring customer feedback
- Rigid project planning
- How is “distributed agile” changing team dynamics?
- Reducing the need for communication
- Increasing the need for asynchronous collaboration
- Eliminating team meeting
- Reducing the importance of trust
- What is “agile coaching” focusing on in modern practice?
- Controlling team decisions
- Enabling teams to self-organize and improve
- Minimizing team autonomy
- Enforcing rigid processes
- What is “agile governance” focusing on in modern practice?
- Rigid hierarchical control
- Enabling decentralized decision-making with clear guidelines
- Avoiding any form of oversight
- Centralizing all decision-making
- What is “agile finance” focusing on in modern practice?
- Rigid annual budgets
- Adaptive funding based on value delivery
- Ignoring project costs
- Minimizing financial transparency
- What is “agile HR” focusing on in modern practice?
- Rigid job descriptions
- Enabling cross-functional teams and continuous learning
- Minimizing employee feedback
- Enforcing strict career paths
- What is a key focus of the future of Agile?
- Returning to rigid waterfall practices
- Embracing adaptability and continuous evolution
- Minimizing collaboration
- Avoiding technological advancements
Answers
- The time from when a request is made until it’s delivered
- The time to complete a single task
- The number of tasks completed per unit of time
- The amount of work a team can complete in a Sprint
- To ensure the delivered product meets customer needs
- To deliver incremental software releases
- To run short, iterative marketing campaigns
- To build and test hardware prototypes iteratively
- To adapt teaching methods based on student feedback
- To build and adapt construction plans based on site conditions
- Leading by supporting and empowering the team
- Believing abilities can be developed through dedication and hard work
- To enable the team to self-organize
- To build trust and enable collaboration
- To adapt and improve processes over time
- Resistance to change
- Coordinating multiple teams
- Lack of face-to-face communication
- Lack of management support
- all of the above
- Issue and project tracking
- Knowledge sharing and collaboration
- Visual collaboration and brainstorming
- A method for reflecting on past sprints and identifying improvements
- A method for daily team coordination
- Understanding how different parts of a system interact
- Designing the system as it evolves
- Shared responsibility for all code and deliverables
- Working at a consistent and manageable pace
- Visualizing and optimizing the flow of value
- Planning, development, and testing
- Visual task management and collaboration
- Team communication and collaboration
- Code repository management and CI/CD
- Criteria for when a task is ready to be started
- A long-lived team of Agile teams
- A team that builds large and complex solutions
- A Kanban system for managing portfolio initiatives
- A method for iterative UX design based on user feedback
- Applying Agile principles across the entire organization
- Automating testing and data analysis
- Enabling large organizations to adapt quickly
- Iteratively exploring and validating product ideas
- Optimizing the entire flow of value to the customer
- Increasing the need for asynchronous collaboration
- Enabling teams to self-organize and improve
- Enabling decentralized decision-making with clear guidelines
- Adaptive funding based on value delivery
- Enabling cross-functional teams and continuous learning
- Embracing adaptability and continuous evolution