Iterative and incremental Team Agreements
This process is intended to involve the team in shaping its own work environment and promote a culture of continuous improvement.
This process is intended to involve the team in shaping its own work environment and promote a culture of continuous improvement.
A proper understanding of Agile Manifesto is VERY important for the introduction of Scrum. The twelve agile principles are less abstract than the four values of the Agile manifesto and can be easily understood.
The game is based on an exercise Pocket-sized Principles.
Exercise to show that thinking in categories and principles is helpful and necessary and at the same time, these categories and principles should be checked on a regular basis.
A popular Agile game to remind companies of their Agile roots, to harness collaboration and participation. Discover parallels in Agile and lean in a reflective discussion
The “Penny Game” allows the team to learn through self-organization and observation; specifically, that smaller batches can deliver value to the customer faster. In addition, the game demonstrates that the size of the batches has a direct impact on the delivery. With a large batch, the Workers feel more pressure on themselves to get the batch to the next Worker; with smaller batches, the pressure is lower but more constant.
Become a product owner and get feedback on your ultimate chocolate bar.
Estimation Games are great for starting conversations and honing and tuning estimations before an estimation session. This exercise helps a team to get into the right mindset for estimating and planning for the sprint.
Reach a consensus by grouping user stories according to scope.
This can be used as a retrospective activity, a team reset activity or any time you want to spark some reflection on how you work together as a team.
Often in projects, the learning is all at the wrong end. Usually after things have already gone horribly wrong or off-track, members of the team gather in a “postmortem” to sagely reflect on what bad assumptions and courses of action added up to disaster. What makes this doubly unfortunate is that those same team members, somewhere in their collective experience, may have seen it coming.
A pre-mortem is a way to open a space in a project at its inception to directly address its risks. Unlike a more formal risk analysis, the pre-mortem asks team members to directly tap into their experience and intuition, at a time when it is needed most, and is potentially the most useful.