(English) Traditional vs. Agile Approach of Managing Work

Stay Updated: Posts | Comments   Follow us on Twitter

Sorry, this entry is only available in English

VN:F [1.9.16_1159]
Rate This
Rating: 4.7/5 (10 votes cast)
(English) Traditional vs. Agile Approach of Managing Work, 4.7 out of 5 based on 10 ratings
Print Friendly
8 Responses to "(English) Traditional vs. Agile Approach of Managing Work"
  • Ben Maynard Июнь 24, 2016 в 2:02 дп

    Hi Aleem

    Played this game yesterday and it went down very well. I had to teams and in addition to recording estimated vs. actual I also recorded waste/inventory (eggs partially complete at the end of each delivery iteration).

    Question for you when working in an agile way, at the end of each iteration, do you have teams discard partially completed eggs or allow them complete them in the next iteration?

    VA:F [1.9.16_1159]
    Rating: 5.0/5 (1 vote cast)
  • Aleem Khan Июнь 24, 2016 в 12:13 пп

    Glad to know that your game went well.

    I discard partially completed eggs after every iteration. But you brought up a good point, and it can be discussed during the debriefing section of the game i.e. partially completed work won’t count toward the velocity (stories are either done or not done). And continuing to work on unfinished work is up to the PO’s discretion.

    VN:F [1.9.16_1159]
    Rating: 0.0/5 (0 votes cast)
  • Vanitha Октябрь 17, 2016 в 5:05 дп

    Hi,

    For the first method, whether the entire team plays the game together for 3 min,6 min,3 min or the team splits into sub teams at the beginning of the game and group doesn’t change for both the methods.

    VA:F [1.9.16_1159]
    Rating: 0.0/5 (0 votes cast)
  • Aleem Khan Октябрь 17, 2016 в 4:41 пп

    Hi Vanitha – the team structure remains the same for both approaches.

    VN:F [1.9.16_1159]
    Rating: 0.0/5 (0 votes cast)
  • Alper Май 27, 2017 в 5:25 дп

    Thanks for sharing, I am planning to use this game in my trainings.
    I have a recommendation. Between iterations, you can change the requirements, say you now want three colour eggs (they can be optional too) that will be more of a value – maybe will be counted as x2 when they finish. That is going to demonstrate the importance of shorter iterations and customer feedback.

    VA:F [1.9.16_1159]
    Rating: 0.0/5 (0 votes cast)
  • Aleem Khan Май 27, 2017 в 7:00 дп

    It’s an excellent idea to introduce shorter feedback cycle, my only caveat I would say, do not introduce many concepts at once. Adding more iterations and introducing new concepts won’t be a bad idea. Let me know how did it go.

    VN:F [1.9.16_1159]
    Rating: 0.0/5 (0 votes cast)
  • Ti Mougne Сентябрь 5, 2017 в 11:41 дп

    I ran this activity with one team of 5. They are new to Scrum, and at this point are operating in a traditional silo team structure. The game was great! We only recorded estimates vs. actuals, and we allowed unfinished work to carry over, but we reduced the actual delivered count by the waste (and those that were incomplete were considered waste). One thing I’d do differently next time is to allow the team to estimate (upfront) the total count to deliver at the end of the 3 sprints (representing the release plan), but then allow them to adjust their sprint estimates each time via learnings. I’d also add the SM role to the game to help facilitate the learnings of the team each sprint.

    VA:F [1.9.16_1159]
    Rating: 5.0/5 (1 vote cast)
  • Ravi Сентябрь 7, 2017 в 1:32 пп

    Thanks for sharing this game.

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

Spam Protection by WP-SpamFree

Login

Discuss Comments
Agile Games Group