Kanban adoption at Software Engineering Professionals (SEP)
In 2004, SEP tried adopting Agile practices. However, Agile failed to have the desired lasting impact across the entire organization. Things changed in 2007, when SEP implemented Kanban for the first time. We will explore how Kanban teams at SEP matured through the lens of the Dreyfus Model for Skill Acquisition. We will examine what this pattern has meant for institutionalization of Lean in the organization. We will discuss a counterintuitive technique for higher success and adoption rates of new methodologies. Finally, we will review common pitfalls teams encountered adopting Kanban.
This experience report will be presented in a slide presentation lecture format. During the presentation we will examine several projects of varying size and industries that were managed using Kanban. There will be opportunities for questions and discussion topics at defined points during the presentation with a Q/A session following.
- An overview of Software Engineering Professionals (SEP) to provide some context and it’s history using Agile practices.
- An explanation of the Dreyfus Model and how it was applied to kanban systems.
- For each stage in the Dreyfus Model, we will examine what that stage looks like and how it manifested itself across multiple kanban teams at SEP.
- Dreyfus Model Stage 1: Novice
- Dreyfus Model Stage 2: Advanced Beginner
- Dreyfus Model Stage 3 : Competent
- Dreyfus Model Stage 4: Proficient
- Dreyfus Model Stage 5: Expert
- At look at the lessons learned while integrating kanban systems across the organization.
- A brief story about how kanban saved a project at SEP.
- Understand how to best introduce kanban within an organization
- Realize how to evaluate at team’s maturity level through the Dreyfus Model.
- Demonstrate how the introduction and teaching process evolved over time
- Illustrate the impact to SEP’s company culture
- Examine the challenges faced while introducing kanban