AgileMe - User contributions [en]

Collaboration Frameworks

2018-11-30T00:00:49Z

Sbargon: /* Collaboration Activities & Workshops */

[[Category:Agile:Articles]][[Category:Agile:Scrum]][[Category:Agile]]

Collaboration frameworks are interactive techniques used with the Scrum Team to generate new ideas, explore assumptions and rationalise existing concepts.

Categories of collaboration frameworks include:
* Understanding – how can we improve our understanding of the problem?
* Exploring – how can we consider a range of ideas and concepts and expand our understanding of the possibilities?
* Evaluating – how can we consider multiple perspectives and critically evaluate the ideas?
* Converging – how can we rationalise our ideas and converge on a great solution?

==Collaboration Activities & Workshops==
Below are some examples of collaboration frameworks and how they can be used:
* [[2 Min Brainstorm]]
* [[Affinity Mapping]]
* [[Dot Voting]]
* [[Fist of Five]]
* [[Radio Tuning]]
* [[Selection In A Range]]
* [[Decisional Balance Sheet]]
* [[Quadrant Chart]]
* [[Note & Vote]]
* [[Dump & Sort]]

==See Also==
* [[Product Owner]]

Bento Box Challenge

2018-11-22T03:23:16Z

Sbargon: Switched file for media

[[Category:Agile:Workshops]][[Category:Agile]]
==Introduction==
The Bento Box Challenge is intended for teams that have at least 1 year's agile experience in using agile practices, and are now becoming stagnant and need to get some deeper insights into the agile principles and simplify their approaches to software development.

The workshop challenges 4 x teams of 4 people to work across a number of dimensions as they create training elements for a central task. The workshop is split between 4 iterations or experiments as the teams are taken on a journey that challenges their approaches of how they can work together.

The outcomes of the workshop are a shared learning experience that continues after the workshop. It is quite possible that teams may change their thinking style about agile as a result of the workshop, and may not be able to freely express what they have learned at the end of the workshop. Hence, the final debrief section is very important to help the teams assimilate the experience and their feelings towards what they have achieved and how they did it.

A post workshop get together is recommended a week or so after the workshop to help the team process what they have learned and how they have applied it within their workplace.

<pdf width="500" height="500">File:Bento_Box_Notes.pdf</pdf>

==Dimensions==
# The first dimension are the work streams or elements of the Bento Box. Each team selects one of the work streams to produce their element of the Bento Box. A completed Bento Box has each of the elements completed for the central task. Work streams and elements can be selected in an overt way with teams self selecting, or in a covert way by blindly selecting a card or opening an envelope which reveals their element as a bit of theatre. The elements of a Bento Box generally include:
#* a video
#* a podcast
#* an infographic
#* a learning tool
#The second dimension are the challenges that the teams face through each iteration and experiment, with a new challenge being presented at the start of each experiment:
#* The first challenge is "Overcome". Teams will need to orientate themselves to the tasks and will need to crash through their initial fears and anxieties to get ahead. Hence this challenge is about enabling the teams to create their first prototype quickly and reduce the procrastination that they may be experiencing
#* The second challenge is "Harmonise". The teams may have worked well in the first challenge, but may have become self serving with a narrow focus. Hence, this challenge is about broadening the teams' horizons to consider what the other teams are doing and how can they support them and harmonise to provide a well balanced Bento Box
#* The third challenge is "Evolve". The teams may begin to work well with the other teams, and now this challenge is about industrialising their approaches and learning how to do more with less
#* The fourth challenge is "Transcend". The teams might be working well together to produce consistent outputs, however, the challenge is now about what deeper insights into the way that they are working they have, and can they now break all of the rules to arrive at something new.
#The third dimension are the learning styles used to learn about the central task. These include:
#* Learning by receiving knowledge, either reading or other means of information acquisition
#* Learning by understanding as the teams begin to process what the information means and position their elements in the Bento Box
#* Learning by doing, as the teams begin to build the elements of the Bento Box
#* Learning by teaching, as the teams begin to tune their elements of the Bento Box to teach others about the central task
# The fourth dimension, which is optional but seems to work well for a half day workshop, is the application of the four agile manifesto values. This could be done as the central task, with each value being the central task to deliver for each of the experiments. Hence, at the end of the workshop the resulting Bento Box would have 4 x agile manifesto values with each one having 4 x elements that can be used to teach others about the agile manifesto values.

[[File:Bento_Box_Main_Graphic.jpg|500px|Bento Box Elements]]

==Learning Objectives==
* How to simplify their approaches to creating an output
* Realisation of what being agile is rather than just doing agile
* Raises deeper questions about their approach to agile

==Materials==
* Workshop [[Media:KanBan_Cards.pdf|Kanban Cards]] + [[Media:Debrief_Kanban_Cards.pdf|Debrief Kanban Cards]] to communicate the flow of the workshop
* Task materials e.g. [[Media:Agile_Manifesto_Task_Cards.pdf|Agile Manifesto Values Cards]] as the task to be worked on by the 4 Bento Box Elements
* Run sheet for the facilitator
* Timer to help the teams understand the rhythms of the workshop
* [[Media:Challenge_Cards.pdf|Challenge Cards]] + envelopes
* [[Media:Experimentation_Card.pdf|Experimentation Cards]]
* [[Media:Feedback_Card.pdf|Feedback Cards]]
* [[Media:Speed_Dating_ID_Cards.pdf|ID Cards]] for speed dating and team formation
* 4 x [[Media:Bento_Box_Graphic.pdf|Bento Box Graphic v1]] or [[Media:Bento_Box_Main_Graphic.jpg|v2]] to communicate how the elements fit together and the expectations
* 4 x Bento Box Elements to help the team identify with their particular Bento Box element:
** 1 x Bento Box Element: [[Media:Bento_Box_Infographic_Team_Graphic.pdf|Infographic]]
** 1 x Bento Box Element: [[Media:Bento_Box_Learning_Tool_Team_Graphic.pdf|Learning Tool]]
** 1 x Bento Box Element: [[Media:Bento_Box_Podcast_Team_Graphic.pdf|Podcast]]
** 1 x Bento Box Element: [[Media:Bento_Box_Video_Team_Graphic.pdf|Video]]
* [[Media:Debrief_Cards.pdf|Debrief Cards]]
* Flip chart paper + markers
* Post it notes + sharpies
* Desk bell for the speed dating component
* iPad or similar to create videos
* Smart phone or similar to create podcasts
* A3 paper to create infographics
* Masking tape to mark out the Bento Box graphic on the floor
* Creative materials to create learning tools e.g.
** paddle sticks
** balloons
** tape
** clips and pins
** coloured markers
** pipe cleaners
** pong balls

==Workshop Flow==
===Connections===
The connections of the workshop include the following aspects:

# connection to the workshop - opening is done with an opening circle to allow the attendees to reframe and get in tune with the workshop
# connection to each other - speed dating is used as an activity to meet other people and derive how the teams are to be formed
# connection to the task - introduction of the task at hand and which bento box elements the teams will provide
# connection to the methods - descriptions of the challenges within each iteration are introduced via a card in an envelope opened at the start of each iteration

===Concepts & Concrete Practice===

Concepts are introduced with a challenge card and a task card in envelopes that are opened at the start of each iteration. The iterations are then started with the teams responding to the task and challenges to product the outputs of the Bento Box. Depending upon the task, there may be supplied equipment and information in the form of concept centres for the teams to use to produce the Bento Box of training materials.

The emphasis is on learning through understanding, applying and then teaching others, as the teams incorpoate new information from the concept centres, apply it to their Bento Box elements that they are producing, and then using the outputs to teach others.

===Conclusions===
Conclusions are provided with a structured debrief with cards to evoke deeper observations or feelings experienced during the workshop. A reasonable amount of time for a paced and structured debrief allows the attendees to provide some structured self reflection and deeper insights into the experience, and allows them to learn from their activities.

In addition, there may also be a follow up discussion exercise where the teams reform to discuss what subsequent insights and observations they made after the course and how they have applied their learning to the work.

==Half Day Implementation==

{| class="wikitable"
! Start
! Finish
! Duration
! Item
! Notes
|-
|08:30||09:00||30 mins||Arrive||
|-
|09:00||09:40||40 mins||Welcome + Connection||* Opening circle - 5 min * Speed dating - 15 min * Team formation - 5 min * Explain task - 5 min * Explain the mechanics of the workshop - Bento Box Graphic - 5 min * Stream selection - Bento Box Team Graphic - 5 min
|-
|09:40||09:45||5 mins||Experiment #1: Intro||* Introduce next part of the Task * Introduce next challenge - OVERCOME
|-
|09:45||10:05||20 mins||Experiment #1: Build||* Build prototypes with the equipment provided
|-
|10:05||10:15||10 mins||Experiment #1: Feedback & Insights||* Participants provide feedback to the teams e.g. market place or sequential depending on number of attendees
|-
|10:15||10:20||5 mins||Break||
|-
|10:20||10:25||5 mins||Experiment #2: Intro||* Introduce next part of the Task * Introduce next challenge - HARMONISE
|-
|10:25||10:45||20 mins||Experiment #2: Build||* Build prototypes with the equipment provided
|-
|10:45||10:55||10 mins||Experiment #2: Feedback & Insights||* Participants provide feedback to the teams
|-
|10:55||11:00||5 mins||Break||
|-
|11:00||11:05||5 mins||Experiment #3: Intro||* Introduce next part of the Task * Introduce next challenge - EVOLVE
|-
|11:05||11:25||20 mins||Experiment #3: Build||* Build prototypes with the equipment provided
|-
|11:25||11:35||10 mins||Experiment #3: Feedback & Insights||* Participants provide feedback to the teams
|-
|11:35||11:40||5 mins||Break||
|-
|11:40||11:45||5 mins||Experiment #4: Intro||* Introduce next part of the Task * Introduce next challenge - TRANSCEND
|-
|11:45||12:05||20 mins||Experiment #4: Build||* Build prototypes with the equipment provided
|-
|12:05||12:15||10 mins||Experiment #4: Feedback & Insights||* Participants provide feedback to the teams
|-
|12:15||12:20||5 mins||Break||
|-
|12:20||12:50||30 mins||Debrief||* Debrief cards in pairs + shareback
|-
|12:50||13:00||10 mins||Close||* Closing circle
|}

Build Your Scrum Framework

2018-11-22T02:44:31Z

Sbargon: Changed file to media

[[Category:Agile:Workshops]][[Category:Agile]]
==Introduction==
This exercise is an upgrade from Build Your Own Scrum, (Weisbart 2018), which was seen to be out of date with the latest Scrum Guide. The tools are based upon the 4 C’s approach described in Sharon Bowman’s Training From The Back of The Room (2009) (Bowman 2009).

==Learning Objectives==
The intended learning objectives for the intended Build Your Own Scrum workshop includes the following:

Begin to understand how the Scrum framework fits with events, roles and artefacts

==Materials==
The materials needed for the workshop include:

* Printed [[Media:Scrum_Framework_Shapes.pdf|framework shapes]] 1 per group
* Printed [[Media:Scrum_Framework_Arrows.pdf|arrows]] 1 per group
* Flip chart paper, 1 for each table group
* Blu-tac or similar for sticking to the walls
* Scissors
* Copies of the [http://scrumguides.org Scrum Guide] document, 1 per group
* Copies of the [http://scrumprimer.org Scrum Primer] document, 1 per group
* Copies of the [[Media:Scrum.jpg|Scrum poster]], 1 per group

==Workshop Flow==
===Connections (5 Minutes)===
# Start by asking the attendees to split into table groups of 4 and to acquire the necessary materials to start for each table group.

===Concepts (0 Minutes)===
# Introduce the reading materials from the Scrum Guide or Scrum Primer.

===Concrete Practice (25 Minutes)===
# Ask the attendees to construct their respective Scrum models using any means necessary e.g. using the handouts and any web based resources they can find.

===Conclusions (15 Minutes)===
# Conclude with a show and tell with each table group presenting their models to the attendees
# Facilitate any questions with the models
# Finish up with a diagram of the Scrum framework and walk the attendees through the industrial recognised Scrum framework

==References==
* Training From The Back of The Room, Sharon L. Bowman, Pfeiffer, 2009
* https://weisbart.com/byos, Adam Weisbart, accessed 2018

My Sweet 16 Birthday Party

2018-11-22T02:27:49Z

Sbargon: Changed file link to media links, so you don't see the boring description page

[[Category:Agile:Workshops]][[Category:Agile]]
==Introduction==
This workshop is loosely based upon the MTV series "My Super Sweet 16" from 2005-8 and is intended to provide the attendees with some hands on user story creation, categorisation, estimation and release planning experience with the use of a simple scenario around planning a large 16th birthday party.

This exercise provides some experience in creating a Product Backlog in the form of a Story Map, estimating Product Backlog Items, attributing business value to items, and crafting a release plan for 5 Sprints.

==Learning Objectives==
* To be able to create new Product Backlog Items and form a meaningful Product Backlog in the form of a story map
* To order the items in a meaningful way
* To be able to estimate items
* To form a basic release plan

==Timings==
Allow for 90 minutes for table groups to successfully complete their tasks

==Materials==
* Each attendee should have a printed copies of:
** [[Media:My_Sweet_16_Birthday_Party_Worksheet.pdf|My Sweet 16 Birthday Party Worksheet]]
** [[Media:My_Sweet_16_Birthday_Party_Poster.pdf|My Sweet 16 Birthday Party Poster]]
** [[Media:User_Story_Anatomy_Poster.pdf|Anatomy of a User Story Poster]]
** [[Media:Affinity_Estimation_Poster.pdf|Affinity Estimation Poster]]
** [[Media:Planning_Poker_Poster.pdf|Planning Poker Poster]]
** [[Media:Ouija_Board_Sizing_Poster.pdf|Ouija Board Sizing Poster]]
** [[Media:Kano_Analysis_Poster.pdf|Kano Analysis Poster]]
** [[Media:MVP_Poster.pdf|MVP Poster]]
** [[Media:Buy_A_Feature_Poster.pdf|Buy a Feature Poster]]
** [[Media:Story_Mapping_Poster.pdf|Story Mapping Poster]]
* Post-it notes
* Marker pens
* Planning Poker cards
* Poker Chips
* Sticky dots
* Sticky stars
* Flip chart paper
* A4 paper

==Workshop Flow==
===Scenario===
The scenario is that your team is working for a high-end party planning company, and one of our most prestigious customers wants to provide a 16th Birthday Party for his daughter, Kelly.
The budget for this party is in excess of $300,000 and in addition there will be a car for the birthday girl presented by the parents.
Kelly has provided a poster of the things that she likes and describes her expectations for the party.

===Tasks===
# As a team review Kelly’s poster of her interpretation of the birthday party
# Perform a 2 minute brainstorm on post-it notes to derive some high level ideas about the party
# Review the “Story Mapping” poster and draw a story board of the user experience from the guests’ and Kelly’s perspective
# On two sheets of flip chart paper arrange the story board diagrams across the top to form the user journey and the expected outcome of the party
# Decompose the user journey into epics to form the categories of things needed to be done to achieve the user experience
# Break down the epics into Product Backlog Items with some information from the “Anatomy of a User Story” poster. The Product Backlog Items will form your to do list of the work to be done to achieve the user experience
# Estimate the Product Backlog Items using one of the following techniques, (the facilitator has the equipment needed):
## Planning Poker
## Affinity Estimation
## Ouija Board Estimation
# Attribute business value to the Product Backlog Items using one of the following techniques, (the facilitator has the equipment needed):
## MVP
## Kano Analysis
## Buy a Feature
# Add post it notes down one side of the Story Map indicating Sprints 1-5 to form swim lanes for each of the Sprints
# Adjust the Product Backlog Items between the Sprint swim lanes to form a release plan over the 5 Sprints
# Call over the facilitator to review and discuss

==References==
# [http://www.mountaingoatsoftware.com/agile/planning-poker http://www.mountaingoatsoftware.com/agile/planning-poker], accessed 2014
# [http://en.wikipedia.org/wiki/Kano_model http://en.wikipedia.org/wiki/Kano_model], accessed 2014
# [http://www.agileproductdesign.com/downloads/user_story_mapping_quickref_comic.pdf User Story Mapping Quick Reference Guide], 2014