Agile Foundations

What is the Agile Manifesto?

• A set of values and principles for software development that prioritize individuals and interactions over processes and tools, working software over comprehensive documentation, customer collaboration over contract negotiation, and responding to change over following a plan.

• A document outlining project management methodologies

• A framework for financial planning

• A set of guidelines for hardware development

Name the four values of the Agile Manifesto.

• Individuals and interactions over processes and tools, Working software over comprehensive documentation, Customer collaboration over contract negotiation, and Responding to change over following a plan.

• Comprehensive documentation over working software

• Processes and tools over individuals and interactions

• Contract negotiation over customer collaboration

What is Sprint Planning in Agile?

• Sprint Planning is a retrospective meeting in Agile.

• Sprint Planning is a daily stand-up meeting in Agile.

• Sprint Planning is a meeting to discuss long-term project goals in Agile.

• Sprint Planning in Agile is a meeting where the team plans the work to be done in the upcoming sprint.

What are the key activities involved in Sprint Planning?

• Holding team meetings, updating project documentation, conducting user interviews

• Setting sprint goal, selecting user stories, estimating effort, breaking down user stories, creating sprint backlog

• Creating sprint plan, conducting daily stand-ups, reviewing sprint progress

• Writing code, testing software, deploying updates

What is a User Story in Agile?

• A User Story in Agile is a concise description of a software feature from an end-user perspective.

• A User Story in Agile is a project management tool

• A User Story in Agile is a type of bug report

• A User Story in Agile is a detailed technical specification

How are User Stories written?

• User Stories are written in a foreign language

• User Stories are written using only emojis

• User Stories are written in the form of a poem

• User Stories are typically written in the format: As a [role], I want [goal], so that [benefit].

What is the purpose of Retrospectives in Agile?

• The purpose of Retrospectives in Agile is to reflect on the team's performance, identify areas of improvement, and implement changes for continuous enhancement.

• Retrospectives are used to assign blame to team members

• Retrospectives are conducted to waste time without any purpose

• Retrospectives aim to showcase individual achievements rather than team performance

What are the main steps in conducting a Retrospective meeting?

• Setting the stage, gathering data, generating insights, deciding what to do, closing the retrospective

• Ignoring team feedback, not documenting action items, not following up on action items, not closing the retrospective

• Setting the stage, analyzing data, brainstorming solutions, closing the retrospective

• Planning the meeting, discussing unrelated topics, skipping the retrospective, ending abruptly

Explain the concept of 'Inspect and Adapt' in Agile.

• Inspect and Delay involves delaying any improvements until the project is completed.

• Inspect and Repeat involves repeating the same actions without analyzing the project's progress.

• Inspect and Ignore involves ignoring the current state of the project and proceeding without any changes.

• Inspect and Adapt involves inspecting the current state of the project, identifying areas for improvement, and making necessary adaptations to optimize the team's performance.

How does Agile promote customer collaboration?

• By ignoring customer feedback

• By excluding customers from the development process

• By involving customers throughout the development process, gathering feedback, and adjusting the product accordingly.

• By only involving customers at the beginning of the project