This workshop will help participants to understand how the Kanban method really works.

We will learn how to use the Kanban method to visualize your current process ("start where you are"). Will figure out how to limit work in progress (WiP); define and make process policies explicit; measure and manage flow.

Also we will figure out what does it mean to search for opportunities for continuous improvement. We will learn how to increase your team speed and at the same time decrease pressure at work.

All of these we will touch through extremely hands-on step-by-step simulation using LEGO bricks.

 

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

Outline/structure of the Session

  • Intro
  • Kanban in a nutshell
  • Kanban Simulation with LEGO
    • start where you are
    • understand your process
    • work with WiP limits
    • define your real process
    • measure and manage flow
    • improve efficiency 
  • Short Retro
  • Outro

Learning Outcome

You will get practical hands-on step-by-step experience how to:

  • visualise your current process with the help of the Kanban Board
  • define process rules and WiP limits
  • deal with bottlenecks and your process efficiency
  • change your process in an evolutionary way
  • see the whole picture

Target Audience

This workshop is designed for professionals who are responsible for process optimisation, business performance and project management: managers, IT directors, heads of departments, middle managers, team leaders, project managers, technical managers, engin

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Ankur Sambhar
    keyboard_arrow_down

    Promiscuous Pairing - More the merrier !!!

    Ankur Sambhar
    Ankur Sambhar
    schedule 2 years ago
    Sold Out!
    45 mins
    Case Study
    Intermediate

    Being Agile developer, have tried & tested various flavors of pair programming over the years while working in highly motivated self-managed team. Some experiments worked while some worked better :)

    This talk is about sharing the personal experience of practicing promiscuous pairing which allowed the team to be always in the beginner's mind state and being able to push the boundaries consistently.

    This experience sharing talk is based on our successful adoption of the promiscuous pairing technique based on very famous research paper by Arlo Belshee "Promiscuous Pairing and Beginner’s Mind: Embrace Inexperience".

  • Sachin Natu
    Sachin Natu
    Naresh Jain
    Naresh Jain
    schedule 2 years ago
    Sold Out!
    60 mins
    Case Study
    Intermediate

    Adopting agile development practices and continuous delivery is becoming a norm in the software industry. Time to market and frequent releases have drastically reduced time available for regression testing. Inspection is considered wasteful. Faster feedback cycles during development is crucial. These have created lot of challenges for testing community, which traditionally relies on manual testing assisted by UI based test automation.

    This is an experience report of transforming testing practices across organization, which decided to embrace Agile. Today our testers are not trying to find defects, instead they collaborate with product management and developers to prevent them in the first place. In fact, during the appraisal process, the defects found by them is ignored, instead we focus on how much time they are able to dedicate to collaboration and exploratory testing. The boundaries between developers and testers have faded away and today quality is whole team's responsibility.

    We started with less than 20% of our testers with automation skills (mostly UI automation) and rest of them relying on manual testing. However, today, all our testers practice BDD. They have picked up Java & Groovy programming skills. They are able to contribute Workflow tests, Integration tests and Business Logic Acceptance Tests. Early collaboration and pairing is the norm. By the time developers are done with their tasks, all checks are already automated and hence we are able to deploy software every fortnight to production.

    Are your testers finding it hard to make this transition to an Agile mindset? This session will give you some concrete ideas based on our transition at IDeaS.  

  • Liked Yuval Yeret
    keyboard_arrow_down

    Understanding and Implementing DevOps Flow

    Yuval Yeret
    Yuval Yeret
    schedule 2 years ago
    Sold Out!
    480 mins
    Workshop
    Intermediate

    DevOps seeks to extend the agile benefits of Flow, Collaboration, Inspect and Adapt thinking all the way to Production. While DevOps and Continuous Delivery were born in the world of web operations in companies like Etsy, Google, Amazon, Facebook and Flickr (also called Unicorns in the DevOps community) it is now clear that Enterprise IT/Product Development companies (also known as Horses) can  also benefit immensely from the ideas and practices and achieve similar results if they manage the change/journey towards DevOps in a way that makes sense in their context. In this workshop we will introduce the concepts of DevOps and Continuous Delivery and help attendees figure out how DevOps can fit into their world as well as how a “DevOps Implementation” might look like.

  • Naresh Jain
    Naresh Jain
    schedule 2 years ago
    Sold Out!
    90 mins
    Tutorial
    Intermediate

    In order to achieve my goals, as a buyer of your product, I want awesome feature.

    AT: make sure your users stories don't get in the way.

    Users Stories, the tool teams use to break big ideas into small demonstrable deliverable, are easy to describe and challenging to write effectively. In this hands-on workshop you'll learn how to write great user stories that adhere to the INVEST principle. We'll learn various techniques to slice your stories using the vertical-slicing approach. We will discuss what elements should be included in the stories, what criteria you should keep in mind while slicing stories; why the size of your user story is important and how to make them smaller and efficient.

  • Aslak Hellesøy
    Aslak Hellesøy
    schedule 2 years ago
    Sold Out!
    60 mins
    Keynote
    Intermediate

    As lead developer of Cucumber and author of The Cucumber Book, Aslak gets asked to consult with organisations who want to introduce Behaviour-Driven Development (BDD). Time after time, he meets teams who are trapped doing half-arsed agile. They do the easy, obvious, visible agile practices, and none of the powerful, hard-to-master, hard-to-see ones.

    When these teams ask for help learning BDD, we get a chance to remind them how important conversations and collaboration are in software development. We teach them to write tests before they write code, as a way to explore and discover the hidden details of a requirement just before they dive in and start building it. This talk will make you wince with recognition, laugh with despair, and finally inspire you with stories of teams that have finally, after years of flaccid scrumming, discovered the true collaborative heart of agile software development. You’ll see patterns you recognise from your own teams, and gain insights about how to fix them.

  • Saket Bansal
    Saket Bansal
    schedule 2 years ago
    Sold Out!
    45 mins
    Talk
    Intermediate

    Why organizations are adapting towards agile? Is it to get most out of their resources or is it about doing the right thing?

     

    Traditional mind set of achieving high productivity and using resources efficiently does not change easily, even when organization moves to agile they remain more and more worried about the team velocity. When I meet agile practicing companies or I attend event on agile I find that most of

    the focus is on delivering product backlog efficiently. We see lot of talks on how to make team more self-organizing so that they can do the things faster.  Even after moving to scrum or agile we keep ignoring the warning

    “There is nothing so useless as doing efficiently that which should not be
    done at all.”  —Peter F. Drucker

    When most of the organization starts with agile they takes it as an engineering process, and most of the team focuses too much on velocity, while to get maximum out of agile we need to look at Enterprise Agility, we need to look at an organization’s entire value stream—from idea to implementation, from concept to consumption.

    My talk would be focusing on need of organization agility and will introduce one of the monitoring tool “Life Cycle Profitability “which can help organizations in getting answers of questions like :

    • Should we delay the release by one month to fix the defects ?
    • Should we reduce the cycle time by adding one more team?
    • Should we delay the release to add functionality?
    • Should we delay the project by one month to get more innovative ?

    Life Cycle Profitability is based on principle “Take an economic view” introduced in book:The Principles of Product Development Flow , Donald G. Reinertsen . In my talk I will be showing how we can convert proxy variables like cycle time , velocity , technical debts  into Life Cycle Profit.

    I presented part of this concept in one of the conference and got good response, but I will create fresh presentation for this talk, since this time I will put more focus on expanding the model to calculate the Life Cycle Profit.