SCRUM works well in development and production environments. Many of my posts have attested to my experiences in implementing SCRUM - self-styled way. SCRUM gives a good framework to apply JIT, Kanban and increase throughput in a peak performance production and delivery oriented environment. There is scope for SCRUM implementation in this arena because you get measurable parameters of velocity and a logical completion measure in releasing a shippable product.
Recently, I was thinking of the notion of shippable product at end of sprint. My experiment is to work and check if I can implement SCRUM practices to ship products and then extend to get shippable product. Any change management requires working on lots of undercurrents than explicit stories and features. There cannot be a defined scope for resolving interpersonal conflicts , improvements in trust and getting together as a cohesive learning unit.
While I was considering the scenario, I could realize that SCRUM can be used in same way to
- Implement multiple tracks of initiatives at same time,
- Calibrate velocity of individual initiative tracks as per situation (most important value of Agile which is being responsive)
- Continue few assignments across multiple sprints,
- Assign and design initiatives to be completed in short term sprints, medium term multiple sprints and
- Even conduct a long extended single sprint which is the most important and overarching initiatives that needs investment and constant attention to sustain.
Ideation of the change management actions and areas could be a free-wheeling mind map, capturing random thoughts, focused discussions, personal experiences and understanding under currents, loyalties and preferences. SCRUM provides a good support structure to create
- A backlog of these ideas,
- Prioritize them in Sprints,
- Track their movements and velocity as Kanban,
- Trace and control efforts in burn up and burn down charts,
- Measure success through EVM.
Shall keep posting more as I progress along the journey.