🎯 Objective:
To illustrate the importance of continuous user feedback and collaboration in agile development through a simple drawing exercise.
🔹 Step 1: Initial Drawing (No Requirements)
Instruction: Participants are told to "draw a house" with no further details.
Time Limit: 1 minute.
Outcome: Everyone draws based on their own assumptions.
Agile Principle Highlighted:
"Working software over comprehensive documentation"
"Customer collaboration over contract negotiation"
🔹 Step 2: User Feedback
The facilitator (acting as the user) reviews the houses.
Provides feedback like:
Doesn’t like chimneys (ecologist).
Likes bicycles, dislikes cars.
Agile Principle Highlighted:
"Business people and developers must work together daily throughout the project."
"Welcome changing requirements, even late in development."
🔹 Step 3: Second Drawing (With Requirements)
Instruction: Redraw the house, but this time the user gives 3 specific requirements while participants are drawing:
Lots of windows (loves looking outside).
Big garden (keen gardener).
Eco-friendly features (e.g., solar panels, lean-to for a bike).
Time Limit: 1 minute.
Outcome: Drawings are more aligned with user needs.
Agile Principle Highlighted:
"Deliver working software frequently, from a couple of weeks to a couple of months."
"Continuous attention to technical excellence and good design enhances agility."
🔹 Step 4: Comparison and Reflection
Participants compare their first and second drawings.
The facilitator discusses how the second round better met their expectations.
Agile Principle Reinforced:
"The best architectures, requirements, and designs emerge from self-organizing teams."
"At regular intervals, the team reflects on how to become more effective."
✅ Key Takeaways:
Early and continuous feedback leads to better outcomes.
Assumptions without user input often miss the mark.
No comments:
Post a Comment