Posts Tagged ‘kick-off’

Scrum Ceremony Puzzle

Posted: November 19, 2018 in facilitation, Scrum
Tags: , , ,

Image result for puzzleThis is a “game” I played as a kick-off activity with a new team. Thought I would share in case someone might find it useful 🙂

The basic idea is to match the correct Purpose, Outcome(s) and Output(s) to each Scrum ceremony.

Preparation:

  • Print out the Ceremony Boards (each team will need its own set)
  • Prepare the Ceremony Cards (each team will need its own set)

Game Play:

  • Place the cards on the boards in the correct spaces
  • The cards are colour coded as a Purpose/Outcome/Output to help

How we played it:

  • I divided my participants into two teams and made a bit of a competition of it.
  • Both teams started in opposite corners of the room and ran to a table in the middle to try solve the puzzle.
  • When a team thought they had solved it, they would signal and both teams went back to their respective corners (think “Survivor style).
  • I would then check the solve against my solution. If the team had solved the puzzle correctly, then they were the winners. If the solution was not correct, both teams could return to their tables to continue working on the puzzle.

Feel free to try out the game and give me feedback!

Resources:

Advertisements

#SGZA 2016: Kick-off to Lift-off

Posted: January 11, 2017 in Agile, Team
Tags: ,

I recently attended the regional Scrum Gathering for 2016 in Cape Town. This is a post in a series on the talks that I attended. All posts are based on the sketch-notes that I took in the sessions. 

dsc_0465

This talk focused largely on the Context section of the Agile Charter, which is meant to be a living set of artifacts and sessions that help a team clarify their Purpose, Context and Alignment. Alignment, in particular, is a part that will probably adjust frequently as team members interact: often daily. The hypothesis is that a team that starts well may not necessarily finish well; but a team that does not start well will never finish well. In other words, a good kick-off is required for (a team) to lift-off.

The first part of Context is “Boundaries and Interactions“. This is understanding who your team members are; how you will interact with each other; how you will interact with others who are not in the non-core team; who these non-core team parties are; and how we will communicate over differences. Steve described one cool activity to kick this off. For the core team, have everyone create a name-card with a photo/image, their name, their talent, and one fun fact. The team places these cards in the center of a sheet of sorts and then draws a boundary around the group. This indicates the boundary between the core team and anyone who isn’t in the core team.

The team then discusses who else may be

  • Interesting to the team (they can give advice/we value their opinion/they have input);
  • Important to the team or project (key knowledge / have to approve or provide things); and
  • Interested in the team or project

These people or groups are then represented outside of the circle and the team discusses and agrees how the core team will interact with these parties. This could be fleshed out further into some kind of communication plan, however it is necessary to balance too much detail and complexity against something that is quick to review and update as it changes. Remember: the Agile Charter should be a LIVING artifact.

The second part of Context is “Committed Resources“. In this instance, we do mean resources/things and NOT people. The proposed activity for this is to draw a timeline arrow with the end point being the mission for the release (agreed in the Purpose section). The team then makes a list of things / activities / skills they will need to achieve the mission and places them on the timeline depending on when they will be required. These can also be ranked in terms of importance. The team then highlights (e.g. using a red dot) resources that the team does not yet have. The idea is that one needs to confirm the missing resources before the time when they are required is reached.

The third and final part of Context is “Prospective Analysis” or “The analysis of prospects”. Basically this means looking at things that might happen and identifying whether they are risks or opportunities. An easy way to do this, once the team has a list of things that might happen, is to categories them into a quadrant with the vertical axis of [Good]-[Bad] and a horizontal axis of [Won’t Happen]-[Will Happen].

Have you ever done a kick-off with your team? What parts of the Agile Charter have you found particularly useful? Which parts have you not experienced as valuable?