neroay.blogg.se - Tasty blue game android

Tasty blue game android update#
Tasty blue game android download#

“Interesting, we only created parts of PBIs, but the most important PBI also did not get done.

Tasty blue game android update#

Update the Velocity Chart for each team.what is your velocity? Nice all worked very hard.SKIP Sprint 1 and ask the teams to come up with a proposal to fix it. IF they say something like: this is stupid, we cannot complete a PBI because it required multiple components THEN say yes that is the result of component teams. Give each team a PBI and then you can start Sprint Planning of 1 min.ĮXPLAIN AGAIN: You can only work on your own speciality because otherwise, that would not be efficient 🙂.GOAL: Understand that there is a mess and propose to introduce an Analysis Team.REMEMBER: You can only work within your own speciality and use your own colour sticky notes. Explain: You are DEVELOPMENT team with all the skills from development, to testing to ship your speciality colours.For example: “You are 1, you are 2 you are 3 etc”.So, first step: Let’s organise into DEVELOPMENT teams Enough wall space for the end product ‘LeSS = Scrum”.Table space for the Integration Team as far away as possible from the development teams.Table space for the Analysis Team as far away as possible from the development teams.Each team needs a flipchart or wall space with A0 papers and also their colour stick notes.It is ordered in Value and it already has estimates on it you see. The order of the PBL is from left to right: “LeSS = Scrum”. Glue the Product Backlog on a wall or door in priority order en explain the PBIs.We Improve the system based on your feedback from the retro.You can introduce other types of teams.You cannot form other DEVELOPMENT teams.Retro for improvement of the system 2 min.Create a Velocity Chart for the 5 teams for 5 Sprints.Ĭreate on an A0 Paper the rules of the Game to that it is visible during the game.We are going to track the teams’ velocity to see progress each Sprint for each team, to use it for Sprint Planning and to track PBIs done.

Tasty blue game android download#

PRODUCT BACKLOG ( DOWNLOAD HERE)ĮXAMPLE DECOMPOSITION OF LETTER ‘E’ ( DOWNLOAD HERE)įACILITATOR GUIDE Step 0. Out of the organisational design improvements, you choose 1 proposal and implement it. The facilitator of the game acts of the owner and has final say on organisational design and acceptance of the product.Īfter each retro, the facilitator leads a discussion about the dynamics that are observed and the teams’ proposals for improvement. ( what dynamics do we see and what can we do to improve? ) and end the Sprint with 2 min of retro where each team proposes an improvement.Then we have a 2 min development episode.Start each Sprint with 1 min of Sprint Planning.The teams do the following steps in parallel but synchronized: Why Scaling Scrum is the Wrong Question to ask at.PAPERS TO HANDOUT FOR FURTHER READING AFTER THE GAME. WhiteBoard/Flipchart where you keep track or progress.Game Rules that everyone in the room can see.These are needed for the Analysis team to do the decomposition (download here) Printed decompositions of PBI letter ‘e’, see below for an example of letter ‘e’ ( download here ).

1 Printed Product Backlog, see below an example.

Caps or Hats 1 Program Manager Cap, 5 Integration Team Caps, 5 Product Owner Caps, 2 Project Manager Caps.

Thick sharpies for each colour for the Analysis Team.

5 flip charts or A0s and wall space for the teams to work on.

So, there is 1 team per colour sticky note and we have a Red team, a Blue team etc. The teams are organised into single function teams. In order to build our product, we work in teams of at most 5 people. The product that we need to create is the text “LeSS = Scrum”. At our company, the specialities we have are Sticky notes of colour Blue, Red, Green, Orange and Yellow. Some companies have Java, Android, iOS, MainFrame, SAP, Billing, Legal etc as specialities. These skills need well-educated people with lots of experience working on the single speciality. Our product consists of several deep specialities. We develop graphics using only Sticky notes. We are a product development group of a company called StickyArts. And then need to add all kinds of extra complexity to their organisation. What they do is scaling by adding Scrum Teams and as a result, they have multiple Scrum Teams instead of multiple team Scrum. In this game, you experience how a typical scaling approach I call “Copy Paste Scaling” results in not so good things in organisations.Ĭopy Paste Scaling is what I see most companies do. The goal of this game is to understand how organisational design using component teams leads to the waterfall and unnecessary complexity.