The daily scrum as an event map

  • What did I do yesterday that helped the Development Team meet the Sprint Goal?
  • What will I do today to help the Development Team meet the Sprint Goal?
  • Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?
The daily scrum gone bad
  1. It supports everyone articulating what they are doing and blockers
  2. They’re probably familiar with the format
  3. It suits kanban boards which have a lot of value in supporting flow and visualising bottlenecks
  1. You can’t see the day visually and the flow of work
  2. You can’t see the individuals and interactions
  3. You can’t see the desired end state
  4. You only get the snap shot state of the work now (or at some point in the past). There is no “when” on the board.
  5. Sometimes difficult to see how the work relates to the sprint goal
  6. The “did yesterday”, “doing today”, “blocked” is a bit formulaic
  7. I wonder why people wait until the meeting to tell us what they did. Shouldn’t this be real time?
  8. If you’re using jira it suffers from not showing collaboration. Instead you can only “assign” a ticket to one person.
  9. There’s not much sight of what’s going on tomorrow in the event this might be useful.
Individuals and Interactions over time

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
Craig Cockburn

Craig Cockburn

538 Followers

Freelance IT Professional, Lean Agile Coach. Wrote UK's first guide to getting online. Non Exec Director. From Dunblane, Perthshire. www.craigcockburn.com