Agile methodology basics in Intro to Computing - Interactive Code Practice

Practice - 5 Tasks

1fill in blank

easy

Complete the code to name the Agile framework that uses sprints.

Intro to Computing

The Agile framework that uses time-boxed iterations called [1] is Scrum.

Drag options to blanks, or click blank then click option'

Aphases

Bcycles

Csprints

Dsteps

Attempts:

3 left

💡 Hint

Common Mistakes

Confusing sprints with phases or cycles which are longer or less specific.

Using generic terms like steps instead of the specific Agile term.

In Agile, Scrum uses short time-boxed iterations called sprints to deliver work incrementally.

2fill in blank

medium

Complete the sentence to describe Agile's approach to changes.

Intro to Computing

Agile welcomes [1] even late in development to improve the product.

Drag options to blanks, or click blank then click option'

Adelays

Bcosts

Cproblems

Dchanges

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing negative terms like delays or problems instead of positive adaptation.

Confusing costs with changes.

Agile values responding to changes over following a fixed plan, even late in development.

3fill in blank

hard

Fix the error in the Agile principle about team communication.

Intro to Computing

The most efficient and effective method of conveying information to and within a development team is [1] communication.

Drag options to blanks, or click blank then click option'

Awritten

Bface-to-face

Cemail

Ddocumented

Attempts:

3 left

💡 Hint

Common Mistakes

Choosing written or documented communication which can be slower.

Selecting email which is less immediate than face-to-face.

Agile emphasizes face-to-face communication as the best way to share information quickly and clearly.

4fill in blank

hard

Fill both blanks to complete the Agile values statement.

Intro to Computing

Individuals and interactions over [1], and working software over [2].

Drag options to blanks, or click blank then click option'

Aprocesses and tools

Bcomprehensive documentation

Ccontract negotiation

Dfollowing a plan

Attempts:

3 left

💡 Hint

Common Mistakes

Mixing up the pairs or choosing contract negotiation instead of documentation.

Confusing following a plan with processes and tools.

Agile values individuals and interactions more than processes and tools, and working software more than comprehensive documentation.

5fill in blank

hard

Fill all three blanks to complete the Agile Scrum roles.

Intro to Computing

The three main Scrum roles are [1], [2], and [3].

Drag options to blanks, or click blank then click option'

AProduct Owner

BScrum Master

CDevelopment Team

DProject Manager

Attempts:

3 left

💡 Hint

Common Mistakes

Including Project Manager as a Scrum role.

Confusing Scrum Master with Development Team.

The three main Scrum roles are Product Owner, Scrum Master, and Development Team. Project Manager is not a Scrum role.

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