Workshops: Internal workshops to identify feature direction and process.
KJ Technique Workshop
The KJ-Method, named for its inventor, Jiro Kawakita (the Japanese put their last names first), allows groups to quickly reach a consensus on priorities of subjective, qualitative data.
Sometimes team members have different opinions on how we should proceed with coming to a consensus for road map features. Other times, tons of subjective data from hours of user testing are collected to inspire future features. The KJ-Technique is an effective workshop for organizing and prioritizing opinions and subjective data.
I Wish : In this method we started with a silent "I Wish" session where stakeholders would rapidly write down features (no matter how serious they are) on sticky notes. These features would be color coded depending on what part of the product it pertains to.
Share : After the 15 minutes are up stakeholders will place thier ideas based on their color up on a white board or wall. For 10 minutes everyone reads silently and adds any features that are inspired from other ones.
Group : Stakeholders now organize the sticky notes based on similarity. If questions come up, they can talk about them but not if it is about debating the validity of a feature.
Name : After all of the features are grouped the team names each grouping or theme that was discovered.
Vote : Individually the team comes up and votes on their top three themes to be addressed in the future road map.
FEATURE to Developed workshop
The purpose of this workshop was to understand how product owners, scrum masters, and development leads manage tasks and prioritize unexpected events. The goal was to identify parts of our process that can be adjusted increasing organization and to allow team leads the freedom to explore worst case scenarios within their development process.
Setup : Every person on the team is presented as a sticky note and grouped in their respected teams. Tasks are created of varying degrees of difficulty and placed out of the room to be brought in at opportune moments. Name badges are created to represent client roles and other stakeholders. Lastly a scrip is created to navigate the team through the journey of possible scenarios.
Mediation : During the workshop a "client" would walk in and add tasks to the backlog and the team would start prioritizing, sizing, and assigning the work. Slowly throughout the workshop events such as "three people get sick" are thrown into the mix to see how the team will respond and adjust.