1. What is Scrum and Kanban?
  2. Comparing between Scrum and Kanban
  3. How to get the best of both worlds? Scrumban
  4. What are the best practices in Scrumban?
  5. Q&A

 

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

Outline/structure of the Session

Just 2 sessions as below:

30 mins of presentation

15 mins of Q&A

Learning Outcome

Gaining insights/best practices about adopting Scrum & Kanban and some best practices of using Scrumban.

Target Audience

People have experience in practising Agile in real life

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal
  • Steven Mak
    By Steven Mak  ~  1 year ago
    reply Reply

    Is this a theoretical talk on Scrumban? Do you have any real personal experience with "Scrumban"?

    What makes you think Scrum doesn't allow Kanban practices and Kanban doesn't allow Scrum practices?


  • Liked Michael Chik
    keyboard_arrow_down

    Michael Chik - Test

    45 Mins
    Talk
    Beginner

    Test

  • Liked Jas Chong
    keyboard_arrow_down

    Jas Chong / Guillaume Duquesnay - PRODUCT OWNER & DEVELOPMENT TEAM – A TANGO IN COMMUNICATION

    60 Mins
    Talk
    Beginner

    With over 5 years in the practice of tango, I would like to use tango techniques to explain the nuances in communication between product team and dev team. It’s not often straight forward or easy.

    Tango is an extreme dance in coordination and non verbal communication. it is also not the kind of dance that can be guided by strict rhythm like salsa. Instead, it’s a decision between both dancers on how fast or how slow they want to take it. It is also one of the few dances where pauses are encouraged and takes the form of regrouping.

    I’ll be using experiential learning to demonstrate techniques in communication. (Note: it’s not a tango lesson but a communication workshop using tango.)

  • Liked Marcio Sete
    keyboard_arrow_down

    Marcio Sete - From zero to happiness - A practical Kanban experience in an Ops Team

    Marcio Sete
    Marcio Sete
    Agile Coach
    Elabor8
    schedule 1 year ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    This talk is about a story of an OpsTeam, working in a multi-million Cloud project, looking for a Project Manager to support them. What did they get? An Agile Coach instead!

    I'll share how this experience has been, the bootstrapping, what worked well, what didn't, the peculiar challenges of an OpsTeam and how we are increasing our happiness index every day using the follow strategy:   

    #1 – Visualize the work

    #2 – Reduce batch sizes to improve flow

    #3 – Collaborate to win

    #4 – Make sure we are doing the right thing and just the right thing

    #5 – Collect tangible results

    #6 – Run different feedback loops 

    #7 – Celebrate quick wins

  • Liked Joseph Yao
    keyboard_arrow_down

    Joseph Yao - Mutation Test - A New Way to Improve Code and Test - More Information

    45 Mins
    Talk
    Beginner

    Mutation test is a way to put a "mutation" into your code, run the test and then see if the test fails or not. A mutation is a change to production code which should make it behave in a different way. The idea is, if the production code is just enough to pass the test, any mutation should make the test failed due to the behaviour change. If test failure doesn't happen, we will say that the test can't kill this mutation. Therefore, some test code smell or production code smell exists, which possibly leads to some learning and improvement of our code and test.

    By TDD, we should get "just enough" code that passing all the test. But, how do we know this? Sometimes, since writing test and code is so interactive in TDD, we may not choose the smallest baby step to pass the test. This means we may write some code which is not driven by current test (code smell). On the other side, we may even miss some important test or create some “weak” test by TDD because the code is too “obvious" to us (test smell). By applying Mutation test mindset and methodology, we can identify such code smell and test smell and then help us improve the quality of our code and test.

    In this topic, I will first introduce what mutation test is and why we can use it to create some learning of and improve our code and test. Then, I will share a real code example in which I tried the mutation test and some learning I got. Finally, based on what I learned so far, I will have a summarisation about the code smell and test smell which can be detected by mutation test.

  • Liked Danielle Jabin
    keyboard_arrow_down

    Danielle Jabin - Measuring Team Performance At Spotify: From Gut Feel To Hard Data

    Danielle Jabin
    Danielle Jabin
    Agile Coach
    Spotify
    schedule 1 year ago
    Sold Out!
    45 Mins
    Talk
    Intermediate

    How do we actually know if our teams are doing well? Is gut instinct enough? Furthermore, in a rapidly growing organization such as Spotify, how can we ensure some sort of consistency in our baseline level of Agile knowledge across the technology, product, and design organization? 

    In this talk, I’ll discuss techniques we have developed and use at Spotify to benchmark health and performance for our teams and some tactics we use to bring them closer to—and beyond!—being the best teams they can be. I’ll explain frameworks that can be used to give us tangible evidence about how we’re doing as teams, as Agile Coaches, and as managers of people and product. Furthermore, I’ll tell you about the organization-level methods we use at Spotify to share knowledge and maintain alignment of our agile practices as we scale in order to bring music to people all around the world

  • Liked Timothy Lok
    keyboard_arrow_down

    Timothy Lok - How to create a User Story Map

    60 Mins
    Workshop
    Beginner

    I will run a workshop to let participants to create a user story map based on a Product.

     

    Steps:

    1. Write up stories
    2. Organize stories in a narrative flow
    3. Explore alternatives
    4. Divide stories into multiple levels
    5. Group stories that reach sub-goals

     

    Example of a Product: "The Next Generation of Word Processing Software"