- Which of the following is a core principle of the Agile Manifesto?
- Comprehensive documentation over working software
- Following a plan over responding to change
- Customer collaboration over contract negotiation
- Process and tools over individuals and interactions
- What is the primary goal of Agile methodologies?
- To minimize project costs
- To maximize predictability
- To deliver value to customers quickly and iteratively
- To follow a strict project plan
- Which of these is a key value in the Agile Manifesto?
- Rigorous planning
- Contract negotiation
- Responding to change
- Process adherence
- In Scrum, who is responsible for maximizing the value of the product?
- Development Team
- Scrum Master
- Product Owner
- Project Manager
- What is the purpose of the Daily Scrum?
- To provide status updates to the Product Owner
- To plan the next Sprint
- To inspect progress towards the Sprint Goal and adapt the Sprint Backlog
- To resolve all project issues
- What is the time-boxed period during which a Scrum Team works to complete a set amount of work?
- Iteration
- Sprint
- Release
- Phase
- Which Scrum artifact represents the work remaining to be done in a Sprint?
- Product Backlog
- Sprint Backlog
- Increment
- Burndown Chart
- Who facilitates the Scrum events and ensures the Scrum Team adheres to Scrum rules?
- Product Owner
- Development Team
- Scrum Master
- Project Manager
- What is the purpose of the Sprint Review?
- To plan the next Sprint
- To inspect the Increment and adapt the Product Backlog
- To resolve project issues
- To conduct a team retrospective
- What is a product backlog?
- A list of tasks for the current sprint
- A prioritized list of features and requirements
- A document for the project closure
- A list of risks
- What is the definition of done?
- When the product owner accepts the work
- When the developer says it is done
- A shared understanding of when work is complete
- When the qa team finishes their work
- What scrum ceremony focuses on improvement?
- Daily scrum
- Sprint review
- Sprint retrospective
- Sprint planning
- What is the primary focus of Kanban?
- Time-boxed iterations
- Continuous flow of work
- Sprint planning
- Detailed documentation
- What does the “WIP” limit in Kanban represent?
- The maximum number of tasks in the Product Backlog
- The maximum number of tasks a team can work on simultaneously
- The total time allowed for a Sprint
- The project’s overall budget
- What is a Kanban board used for?
- To plan Sprints
- To visualize the flow of work
- To track project costs
- To create detailed documentation
- In Kanban, what is the goal of managing flow?
- To increase the number of features delivered
- To reduce cycle time and improve predictability
- To enforce strict deadlines
- To minimize team communication
- What is a cumulative flow diagram?
- A diagram showing team velocity
- A diagram showing the flow of work over time
- A diagram showing the project budget
- A diagram showing the team structure
- What is a user story?
- A detailed technical specification
- A short description of a feature from the user’s perspective
- A project plan
- A risk assessment
- What format is commonly used for user stories?
- As a [role], I want [goal], so that [benefit]
- Detailed technical requirements
- Project budget and timeline
- Risk register
- What is “story points” used for??
- To measure the time it takes to complete a task
- To estimate the relative size and complexity of a user story
- To track project costs
- To document project risks
- What is planning poker?
- A risk management technique
- A method for estimating user stories
- A communication tool
- A project closing activity
- What is a spike?
- A very large user story
- A time-boxed research activity
- A sprint that is longer than normal
- A project risk
- What is continuous integration (CI)?
- Integrating project teams
- Continuously merging code changes into a central repository
- Continuous project planning
- Continuous customer feedback
- What is test-driven development (TDD)?
- Testing after development is complete
- Writing tests before writing code
- Testing by the customer
- Automated testing only
- What is refactoring?
- Rewriting code to improve its design without changing its functionality
- Adding new features to the software
- Fixing bugs
- Documenting the code
- What is pair programming?
- Two teams working on the same project
- Two developers working together on the same code
- Two project managers working together
- Two customers providing feedback
- What is a burn-down chart?
- A chart showing the project budget
- A chart showing the remaining work in a Sprint
- A chart showing the team’s velocity
- A chart showing project risks
- What is a velocity in agile?
- The speed of the project manager
- The amount of work the team completes per sprint
- The speed of the server
- The speed of the network
- What is the role of the Agile Coach?
- To manage the project budget
- To facilitate team meetings
- To guide the team in adopting Agile practices
- To write code
- What is a self-organizing team?
- A team that requires minimal management oversight
- A team that works independently of the Product Owner
- A team that only plans at the beginning of the project
- A team that does not communicate with each other
- What is the role of the dev team?
- To manage the budget
- To create the product
- To manage the product backlog
- To facilitate the meetings
- What is SAFe?
- A small agile framework
- A Scaled Agile Framework
- A simple agile tool
- A set of agile metrics
- What is LeSS?
- Large-Scale Scrum
- Little-Scale scrum
- Lean system scrum
- Linear system scrum
- What is a Program Increment (PI) in SAFe?
- A single sprint
- A timebox during which an Agile Release Train (ART) delivers incremental value
- A daily meeting
- A project closure phase
- What is the purpose of the Release Train Engineer (RTE) in SAFe?
- To write code
- To manage the project budget
- To facilitate the ART events and processes
- To manage the product backlog
- What is the purpose of the Inspect & Adapt event in SAFe?
- To plan the next PI
- To review the current PI and identify improvement opportunities
- To conduct daily stand-ups
- To manage risks
- What is DevOps?
- A project management methodology
- A set of practices that automate the processes between software development and IT teams
- A risk management technique
- A communication tool
- What is continuous delivery (CD)?
- Continuous project planning
- Continuously releasing software to production
- Continuous customer feedback
- Continuous team meetings
- What is a minimum viable product (MVP)?
- A fully featured product
- A product with just enough features to satisfy early customers
- A project budget
- A detailed project plan
- What is technical debt?
- Project budget overruns
- The implied cost of rework caused by choosing an easy solution now instead of a better approach
- Project delays
- Communication issues
- What is the purpose of a sprint goal?
- To track project costs
- To provide focus and direction for the Sprint
- To document project risks
- To plan the next Sprint
- What is a burn-up chart?
- A chart showing the remaining work in a Sprint
- A chart showing the total completed work over time
- A chart showing the project budget
- A chart showing project risks
- What is a value stream?
- A stream of project tasks
- The sequence of activities that an organization undertakes to deliver a value to a customer
- A project budget
- A communication plan
- What is a lean startup?
- A large corporate project
- A methodology for developing businesses and products that aims to shorten product development cycles
- A project closure process
- A risk management technique
- What is emergent architecture?
- A pre-defined architectural plan
- An architecture that evolves over time based on feedback and learning
- A project budget
- A communication plan
- What is a product vision?
- A detailed project plan
- A long-term goal for the product
- A sprint backlog
- A risk register
- What is a release planning event?
- A daily meeting
- A meeting to plan the next release
- A sprint retrospective
- A risk assessment
- What is a system demo?
- A demo of the project budget
- A demo of the integrated work from all teams in an ART
- A risk assessment meeting
- A sprint retrospective
- What is a Communities of Practice (CoP)?
- A project team
- Groups of people who share a concern or a passion for something they do and learn how to do it better as they interact regularly
- A risk management team
- A communication team
- What is a value stream mapping?
- Mapping the project budget
- Visualizing the flow of value through a process
- Mapping project risks
- Mapping team communication
Answers
- Customer collaboration over contract negotiation
- To deliver value to customers quickly and iteratively
- Responding to change
- Product Owner
- To inspect progress towards the Sprint Goal and adapt the Sprint Backlog
- Sprint
- Sprint Backlog
- Scrum Master
- To inspect the Increment and adapt the Product Backlog
- A prioritized list of features and requirements
- A shared understanding of when work is complete
- Sprint retrospective
- Continuous flow of work
- The maximum number of tasks a team can work on simultaneously
- To visualize the flow of work
- To reduce cycle time and improve predictability
- A diagram showing the flow of work over time
- A short description of a feature from the user’s perspective
- As a [role], I want [goal], so that [benefit]
- To estimate the relative size and complexity of a user story
- A method for estimating user stories
- A time-boxed research activity
- Continuously merging code changes into a central repository
- Writing tests before writing code
- Rewriting code to improve its design without changing its functionality
- Two developers working together on the same code
- A chart showing the remaining work in a Sprint
- The amount of work the team completes per sprint
- To guide the team in adopting Agile practices
- A team that requires minimal management oversight
- To create the product
- A Scaled Agile Framework
- Large-Scale Scrum
- A timebox during which an Agile Release Train (ART) delivers incremental value
- To facilitate the ART events and processes
- To review the current PI and identify improvement opportunities
- A set of practices that automate the processes between software development and IT teams
- Continuously releasing software to production
- A product with just enough features to satisfy early customers
- The implied cost of rework caused by choosing an easy solution now instead of a better approach
- To provide focus and direction for the Sprint
- A chart showing the total completed work over time
- The sequence of activities that an organization undertakes to deliver a value to a customer
- A methodology for developing businesses and products that aims to shorten product development cycles
- An architecture that evolves over time based on feedback and learning
- A long-term goal for the product
- A meeting to plan the next release
- A demo of the integrated work from all teams in an ART
- Groups of people who share a concern or a passion for something they do and learn how to do it better as they interact regularly
- Visualizing the flow of value through a process