Agile methodology basics in Intro to Computing - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is Agile methodology?

Agile methodology is a way to manage projects by breaking work into small parts called iterations or sprints. It focuses on teamwork, flexibility, and delivering small pieces of working software often.

beginner

What is a sprint in Agile?

A sprint is a short, fixed time period (usually 1-4 weeks) during which a team works to complete a set of tasks or features. It helps teams deliver work regularly and get feedback quickly.

intermediate

Name three key values of the Agile Manifesto.

1. Individuals and interactions over processes and tools
2. Working software over comprehensive documentation
3. Customer collaboration over contract negotiation

intermediate

What is the role of a Scrum Master?

A Scrum Master helps the team follow Agile practices, removes obstacles, and facilitates meetings. They support the team to work smoothly and improve continuously.

beginner

Why is customer feedback important in Agile?

Customer feedback helps the team understand if the product meets needs and allows quick changes. It ensures the final product is useful and valuable.

What is the main goal of Agile methodology?

A Deliver working software frequently

B Create detailed documentation before coding

C Complete the entire project before showing results

D Avoid changes during the project

Agile focuses on delivering working software frequently to get feedback and improve.

How long is a typical Agile sprint?

A 6 months

B 1 year

C 1 day

D 1-4 weeks

Sprints usually last between 1 to 4 weeks to allow quick delivery and feedback.

Which role helps remove obstacles in an Agile team?

A Scrum Master

B Product Owner

C Developer

D Customer

The Scrum Master supports the team by removing obstacles and facilitating Agile practices.

Which is NOT a key value of the Agile Manifesto?

A Customer collaboration over contract negotiation

B Working software over comprehensive documentation

C Processes and tools over individuals and interactions

D Responding to change over following a plan

Agile values individuals and interactions over processes and tools, not the other way around.

Why does Agile encourage frequent customer feedback?

A To delay the project

B To ensure the product meets customer needs

C To increase documentation

D To avoid changes

Frequent feedback helps the team adjust and deliver a product that customers want.

Explain the main principles of Agile methodology and how they help teams deliver better software.

Think about how breaking work into small parts and talking often helps.

Describe the roles of Scrum Master and Product Owner in an Agile team.

One helps the team work well, the other decides what to build.

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