(English) The Herculean Doughnut

Stay Updated: Posts | Comments   Follow us on Twitter

Désolé, cet article est seulement disponible en English.

VN:F [1.9.16_1159]
Rate This
Rating: 4.5/5 (28 votes cast)
(English) The Herculean Doughnut, 4.5 out of 5 based on 28 ratings
Print Friendly
8 Responses to "(English) The Herculean Doughnut"
  • Jason Morillo %A %e %B %Y at %H:%M

    I found this exercise very worthwhile and provoked great conversation among teams I’m working with transitioning from traditional roles to that inside of a Scrum Framework.

    Adding to the variations, we had our traditional roles on a separate board with duplicate cards so they wouldn’t have to remove them from the doughnut. There we asked them to place them according to current/past responsibilities. This was just an enlightening lesson due to that the scrum doughnut for the most part will look the same, however, the traditional board VARIED so much among the groups we went through this exercise with. Some had 70% of the stuff on the project manager, some had a majority of the items on the BA with very little if any on the business partners/SME.

    VN:F [1.9.16_1159]
    Rating: 0.0/5 (0 votes cast)
  • Nick W %A %e %B %Y at %H:%M

    I use a similar game, though with a Venn diagram instead of a doughnut. This leaves some nice room for discussion as to whether everyone should be responsible for a given role, or whether only two people should. E.g. from your above examples I’d argue that “Motivation of the team” should come from the SM and the Team, but probably not the PO.

    I’m sure there are people out there who’d disagree however….

    VA:F [1.9.16_1159]
    Rating: 0.0/5 (0 votes cast)
  • Sam Whiting %A %e %B %Y at %H:%M

    Thanks for the comments.

    It is, on a visual level, just a less confusing Venn Diagram (shhh don’t tell anyone), however it also emphasises that you can leave things outside for “no one” to do.

    Ultimately, it’s as much a chance for the team to make mistakes they can then learn from as it is about getting it right first time. In my opinion some responsibilities are are not always either prescriptive or obvious to the roles as others. If a PO happens to be a brilliant motivator of people, then seems a shame to waste that natural ability and I think that increases the likelihood that the team will include him in that responsibility. The one benefit I have always got from this is that when finished, whether its what the text book says or not, everyone leaves having accepted responsibilities.

    I am really glad you found it useful.

    VA:F [1.9.16_1159]
    Rating: 4.5/5 (2 votes cast)
  • Berthold Barth %A %e %B %Y at %H:%M

    As with the Planning Poker Game, the journey is the goal here. On top of helping a team make sense of the roles that Scrum offers, the discussions led to a deeper insight into the reasons for the division and left room for discussing ambiguities past and future. Plus it gets the team off their butts.

    VA:F [1.9.16_1159]
    Rating: 0.0/5 (0 votes cast)
  • Richard Scott-Will-Harknett %A %e %B %Y at %H:%M

    Been using this actively for a while now. Great game that drives some very interesting conversations. I added to the list of activities/responsibilities and threw in some others such as dealing with budget, risk, performance management, motivation, creating status reports, and other things I seem to remember from my project management past (its alright I’m better now!) etc. – As Bethhold said this is so much more about the the journey. Its the conversation that is really important. Nice one Sam – thanks.

    VN:F [1.9.16_1159]
    Rating: 5.0/5 (1 vote cast)
  • Raymond Simplice %A %e %B %Y at %H:%M

    Sam, this is a great game. It definitely promotes team collaboration, and allows everyone to participate and have fun at the same time. But, I work a lot with distributed teams, it’s unfortunate, distributed teams don’t seem to have a fair shot at this game.

    VA:F [1.9.16_1159]
    Rating: 0.0/5 (0 votes cast)
  • Ken Coomes, CSM %A %e %B %Y at %H:%M

    Thanks for the initial work, Sam! Like so many others, we have found it useful, mainly as a discussion starter. I changed it to “SCRUM-ptious” Donut Game (Herculean fits, as it is very large, but I couldn’t resist the word play.) We added a few others, and changed some of the wording. And to echo what many have said, it’s more about the journey; not about getting it right immediately. Our experience helping teach has been distinguishing between the “book” answer for some and our own real world examples. And we bring in donuts to get started, which is always a big hit.

    VA:F [1.9.16_1159]
    Rating: 0.0/5 (0 votes cast)
  • popi makris %A %e %B %Y at %H:%M

    i LOVE this game and play it with ALL new teams after i have reviewed the scrum framework – this is part of the Review we do on day 2 of team training. Thank you so much Sam!

    VA:F [1.9.16_1159]
    Rating: 0.0/5 (0 votes cast)
Leave a Reply:

Spam Protection by WP-SpamFree


Discuss Comments
Agile Games Group