Agile methodology overview in Software Engineering - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

Core Values of Agile

Which of the following is NOT one of the four core values stated in the Agile Manifesto?

A Comprehensive documentation over working software

B Individuals and interactions over processes and tools

C Customer collaboration over contract negotiation

D Responding to change over following a plan

💡 Hint

Think about what Agile prioritizes more: documentation or working software?

The Agile Manifesto values working software over comprehensive documentation. So option A is the one that is NOT a core value.

📋 Factual

intermediate

Agile Iteration Length

What is the typical length of an iteration (also called a sprint) in Agile methodology?

A 1 to 4 weeks

B 3 to 6 months

C 1 to 2 days

D 6 to 8 weeks

💡 Hint

Agile focuses on quick, frequent delivery cycles.

Agile iterations or sprints usually last between 1 and 4 weeks to allow teams to deliver small, workable pieces of software frequently.

🚀 Application

advanced

Applying Agile Principles

A team following Agile notices that customer requirements change frequently during development. What is the best Agile approach to handle this situation?

A Ignore changes until the project is complete to avoid delays

B Incorporate changes in the next iteration and continuously adapt the plan

C Freeze requirements at the start and avoid changes during the project

D Extend the project timeline to accommodate all changes at once

💡 Hint

Agile values responding to change over following a fixed plan.

Agile encourages adapting to changing requirements by incorporating them in upcoming iterations, allowing flexibility and continuous improvement.

🔍 Analysis

advanced

Comparing Agile and Waterfall

Which statement best describes a key difference between Agile and Waterfall methodologies?

A Waterfall delivers software in small increments; Agile delivers all at once at the end

B Agile requires detailed documentation before coding; Waterfall does not

C Waterfall follows a linear, sequential process; Agile is iterative and incremental

D Agile discourages customer involvement; Waterfall encourages it throughout

💡 Hint

Think about how each methodology structures the development process.

Waterfall is a linear, step-by-step approach, while Agile uses iterative cycles to build software incrementally.

❓ Reasoning

expert

Agile Team Roles and Responsibilities

In an Agile Scrum team, which role is primarily responsible for maximizing the value of the product and managing the product backlog?

A Development Team Member

B Scrum Master

C Project Manager

D Product Owner

💡 Hint

This role acts as the voice of the customer and prioritizes work.

The Product Owner manages the product backlog and ensures the team delivers value aligned with customer needs.

Practice

1. What is the main focus of Agile methodology in software development?

easy

A. Detailed upfront planning

B. Strict hierarchy and roles

C. Quick delivery and teamwork

D. Long development cycles without feedback

Solution

1. Step 1: Understand Agile's core principles

   Agile emphasizes flexibility, collaboration, and fast delivery rather than rigid plans.

2. Step 2: Compare options with Agile focus

   Only quick delivery and teamwork match Agile's approach; others describe traditional methods.

3. Final Answer:

   Quick delivery and teamwork -> Option C

4. Quick Check:

   Agile = Quick delivery and teamwork [OK]

Hint: Agile means fast work and team effort [OK]

Common Mistakes:

• Thinking Agile requires detailed upfront planning
• Confusing Agile with waterfall method
• Assuming Agile avoids teamwork

2. Which of the following is a key element of Agile methodology?

easy

A. Avoiding customer feedback until the end

B. Using sprints to organize work

C. Writing all code before testing

D. Planning the entire project in detail upfront

Solution

1. Step 1: Identify Agile work structure

   Agile uses short cycles called sprints to deliver work incrementally.

2. Step 2: Eliminate incorrect options

   Writing all code before testing, avoiding feedback, and detailed upfront planning contradict Agile principles.

3. Final Answer:

   Using sprints to organize work -> Option B

4. Quick Check:

   Sprints = Agile work cycles [OK]

Hint: Sprints are short work cycles in Agile [OK]

Common Mistakes:

• Believing testing happens only after coding
• Ignoring customer feedback during development
• Thinking Agile requires full upfront planning

3. Consider this Agile sprint cycle: A team plans a 2-week sprint, delivers a feature, then gathers user feedback. What is the main benefit of this approach?

medium

A. It allows quick adjustments based on user input

B. It delays feedback until the project ends

C. It avoids changes to the original plan

D. It focuses only on documentation

Solution

1. Step 1: Analyze sprint and feedback process

   The team delivers quickly and collects feedback after each sprint.

2. Step 2: Understand Agile benefit

   This process allows adapting the product based on real user needs fast.

3. Final Answer:

   It allows quick adjustments based on user input -> Option A

4. Quick Check:

   Sprint + feedback = quick adjustments [OK]

Hint: Agile uses feedback to improve fast [OK]

Common Mistakes:

• Thinking feedback is delayed until project end
• Assuming no changes happen during sprints
• Believing documentation is the main focus

4. A team following Agile forgot to hold daily stand-up meetings during a sprint. What problem might this cause?

medium

A. Complete elimination of user feedback

B. Faster delivery of features

C. More detailed upfront planning

D. Lack of team communication and delayed issue detection

Solution

1. Step 1: Understand purpose of daily stand-ups

   These meetings help team members share progress and spot problems early.

2. Step 2: Identify consequence of missing stand-ups

   Without them, communication suffers and issues may go unnoticed, causing delays.

3. Final Answer:

   Lack of team communication and delayed issue detection -> Option D

4. Quick Check:

   Missing stand-ups = poor communication [OK]

Hint: Daily stand-ups keep team aligned [OK]

Common Mistakes:

• Assuming missing stand-ups speeds delivery
• Confusing stand-ups with planning meetings
• Thinking user feedback is stopped by missing stand-ups

5. A product owner wants to improve the Agile process by combining user feedback with sprint planning. Which approach best applies Agile principles?

hard

A. Review user feedback at the end of each sprint and adjust the next sprint's goals

B. Ignore user feedback until the entire project is complete

C. Plan all sprints in detail before starting any work

D. Avoid changing sprint goals once set, regardless of feedback

Solution

1. Step 1: Understand Agile's iterative feedback loop

   Agile encourages using feedback regularly to improve future work cycles.

2. Step 2: Match options to Agile principles

   Only reviewing feedback after each sprint and adjusting plans fits Agile's flexible approach.

3. Final Answer:

   Review user feedback at the end of each sprint and adjust the next sprint's goals -> Option A

4. Quick Check:

   Feedback + sprint planning = Agile improvement [OK]

Hint: Use feedback to plan next sprint [OK]

Common Mistakes:

• Waiting until project end for feedback
• Planning all sprints upfront without changes
• Ignoring feedback when sprint goals are set