Agile is a (a)   approach to software delivery that builds software incrementally from the start of the project.

Agile methodologies focus on (a)   rather than predictive methodologies.

The Agile Manifesto values (a)   and interactions over processes and tools.

In Scrum, the primary unit of work is called a (a)   , which typically lasts 2 to 4 weeks.

The (a)   is responsible for managing the product backlog in Scrum.

The Kanban Method is inspired by the (a)   manufacturing system.

Agile approaches emphasize (a)   to change over following a plan.

The (a)   is a meeting held at the end of a Sprint to reflect on team performance and identify areas for improvement.

The (a)   is a prioritized list of features, requirements, and tasks that the team needs to work on in Scrum.

Agile methodologies are not suitable for projects with (a)   and stable requirements.

The (a)   is responsible for facilitating the Scrum process and helping the team remove obstacles.

The Agile Manifesto values (a)   software over comprehensive documentation.

The Agile Manifesto values (a)   software over comprehensive documentation.

In Agile, (a)   is the primary measure of progress.

The Kanban Method focuses on (a)   work in progress to improve flow.

Agile teams typically consist of (a)   to 9 members.

The (a)   is a daily meeting in Scrum where team members discuss progress and obstacles.

Agile approaches are particularly useful for projects with (a)   requirements.

The (a)   is the sum of all the Product Backlog items completed during a Sprint.

The Agile Manifesto values (a)   collaboration over contract negotiation.

The Kanban Method is considered a (a)   approach, meaning teams can start using it without major changes to their current process.

(a)   work refers to projects with clear procedures and low levels of uncertainty, often based on proven processes from past projects.

(a)   work involves projects with unclear requirements, high complexity, and frequent changes, requiring problem-solving and collaboration.

Agile approaches focus on delivering value in short cycles, adapting quickly to changes, and (a)   improvement.

The three key principles of Agile methodologies are: adaptive methodologies, focus on people, and (a)   processes.

In Scrum, a (a)   is a time-boxed period (usually 2-4 weeks) where the team works to deliver a potentially shippable product increment.

The (a)   is responsible for managing the product backlog, prioritizing work, and ensuring the team delivers value to the customer.

The (a)   Method is a lean approach to managing work, focusing on visualizing work, limiting work in progress, and improving flow.

The (a)   is a set of values and principles for software development that prioritizes individuals, collaboration, and responding to change.

Definable work has clear procedures and low risk, while (a)   work involves unclear requirements, high complexity, and frequent changes.

The (a)   meeting is a short meeting where team members discuss progress, plans, and any obstacles they are facing.

The (a)   facilitates the Scrum process, helps the team remove obstacles, and ensures the team follows Agile principles.

The main goal of (a)   and incremental approaches is to deliver small increments of work, gather feedback, and adapt quickly to changes.

Agile and Kanban are subsets of (a)   thinking, sharing principles like focusing on value, minimizing waste, and continuous improvement.

The (a)   is a meeting held at the end of a Sprint to reflect on team performance and identify areas for improvement.

Agile focuses on adaptability and responding to change, while traditional (a)   approaches aim to define all requirements upfront.

Customer (a)   ensures that the product meets customer needs and allows for continuous feedback and adaptation.

The (a)   is a prioritized list of features, requirements, and tasks that the team needs to work on to deliver the product.

The (a)   is responsible for delivering the product increment at the end of each Sprint.

The Agile Manifesto values guide teams to prioritize individuals, collaboration, working software, and (a)   to change over rigid processes and documentation.

Small increments allow teams to gather feedback quickly, adapt to changes, and reduce the risk of (a)   and wasted effort.