On October 31th 2014 I attended the Agile Tour Brussel 2014 (#ATBRU) conference for the first time. One of the sessions was on Scrum in Industry (Scrum beyond Software series). Xavier Quesada Allue and his college shared their experience in implementing scrum at a supplier of Volvo. This supplier produces parts for the Volvo plant in Gent. I really loved this session. Xavier wore the normal outfit at the manufacturing plant: special jacket and safety glasses. Next he showed a nice video for setting the scene.
The supplier was experienced with lean and improvements but was not able to create and overview of all improvement actions and priority. They wanted to see if Scrum could help. Scrum was used first to create teams. A team was responsible for implementing improvements in a certain area. Next a physical scrum board was used to create overview and create a flow. The sprints where used to focus on the most important improvements. The sprint demo and review was used to show the results and improve the scrum process.
In two different contexts I introduced Scrum for non-IT. Recently I implemented scrum in a governmental agency. This team needed to deliver a “Legger”. A “Legger” is a formal document explaining the waterways and who is responsible for maintaining the waterway. The Legger team was highly dependent of other departments within this agency. The Legal department was needed for legal governance and the Policy department was needed to formulate new Policies. All guidelines for the delivery of the “Legger” documents. Next projects changing the waterways needed to deliver Geo data on bridges, pumping station etcetera on order to deliver a map.
There were some interesting parallels in mine and Xavier’s experiences:
- Both teams had difficulty maintaining their workload because external dependencies continuously changed priority.
- Teams and team members had difficulty to focus. They handled a lot of activities in parallel.
- Introducing scrum with a physical scrum board (Visualization) or task board helped teams to get more control on the workload. It’s interesting to see teams tend to change the way the board is setup (number of columns, swimming lanes, coloring) .
- Introducing the sprint planning session helped the teams to focus on the highest priority work.
- The daily scrum helped the team to keep focused.
- The scrum retrospective helped the team to learn and improve.
The Legger team had great trouble delivering the committed work (user stories) in the first 2 sprints. After sprint 2 retrospective and intervention on time management the team was able to finish the planned work in halfway sprint 3. This result was a great result for the team and team development.
In my opinion scrum for non-IT can be of added value for many non-IT teams. The Scrum process and roles can help teams to improve. During the adoption phase a scrum coach can help what processes and roles can add value.
Improving Team series #5: Team enabling condition 3: Right People on board? Learn how to select new team members. pos.li/2b7q5p
Last week my assignment ended. Objective was to train and coach teams to use Kanban / Scrum to manage their work ef… twitter.com/i/web/status/1…
Hoe kan je partners en publiek enthousiast te maken en betrekken bij je bibliotheek? Maak kennis met Liberating Str… twitter.com/i/web/status/1…
Vanaf 28 januari ben ik weer beschikbaar voor een nieuwe opdracht. Zoekt u een senior scrum master, team coach of h… twitter.com/i/web/status/1…
Improving Team series #4: Team enabling condition 2: Compelling Purpose? Learn why simply stating “You know what t… twitter.com/i/web/status/1…
- March 2017
- February 2017
- October 2016
- November 2014
- October 2014
- December 2013
- March 2013
- February 2013
- January 2013
- April 2012
- March 2012
- October 2011
- September 2011
- June 2010
- May 2010
- April 2010
- March 2010
- January 2010
- December 2009
- November 2009
- October 2009
- May 2008
- January 2008
- October 2007
- August 2007
- July 2007
- April 2007
- March 2007
- December 2006
- November 2006
- August 2006