Agile Frameworks and Methodologies Flashcards

What is the primary focus of the Agile Framework?

Answer: Customer collaboration over contract negotiation

The Agile Framework, as outlined in the Agile Manifesto, primarily focuses on valuing "Customer collaboration over contract negotiation." This principle emphasizes continuous engagement with the customer throughout the development process to ensure the product truly meets their evolving needs. Prioritizing collaboration leads to more relevant and valuable outcomes than rigid adherence to initial contractual terms.

Which of the following is a key benefit of the Scrum methodology?

Answer: Frequent, small deliverables

A key benefit of the Scrum methodology is its emphasis on frequent, small deliverables, typically at the end of each Sprint. This approach allows for continuous feedback from stakeholders and users, enabling the team to adapt and refine the product iteratively. Delivering working software regularly provides early value and reduces the risk of large-scale failures.

What does the term 'Kanban' refer to in Agile methodologies?

Answer: A board for visualizing work tasks

In Agile methodologies, 'Kanban' refers to a visual system, often a board, used to manage and visualize work as it flows through a process. It helps teams see the status of tasks, identify bottlenecks, and limit work in progress. This visual management system promotes efficiency and continuous improvement by making the workflow transparent.

Which Agile methodology focuses on continuous delivery and testing?

Answer: Extreme Programming (XP)

Extreme Programming (XP) is an Agile methodology specifically known for its focus on continuous delivery and testing. XP practices like test-driven development (TDD), continuous integration, and frequent releases ensure that software is constantly tested and delivered in small, functional increments. This emphasis on quality and rapid feedback loops makes it highly effective for complex projects.

What is a Sprint Review in the Scrum process?

Answer: A review meeting with stakeholders to demonstrate completed work

A Sprint Review in the Scrum process is a formal meeting where the Development Team demonstrates the work completed during the Sprint to stakeholders. Its purpose is to gather feedback on the increment and collaboratively decide on future adjustments to the Product Backlog. This transparency and feedback loop ensure the product remains aligned with customer needs.

What is the purpose of a Product Backlog in Scrum?

Answer: A prioritized list of features or tasks

The Product Backlog in Scrum is a dynamic, prioritized list of all the features, functions, requirements, enhancements, and fixes that constitute the work to be done on the product. It is maintained by the Product Owner and serves as the single source of truth for all work. This backlog guides the Development Team on what to build next, ensuring alignment with product vision.

How does the Agile Manifesto prioritize customer collaboration?

Answer: Customer collaboration over contract negotiation

The Agile Manifesto explicitly states "Customer collaboration over contract negotiation" as one of its four core values. This principle highlights the importance of continuous, direct engagement with customers to understand their evolving needs and incorporate their feedback throughout the project lifecycle. It prioritizes building strong relationships and delivering value over strict adherence to initial, potentially outdated, contractual terms.

What is a key principle of the Lean methodology in Agile?

Answer: Eliminating waste and improving flow

A key principle of the Lean methodology in Agile is the relentless pursuit of eliminating waste and improving the flow of value to the customer. Lean focuses on identifying and removing any activity that does not add value, such as unnecessary features, waiting times, or defects. By optimizing the workflow, Lean aims to deliver higher quality products more efficiently.

Which of the following is NOT a role in Scrum?

Answer: Project Manager

In Scrum, the core roles are the Product Owner, Scrum Master, and Development Team. The traditional role of a "Project Manager" does not exist in Scrum, as many of those responsibilities are distributed among the Scrum Master (facilitating the process), Product Owner (managing the product backlog), and the self-organizing Development Team. This structure promotes collaboration and self-management within the team.