Skip to main content

What powerful questions does Scrum help you answer?


The video on powerful questions made me think about the deeper purpose of the various Scrum activities. Can I formulate Scrum as a series of Powerful Questions to be general enough, that they might be useful outside of software development? Here is the image I came up with and below are the questions I think each of the Scrum Activities and artefacts strives to help you answer.


Sprint

  • The Sprint is a container to limit ourselves to setting reasonable medium-term goals. 
  • What can we reasonably expect to accomplish by the end of the sprint?

Vision

  • How will our efforts make the world a better place?
  • Who needs our product and why?
  • Why should we build it?

Product Backlog

  • What characteristics should our product have?
  • What goals must we accomplish to achieve our vision?

Backlog Refinement

  • What could we do to get us closer to our vision?
  • What small steps could take us nearer to our goal?
  • How can we make the steps smaller and more likely of success?

Sprint Planning

  • Part 1 - What is the best possible step forward, given what we know today?
  • Part 2 - How can we accomplish these steps?

Daily Scrum

  • What are our goals for the day?
  • How will we accomplish them?
  • What help do we need?
  • Who needs to talk about what?
  • What could be slowing us down?

Sprint Review

  • What have we accomplished or learned?
  • How does this change our vision?

Retrospective

  • How can we work more effectively?
  • What could be slowing us down?

Definition of Done

  • How do we know a step was successful?
  • How do we ensure the quality of our work?
  • How do we know that what was done in the last sprint is still done in this sprint?

Comments

if you are interested in powerfull questions, you might want to look at (or help)

www.twitter.com/Retroflection or
www.retroflection.org for the app version of +2000 questions, posted since 01/01/2010

Popular posts from this blog

Scaling Scrum: SAFe, DAD, or LeSS?

Participants in last week's Scrum MasterClass wanted to evaluate approaches to scaling Scrum and Agile for their large enterprise. So I set out to review the available frameworks. Which one is best for your situation?

Recently a number of approaches have started gaining attention, including the Scaled Agile Framework ("SAFe") by Dean Leffingwell, Disciplined Agile Development (DAD), by Scott Ambler, and Large Scale Scrum (LeSS), by Craig Larman and Bas Vodde. (Follow the links for white papers or overviews of each approach).

How to compare these approaches? My starting point is Scrum in the team. Scrum has proven very effective at helping teams perform, even though it does not directly address the issues surrounding larger organizations and teams. An approach to scaling Scrum should not be inconsistent with Scrum itself.

Scrum implements a small number of principles and constraints: Inspect and Adapt. An interdisciplinary Team solves the problem. Deliver something of va…

Sample Definition of Done

Why does Scrum have a Definition of Done? Simple, everyone involved in the project needs to know and understand what Done means. Furthermore, Done should be really done, as in, 'there is nothing stopping us from earning value with this function, except maybe the go-ahead from the Product Owner. Consider the alternative:
Project Manager: Is this function done?
Developer: Yes
Project Manager: So we can ship it?
Developer: Well, No. It needs to be tested, and I need to write some documentation, but the code works, really. I tested it... (pause) ...on my machine. What's wrong with this exchange? To the developer and to the project manager, "done" means something rather different. To the developer in this case, done means: "I don't have to work on this piece of code any more (unless the tester tells me something is wrong)." The project leader is looking for a statement that the code is ready to ship.

At its most basic level, a definition of Done creates a sh…

10 Warning Signs, that your team is not self-organizing

How do you know that self-organization is working? The Bern Chapter of Scrum Breakfast Club looked into this questions, and identified the following warning signs (which I have taken the liberty of translating).

The team reports to the Scrum Master at the Daily ScrumPeople wait for instructions from the Scrum MasterTeam members don't hold each other responsible [for their commitments]The same impediment comes up twice"That's the way it is" => resignation"I" instead of "We"Flip charts are lonelyCulture of conflict-avoidanceDecisions processes are unclear, nor are they discussedPersonal goals are more important than team goals
To this list I would add my a couple of my favorites:
you don't see a triangle on the task board (not working according prioritization of stories)after the daily Scrum, people return directly to their desks (no collaboration)there are a least as many stories in progress as team members (no pairing)
P.S. You can join the …