1. Individuals and interactions over processes and tools: Agile prioritizes the importance of people and their interactions over rigid processes and tools. It emphasizes collaboration, communication, and teamwork among team members.

2. Working software over comprehensive documentation: Agile emphasizes the importance of delivering working software as the primary measure of progress. While documentation is important, Agile values tangible results and prioritizes delivering value to customers through functioning software.

3. Customer collaboration over contract negotiation: Agile promotes active involvement and collaboration with customers throughout the development process. It emphasizes understanding and responding to customer needs and feedback, rather than relying solely on fixed contracts or requirements documents.

4. Responding to change over following a plan: Agile recognizes the dynamic nature of software development and the need to adapt to changing requirements and priorities. It encourages flexibility, continuous improvement, and responsiveness to change to deliver the best possible outcome.

he Agile Manifesto consists of twelve principles that provide guidance on how to apply the four core values of the Agile Manifesto into practice. Here are the twelve principles:

1. Customer satisfaction through early and continuous software delivery: Agile prioritizes delivering valuable software to customers early and frequently, ensuring that their needs are met and their feedback is incorporated throughout the development process.

2. Welcome changing requirements, even late in development: Agile recognizes that requirements can evolve and change over time. Embracing change allows teams to adapt quickly to customer feedback and market demands, leading to better outcomes.

3. Deliver working software frequently, with a preference for shorter timescales: Agile encourages delivering functional increments of software frequently, typically in iterations or sprints, to provide value to customers more rapidly and to gather feedback early.

4. Close, daily cooperation between business people and developers: Agile emphasizes the importance of collaboration between stakeholders and development teams to ensure that the delivered software meets business objectives and customer needs.

5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done: Agile promotes empowering and trusting individuals within self-organizing teams. Motivated team members are more likely to produce high-quality work and achieve project success.

6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation: Agile values direct communication and encourages colocation or virtual face-to-face interaction to enhance collaboration, reduce misunderstandings, and foster shared understanding among team members.

7. Working software is the primary measure of progress: Agile emphasizes delivering tangible results—working software—as a measure of project progress, rather than focusing solely on documentation or intermediate deliverables.

8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely: Agile advocates for maintaining a sustainable pace of work to prevent burnout and ensure long-term productivity and effectiveness.

9. Continuous attention to technical excellence and good design enhances agility: Agile emphasizes the importance of technical excellence and sound design principles to maintain flexibility, adaptability, and responsiveness to change over the long term.

10. Simplicity—the art of maximizing the amount of work not done—is essential: Agile encourages teams to focus on delivering the most valuable features and eliminating unnecessary complexity. Simplifying processes and solutions leads to greater efficiency and effectiveness.

11. The best architectures, requirements, and designs emerge from self-organizing teams: Agile trusts that self-organizing teams, with the right skills and autonomy, are best positioned to make informed decisions and produce high-quality outcomes.

12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly: Agile promotes continuous improvement through reflection and adaptation. Regular retrospectives allow teams to identify areas for improvement and make necessary adjustments to enhance their effectiveness and efficiency.

These principles serve as a guide for Agile teams to effectively deliver value to customers, embrace change, collaborate closely, empower individuals, and continuously improve their processes and outcomes.

1. The Agile Manifesto was created in which year?

a) 1995
b) 2001
c) 2010
d) 2015

✅ Answer: b
📌 Explanation: The Agile Manifesto was created in 2001 by 17 software development experts in Snowbird, Utah.

2. How many core values are outlined in the Agile Manifesto?

a) 3
b) 4
c) 5
d) 6

✅ Answer: b
📌 Explanation: The Agile Manifesto consists of four core values that prioritize people, collaboration, and adaptability.

3. Which of the following is NOT one of the four Agile values?

a) Individuals and interactions over processes and tools
b) Working software over comprehensive documentation
c) Contract negotiation over customer collaboration
d) Responding to change over following a plan

✅ Answer: c
📌 Explanation: The correct Agile value is "Customer collaboration over contract negotiation."

4. Agile Manifesto emphasizes:

a) Strict project planning
b) Delivering valuable software frequently
c) Detailed documentation before development
d) Heavy reliance on project managers

✅ Answer: b
📌 Explanation: Agile promotes frequent delivery of working software to ensure customer satisfaction.

5. Agile Manifesto values customer collaboration:

a) More than contract negotiation
b) Equally as contract negotiation
c) Less than contract negotiation
d) Not at all

✅ Answer: a
📌 Explanation: Agile prioritizes collaboration with customers to ensure software meets their needs.

6. What is the highest priority in Agile development?

a) Completing documentation
b) Following the project schedule
c) Satisfying the customer through early and continuous delivery
d) Avoiding changes in project requirements

✅ Answer: c
📌 Explanation: Agile emphasizes customer satisfaction through early and frequent delivery of valuable software.

7. According to Agile principles, how often should teams deliver working software?

a) Once at the end of the project
b) Every few years
c) Frequently, from a couple of weeks to a couple of months
d) Only after all requirements are finalized

✅ Answer: c
📌 Explanation: Agile promotes frequent releases (every few weeks or months) to gather continuous feedback.

8. What is the preferred way of communication in Agile teams?

a) Emails
b) Formal reports
c) Face-to-face conversation
d) Conference calls

✅ Answer: c
📌 Explanation: Agile prefers face-to-face communication for effective collaboration and faster decision-making.

9. Agile encourages welcoming change in requirements:

a) Only at the beginning of the project
b) Even late in development
c) Only if it doesn't impact the schedule
d) Never

✅ Answer: b
📌 Explanation: Agile embraces change, even late in development, to enhance customer value.

10. Agile teams should aim to deliver software with a preference for:

a) Complicated design
b) Working functionality
c) Extensive documentation
d) Rigid deadlines

✅ Answer: b
📌 Explanation: Agile prioritizes working software over excessive documentation or strict planning.

11. What is the recommended pace of development in Agile?

a) Slow and steady
b) As fast as possible
c) A sustainable and constant pace
d) Variable, depending on workload

✅ Answer: c
📌 Explanation: Agile promotes a sustainable pace to maintain quality and team well-being.

12. What is a key characteristic of an Agile team?

a) Large, hierarchical structure
b) Self-organizing and cross-functional
c) Rigid and controlled by management
d) Strictly follows a waterfall model

✅ Answer: b
📌 Explanation: Agile teams are self-organizing and cross-functional, making decisions collaboratively.

13. Agile encourages simplicity. What does this mean?

a) Removing all project documentation
b) Maximizing work done to meet deadlines
c) Avoiding unnecessary work and focusing on essentials
d) Ignoring planning completely

✅ Answer: c
📌 Explanation: Agile promotes simplicity by focusing on only what is necessary to deliver value.

14. Who should be responsible for technical decisions in Agile?

a) Only senior management
b) Only team leaders
c) The entire development team
d) External consultants

✅ Answer: c
📌 Explanation: Agile empowers the entire development team to make technical decisions collaboratively.

15. Agile promotes:

a) Detailed upfront planning
b) Collaboration and continuous feedback
c) Isolated work without stakeholder involvement
d) Rigid control of development phases

✅ Answer: b
📌 Explanation: Agile focuses on continuous collaboration, adaptability, and feedback.

16. How does Agile measure progress?

a) By tracking the number of meetings
b) By the percentage of documentation completed
c) By working software delivered
d) By following the original plan strictly

✅ Answer: c
📌 Explanation: Agile measures progress based on working software, not just documentation or planning.

17. What is the primary role of a customer in an Agile project?

a) To review and approve all project documentation
b) To provide continuous feedback
c) To control development schedules
d) To handle team management

✅ Answer: b
📌 Explanation: Agile involves customers in continuous feedback cycles to ensure the product meets their needs.

18. What mindset does Agile promote regarding failure?

a) Failure is unacceptable
b) Failure should be punished
c) Failure is a learning opportunity
d) Failure should be ignored

✅ Answer: c
📌 Explanation: Agile sees failures as learning opportunities to improve future iterations.

19. Agile teams should prioritize:

a) Following the plan no matter what
b) Responding to change
c) Avoiding changes in scope
d) Strictly adhering to initial requirements

✅ Answer: b
📌 Explanation: Agile teams prioritize adaptability and responsiveness to change over rigid planning.

20. The Agile Manifesto is best described as:

a) A rigid framework with fixed steps
b) A set of values and principles to guide agile teams
c) A detailed project management methodology
d) A requirement for software development

✅ Answer: b
📌 Explanation: The Agile Manifesto is a flexible guide that provides values and principles for agile development.