ScrumBan - Boosting your Scrum using Kanban/Flow

ScrumBan is a hybrid Lean/Agile approach combining Scrum and Kanban. It combines the team-focused rhythmic nature of the Scrum Framework with the Lean/Flow focus of Kanban to create a winning combination. This workshop provides attendees with sufficient knowledge about Scrum, Kanban and Scrumban to lead or guide a team in their adoption of ScrumBan – from system design through to evolutionary change. They will have an understanding of the principles and thinking behind Scrum and Kanban to help them drive meaningful focused continuous improvement using context-specific strategies/practices.

 
1 favorite thumb_down thumb_up 3 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist
 

Outline/structure of the Session

  • Scrumban - Evolving Scrum using Kanban - presentation
  • In-depth Case Study - presentation 
  • Comparing Kanban and Scrum - exercise mixed with content presentation
  • Experiencing Scrum Iterations and Kanban Flow in the GetScrumBan game - long exercise
  • Q&A - How ScrumBan can help you in your context - open discussion / lean coffee / world cafe exercise
  • Summary/Epiphanies exercise - What are you taking away to your team/group/organization?
  • Retrospective exercise/Closing

overall the workshop aims for a balanced mix of presentation/expert content, discussion, and interactive experiential exercises. 

Learning Outcome

  • Know what is Kanban
  • Know what is ScrumBan
  • Know how ScrumBan looks in practice based on a class exercise as well as stories from real companies
  • Know how the journey towards ScrumBan can look like
  • Understand the effect ScrumBan will have on the Scrum ceremonies, roles, artifacts
  • Have a set of suggestions you can apply in your Scrum team tomorrow morning

 

Target Audience

Scrum Masters, Agile Coaches/Consultants, Scrum Practitioners, Senior Development/Test Managers, Senior Release/Program/Project Managers

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Jerry Rajamoney
    By Jerry Rajamoney  ~  2 years ago
    reply Reply

    Hi Yuval,

    Thanks for this topic. I have a Quick clarification. It says 480 minutes which means 6 hours (almost a full day). Is this is correct? Is this means anyone sign up for this needs to be in the session full day. Please clarifiy.

  • Joel Tosi
    By Joel Tosi  ~  2 years ago
    reply Reply

    Hi Yuval,

       Same question as in the other workshop submission - please elaborate on the exercises for the workshop - what is needed, how are they ran, do they build on each other, what is the duration, etc

    Best,

    Joel

    • Yuval Yeret
      By Yuval Yeret  ~  2 years ago
      reply Reply

      Same answer :-) added explicit exercises to the outline

      i would say the exercises are around 1/2 of the time


  • Liked vinaya muralidharan
    keyboard_arrow_down

    The Snowball Effect - From Team Kanban to Enterprise Kanban

    vinaya muralidharan
    vinaya muralidharan
    Sutap
    Sutap
    schedule 2 years ago
    Sold Out!
    20 mins
    Experience Report
    Intermediate

    About two years ago, we embarked on our journey towards Agility and Kanban was our vehicle.

    But Kanban had people worried.

    How can we not have detailed plans?! How can we limit WIP when we have so many things to work on?!

    We have due dates to meet! And so on.

    We would like to share one of the approaches that we adopted to help move the change along.

    In addition to focusing on the Kanban implementation at the project levels, we adopted another route – to work through the individuals and the teams – a grounds up approach. We encouraged people and teams to use Kanban boards to manage their daily tasks.

    You have difficulty in managing personal stuff? We’ll help you manage better!

    You have issues in managing team level priority? Look what we did within our team- we have a Team Kanban and we are now much better organized!

    One by one we saw people getting interested. The movement gathered steam - we worked directly with a handful of people and they in turn got their peers onboard. And we saw various flavors like Personal Kanban, Team Kanban cropping up all over the place – even in our Travel Office and Corporate Office. What this did was give people a safe, controlled environment to experiment and learn in.

    As they got used to the ideas of limiting WIP, pulling work, visualizing work and “stop starting, start finishing”, it gave them the confidence to work this way at the project level too. And it made our lives as change agents just a wee-bit easier!

    We welcome you to come hear our story about nurturing the change towards Agility by making it a grass roots movement.

    A brief introduction to Amdocs - Amdocs is a leading provider of Customer Experience systems and services in the telecommunications domain, typically doing large scale transformation projects.

  • Liked Hrishikesh Karekar
    keyboard_arrow_down

    An Empirical Approach to Agile Transformations

    Hrishikesh Karekar
    Hrishikesh Karekar
    schedule 2 years ago
    Sold Out!
    20 mins
    Talk
    Beginner

    Enterprises big and small are aspiring for agility these days and kick-starting Agile transformations. Agile is mainstream. The movement that started with a manifesto and principles has grown bigger. From product development and startups, agile is now being adopted in mainstream (read legacy) companies for all kinds of knowledge work beyond the scope of pure product development – in services, support, marketing, HR and so on.

    With the widespread application, many ways to achieve agility have also sprung up. We have ScrumKanbanScrumbanSAFe and probably few more variations. Each have their benefits and challenges depending on the organizational context that they are being used into.

    For organizations that are just starting, this plethora of information is quite confusing and intimidating sometimes too. Transformations also involve a lot of investment - both financially and otherwise. Its a big change. Deciding on an approach at the outset is not trivial. 

    The talk would suggest an approach to Agile transformations that is based on the fundamental premise of Agile - the empirical philosophy of transparency, inspection and adaptation and provide practical tips and tricks based on my experience with large scale transformations.