If you're new here, you may want to subscribe to my RSS feed. Thanks for visiting!
We had our first Daily Scrum. It took 16 minutes. I minute too long. Our ScrumMaster asked each of us the 3 Scrum questions:
- What have you done since yesterday's meeting?
- What are you going to get done today?
- What impediments (obstacles) do you need to be removed?
What do I know? I'm just a beginner. A happy beginner!
We got through the questions in under 10 minutes. We then asked follow-up questions to some of the team members' responses. One issue was left to be addressed by tomorrow's Scrum. Once the meeting was closed I called for a Spike1 to address the issue with three people on the team. In 5 more minutes we resolved an assignment that in other settings might have taken a number of phone calls, emails, and interruptions. Spike over!
I've been thinking quite a lot about "inspect and adapt." There is a direct parallel to Deming's plan-do-check-act. I still haven't had a conversation with our ScrumMaster about it. I'm wondering, is inspect and adapt short-hand? I'm probably missing something, but I'd expect to be clear about my hypothesis so I know what to inspect for. But what do I know? I'm just a beginner. A happy beginner!
By the way, I forgot to ask the others to stand during the Scrum meetings. I stood, fidgeted, made a few notes, and fidgeted some more. I'll ask the others to fidget with me tomorrow.
- The word spike refers to a focussed high level of engagement to get just one thing done. Everything else is on hold for that time. [ ⇑ back ]
? Guy Kawasaki wrote, "Less is the new more." Easy to learn: symmetry, seduction, subtraction, and sustainability. Very valuable to do. Step 1: Read Matt's book!! just 140 keystrokes.
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=03314884-90d1-47e5-acf3-2821313e9fdc)
![Reblog this post [with Zemanta]](http://img.zemanta.com/reblog_e.png?x-id=4ce3f392-8989-448a-a97a-c1432dd3fce6)