Планируете вашу следующию аджайл ретроспективу? Начните со случайного плана, адаптируйте его к вашей команде и ситуации, распечатайте его или поделитесь URL вашего плана с другими. Или просто полистайте в поиске новых идей!
Are you running your retrospectives with Miro? Create prettier boards faster with the giant Retromat Miroboard Mega Template!
Tackle the 7 Wastes of Software Development Source:
Tony O'Halloran
This activity facilitates a broad discussion around waste, using the 7 Wastes of Software Development from Lean Software Development by Mary and Tom Poppendieck.
Prepare the room with 7 flip-chart sheets, each representing a category of waste. Be sure to give enough room for small groups to stand around them, so spread the sheets out across the room!
The 7 categories of waste are:
Partially Done Work
Is work going from beginning to end in a single rapid flow? For example; are you building up large amounts of untested or undeployed work? Do you have long-lived feature branches?
Extra Features
Do your customers or users actually need what you’re building?
Relearning
Do you spend a lot of time rediscovering what you (or someone else on your team) already knew at one time?
Handoffs
Is your team truly collaborating, or handing off bits of work to each other, losing tacit knowledge in the process?
Delays
Does work typically spend lots of time stalled awaiting things like environments, someone to be available, or decisions to be made?
Task Switching
Do you find that you lose time to context switching frequently?
Defects
Does your team have a low defect rate? How late in the development process do you find defects? Could this feedback loop be shorter?
To start, briefly describe each of the different types of waste (more in-depth information here). Then pose the core questions:
In which situations do we incur this type of waste?
Where do we do a good job of avoiding this type of waste?
Break into groups of 2-3 people, preferably with a mix of roles in the groups. This helps to build awareness of the waste everyone else is dealing with on your team. Then, each group selects their first topic and spends a short amount of time writing post-its to answer the two questions above. Limit it to 2 or 3 minutes per topic and 2 post-its per person for each topic to avoid getting swamped with data. When the timebox is up, each group cycles to the next category until everyone has had an opportunity to contribute to each.
What themes are emerging? What do participants notice? Use dot-voting to decide which topics are important enough to further discuss in the next phase.
Антон работает Скрам коучом и тренером со множеством разных организаций. Линк на его тренинги для Скрам мастеров - CSM и владельцев продукта – CSPO. Пишите ему на Twitter!
Когда Корина работала скрам мастером она сама нуждалась в Ретромате.
В конце концов она сама построила его в надежде на то, что он и другим поможет.
У вас есть вопросы, предложения или тёплые слова?
Пишите ей или
читайте её Twitter.
Если вам нравится Ретромат, вам может понравится блог Коринны и
её сайт с обзорами и распечатками Wall-Skills.com.
Тимон проводит скрам тренинги. Oн использовал Ретромат на протяжении долгого времени как разработчик, владелей продукта, скрам мастер и аджайл коуч. С 2016-ого года он разрабатывает Ретромат вместе с Коринной и вносит много своих идей. Вы можете написать ему email или читать его на Twitter.
