Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Effective Knowledge transition using agile

136 views

Published on

Effective Knowledge transition using agile

Published in: Technology
  • Be the first to comment

  • Be the first to like this

Effective Knowledge transition using agile

  1. 1. Effective Knowledge Transition using Agile Gayatri Kalyanaraman PM Power Consulting
  2. 2. Framework for Knowledge transition  Expectation setting with all stakeholders  Showcase after every sprint  Create a model of trust  Have intermediate retrospectives  Agreement with all the team members on the roles and responsibilities when a new member comes in
  3. 3. Different levels of transition (Large) Team Transition Travel plan with sprint Goals for every sprint Demo & retro with transparent feedback Knowledge Transition, Assisted, Primary - 3 phases Team Expansion Joint planning Objectives for the transition Demo Knowledge Transition, Assisted - 2 phased transition Role Transition Expectation setting Sprint long with one stage Demo & Retro - Transition plans need to be customized - Multiple stages based on the complexity
  4. 4. Role Transition Scenarios  Rotating scrum master model or Quality Analyst role for a Developer or Automation expert playing the analyst role Ways to make it effective  Team capacity ( & thus Velocity) is appropriately taken into account  Plan created, understood and agreed by team  Roles & responsibilities that are changing so that everyone signs up  Feedback given to new member(s) individually  Discussed openly in retrospective to make it better  Self organizing teams will find ways to settle into a rhythm!
  5. 5. Team Expansion Scenarios  Existing team and New team co-located  New teams created for product development, large program Ways to make it effective (apart from role transition aspects)  Two phase transition with knowledge transition followed by a assisted phase one or two stories to be done  Stories written to carve out the scope and created, agreed by the two teams  Demo Focus on learning and width of knowledge rather actual story completion. Doneness criteria should be modified during this phase  Modules to be sliced small so that it includes KT, assisted phase across requirements, dev and implementation  Adaptive planning in the end of the sprint to be created with inputs from the feedback  Retrospective within team as well as inputs from the team providing transition
  6. 6. (Large) Team Expansion Scenarios  Vendor Consolidation (moving from one vendor to the other)  Geography movement for development, maintenance Ways to make it effective (apart from Team expansion aspects)  Knowledge phase with modules planned  Assisted phase where teams take up actual stories to develop with inputs  Primary phase where new team(s) take responsibility of delivery with active feedback  Travel planned for each sprint according to the module/phase  Adaptive planning in the end of the sprint to be created with inputs from the feedback  Retrospective within team as well as inputs from the team providing transition  Optionally having a role as a transition manager similar to a product owner to manage access, escalation, metrics, culture and motivational aspects
  7. 7. Measurement Parameters  (Large) Team Transition o Learnings captured, Demonstration Feedback, Adaptive plan for next sprint(s), and Retrospective (using direct feedback from traveling transition team members)  Team Expansion o Demonstration Feedback, Adaptive plan for next sprint, Retrospective  Role based transition o Demonstration Feedback & Retrospective inputs

×