An Organization change is sustainable when its evolutionary instead of revolutionary. Organizational change using Scrum is disruptive and may yield results quicker. However it may encounter lots of resistance and may cause few heartburns as well. Kanban on the other hand is not disruptive and evolutionary. However, it needs to disciple to sustain continuous improvement. Organizations incur same amount of pain with bot the approaches but at different rates and times.

This talk is about making best use of both aproaches to bring in revolutionary changes at a sustainable pace with a story.

 
1 favorite thumb_down thumb_up 1 comment visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

- How to apply Theory of Contstraints to identify and address Organizational change?

- Lean Thinking.

- Kanban Thinking.

- Timeboxing Organizational Changes.

- Discuss a case study where Scrumban is best approach for Organizational change than Scrum or Kanban in isolation.

 

Learning Outcome

  • Learn when to apply Scrumban.
  • Learn how to apply Scrumban to bring about evolutionary change to Organizations.

 

Target Audience

Change agents, coaches, Managers

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Anish Cheriyan
    By Anish Cheriyan  ~  2 years ago
    reply Reply

    Hi Apeksha,

    Thanks for the topic submission. Please request to  add more details of the case study of Scrumban which you are planning to share.

    Please add the draft slides.
    Also request you to add any presentations which you have done in past along with the video.


    Thanks
    Anish


    • Liked Naveen Kumar Singh
      keyboard_arrow_down

      Naveen Kumar Singh - Large-Scale Scrum (LeSS) - Journey from component team to customer-centric feature team

      90 mins
      Case Study
      Executive

      Will share LeSS (Large-Scale Scrum) implementation journey and challenges encountered during transformation from component team to customer-centric feature team. Journey that covers defining product, building feature team through changing organization design and descaling organization through lean thinking. Talks will cover challenges in adoption and difficulties in retaining agile values beyond single team. Will also talk about key engineering practices that helped in resolving integration challenges and roles of management after adoption.