Agile methodology basics in Intro to Computing - Practice Problems & Coding Challenges

Challenge - 5 Problems

🧠 Conceptual

intermediate

What is the primary goal of Agile methodology?

Choose the best description of the main goal Agile aims to achieve in software development.

A Deliver working software quickly and adapt to change frequently.

B Complete all project documentation before starting coding.

C Follow a strict plan without changes until the project ends.

D Assign tasks only to senior developers to ensure quality.

💡 Hint

Think about flexibility and speed in delivering software.

Agile focuses on delivering working software quickly and adapting to changes rather than following a fixed plan.

❓ trace

intermediate

Trace the Agile sprint cycle steps

Put these Agile sprint cycle steps in the correct order.

A 1,3,2,4

B 1,2,3,4

C 2,1,3,4

D 1,2,4,3

💡 Hint

Think about planning first, daily updates, then review and reflection.

The correct order is Sprint Planning, Daily Stand-up, Sprint Review, and Sprint Retrospective.

❓ identification

advanced

Identify the Agile artifact used to track work progress

Which Agile artifact visually shows the progress of tasks during a sprint?

A Burndown Chart

B Product Backlog

C Sprint Goal

D Definition of Done

💡 Hint

It is a chart that shows how much work remains over time.

The Burndown Chart tracks remaining work and progress during a sprint visually.

❓ Comparison

advanced

Compare Agile and Waterfall methodologies

Which statement correctly contrasts Agile with Waterfall?

A Waterfall encourages daily team meetings; Agile avoids frequent communication.

B Agile requires full documentation upfront; Waterfall allows changes anytime.

C Waterfall delivers software in small parts; Agile delivers all at once.

D Agile is flexible and iterative; Waterfall is linear and sequential.

💡 Hint

Think about how each method handles project phases and changes.

Agile is iterative and adapts to change, while Waterfall follows a fixed, linear sequence.

🚀 Application

expert

Determine the sprint velocity from given data

A team completed 5 user stories with story points: 3, 2, 5, 8, and 2 in one sprint. What is the sprint velocity?

A 15

B 18

C 20

D 10

💡 Hint

Add all the story points completed in the sprint.

Sprint velocity is the total story points completed in a sprint: 3+2+5+8+2 = 20.

Practice

1. What is the main purpose of breaking a project into sprints in Agile methodology?

easy

A. To complete the entire project in one go without breaks

B. To make the project easier to manage and deliver in small parts

C. To avoid any communication within the team

D. To delay feedback until the project is finished

Solution

1. Step 1: Understand Agile sprint concept

   Agile divides big projects into smaller parts called sprints to manage work better.

2. Step 2: Identify the purpose of sprints

   Sprints help teams focus on small goals, making progress visible and manageable.

3. Final Answer:

   To make the project easier to manage and deliver in small parts -> Option B

4. Quick Check:

   Agile sprints = small, manageable parts [OK]

Hint: Sprints mean small parts, not one big chunk [OK]

Common Mistakes:

• Thinking sprints mean working without breaks
• Believing sprints avoid team communication
• Assuming feedback is delayed until project end

2. Which of the following is the correct sequence of phases in an Agile sprint?

easy

A. Review, Improve, Plan, Work

B. Work, Plan, Improve, Review

C. Plan, Work, Review, Improve

D. Improve, Review, Work, Plan

Solution

1. Step 1: Recall Agile sprint phases

   Agile sprints start with planning, then working, followed by review and improvement.

2. Step 2: Match the correct order

   Plan, Work, Review, Improve matches the correct sequence: Plan, Work, Review, Improve.

3. Final Answer:

   Plan, Work, Review, Improve -> Option C

4. Quick Check:

   Sprint phases = Plan -> Work -> Review -> Improve [OK]

Hint: Remember: Plan before work, then review and improve [OK]

Common Mistakes:

• Mixing up the order of phases
• Starting with work before planning
• Skipping the review phase

3. Consider this Agile team scenario: The team completes a sprint and holds a retrospective meeting. What is the main outcome of this retrospective?

medium

A. To identify what went well and what can be improved

B. To assign blame for missed tasks

C. To finalize the entire project without changes

D. To stop all communication until the next sprint

Solution

1. Step 1: Understand the purpose of sprint retrospective

   The sprint retrospective is a meeting to discuss successes and areas for improvement.

2. Step 2: Identify the correct outcome

   The team focuses on learning and improving, not blaming or stopping communication.

3. Final Answer:

   To identify what went well and what can be improved -> Option A

4. Quick Check:

   Sprint retrospective = learn and improve [OK]

Hint: Retrospective means learn, not blame or stop [OK]

Common Mistakes:

• Thinking retrospective is for blaming team members
• Assuming project is finalized at retrospective
• Believing communication stops after retrospective

4. A team following Agile forgot to hold daily stand-up meetings. What problem is most likely to occur?

medium

A. Lack of daily communication causing delays and misunderstandings

B. The project will automatically finish early

C. The team will have too many meetings

D. The sprint planning phase will be skipped

Solution

1. Step 1: Understand the role of daily stand-ups

   Daily stand-ups keep the team aligned and help spot problems early.

2. Step 2: Identify the impact of missing stand-ups

   Without daily communication, delays and misunderstandings are likely.

3. Final Answer:

   Lack of daily communication causing delays and misunderstandings -> Option A

4. Quick Check:

   Missing stand-ups = poor communication [OK]

Hint: Daily stand-ups prevent delays and confusion [OK]

Common Mistakes:

• Thinking missing stand-ups speeds up project
• Believing more meetings happen without stand-ups
• Assuming sprint planning is skipped

5. A product owner wants to improve team flexibility by adjusting sprint length based on project needs. Which Agile principle supports this approach?

hard

A. Fixing sprint length regardless of project changes

B. Completing all work before any review

C. Avoiding customer feedback during sprints

D. Responding to change over following a fixed plan

Solution

1. Step 1: Recall Agile values about change

   Agile values responding to change more than strictly following plans.

2. Step 2: Match the principle to sprint length adjustment

   Adjusting sprint length to fit needs shows flexibility and embracing change.

3. Final Answer:

   Responding to change over following a fixed plan -> Option D

4. Quick Check:

   Agile principle = embrace change [OK]

Hint: Agile means adapt plans, not stick rigidly [OK]

Common Mistakes:

• Thinking Agile avoids changes
• Believing reviews happen only after all work
• Assuming sprint length is always fixed