5 Target Conditions towards Agile Adoption

In the book "Toyota Kata" by Mike Rother, highlighted the importance of a "target condition" towards Kaizen. Inspired by this, we had been working with multiple organizations of various sizes and plethora of domains in adopting Scrum and Agile Software Development guided by 5 Target Conditions. This talk will be about what these target conditions are, how we help organizations with these, and what results we had experienced.

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

Outline/structure of the Session

First part of the talk will be about our experience in helping organizations become more agile. What are the common issues, the common blockers, etc. This should roughly take around 10-15mins.

Then we talk about 5 core concepts we use in order to help these organizations. There will be side-by-side discussion of the concept, and how they get manifested according to experience. These concepts are as follows: "team" teams, self-management, cross-functionality, iterations, and lowering cost of change. This should take around 20-30mins.

We then move to the "Target Condition" concept. Talk about it in detail.

The subsequent target conditions then are:
1. Teams as smallest atomic unit of resource management
2. Teams that are adept at self-management
3. Cross-functional teams with enough skills and knowledge to deliver work with minimal external dependencies
4. Development done in iterative cycles
5. Continuously lowering cost of change through process improvements

This may take roughly around 10-15mins.

Finally, we tie it all together showing how we use the 5 core concepts as target conditions for the organizations. This may take around 15-25mins.

Learning Outcome

  • For attendees to use target conditions as a way towards continuous improvement
  • Understand core concepts that help organizations achieve further agility

Target Audience

management, coaches, leaders

schedule Submitted 1 year ago

Comments Subscribe to Comments

comment Comment on this Proposal

  • Liked Joseph Yao
    keyboard_arrow_down

    Joseph Yao - No Return Value Driven Development

    45 Mins
    Talk
    Beginner

    As a programmer, you most likely have written some functions which return a value, right? Do you know how to write code without any return value? Do you know what kind of design problem will come with the code which returns some value?

    This topic will show you the value of no return value code via some real code sample. It will show you the benefit about such no return value design as well as something deep in the object oriented design.

    If you're a programmer who wants to write better code, this is topic for you. Your development mindset might be stroke in this talk, please keep calm. :)

  • Liked Eric Byron
    keyboard_arrow_down

    Eric Byron - Game Outcomes Project

    45 Mins
    Talk
    Intermediate

    In November 2014 an independent team of academic and industry leaders conducted a survey targeting the video games industry in an effort to understand the factors that distinguish successful teams from those that are less successful.  The results of the survey were dramatic and resulted in a series of 5 articles published on Gamasutra and numerous workshops and discussions within the games industry.  The results are presented here showing the statistical correlations that clearly identify things great teams do.  In March of this year, 2016, Paul Tozour, who lead the team in 2014, will be presenting a version of this presentation at the Game Developers Conference (GDC) in San Francisco.  

  • Liked Lau Chun Yin Vincent
    keyboard_arrow_down

    Lau Chun Yin Vincent - How our Engineering team work as a Learning Organization

    Lau Chun Yin Vincent
    Lau Chun Yin Vincent
    Software Architect
    OneSky
    schedule 1 year ago
    Sold Out!
    45 Mins
    Talk
    Beginner

    About how our startup Engineering team (~13ppl) learn, talk about the challenge, our philosophy and tactics. Inspired by different agile practice e.g. in spotify, enable interactions with processes. 


    It will be largely based on the blog post
    https://medium.com/translate-engineer-error/how-our-engineering-team-work-as-a-learning-organization-92aae2fbd26f#.jp183ulf9


    30mins should it be, when more time available it will be Q&A. 
     
    We believe

     

    • Passion is key
    • It’s about Process
    • Build expertise Inside the team
    • Maximize the diffusion rate
    • Be Measurable
    • Know the unknown unknowns

    We learn by

    1. Weekly Engineering Session
    2. OKR (Objective and Key Results) framework
    3. Expertise-based Chapter
    4. Hacking Github as a knowledge base
    5. Process for continuous and timely feedback
    6. Share often, at right channels.
    7. Stay connected with the world
    8. Nudge for good

     

  • Liked Stephanie Tong
    keyboard_arrow_down

    Stephanie Tong - The Marriage between Design Thinking and Agile

    45 Mins
    Case Study
    Beginner

    Design Thinking is a human-centred way of solving the right problems that balances commercial and technical realities. Whereas, Agile is about requirements and solutions evolving through collaboration between self-organizing, cross-functional teams.

    Both have HUMAN at the core of it and it creates immense synergy to solve the right problems.

    I will go through a case study where my team has helped an international logistics company to solve its sales problems using Design Thinking and Agile.

  • Liked Nicolas Lassus
    keyboard_arrow_down

    Nicolas Lassus - UX and Agile - friends or foes?

    45 Mins
    Talk
    Beginner

    The User Experience practice has many similarities to the Agile philosophy, yet the two come from different origins and are often implemented in parallel in different parts of the organisation. User Experience practitioners also often fall back to a waterfall-like methodology and fail to involve other non-design parties in the process.

    This talk aims at sharing the experience of implementing Agile to run the design and animation teams at GoAnimate, and how better user experience can be delivered by breaking down the walls between job roles: designers, developers, marketers, customer service representatives, all working together to deliver an outstanding product.

  • Teng Daniel
    Teng Daniel
    Awakener
    Odd-e
    schedule 1 year ago
    Sold Out!
    60 Mins
    Talk
    Advanced

    We are going to share a case study of how we kick start a LeSS (Large Scaled Scrum) agile transition in FDA (Food & Drugs Administration) regulated organization. The product is a surgery X-Ray machine and the team include software engineer, mechanical engineer, electronical engineer. After one year journey, the product get shipped within one year comparing to 2.5 years of previous version. No bug was found after shipping the product so far and the build time reduced from 20+ hrs to 2.8 secs. What made these happen? One of the biggest challenges is how to enable cross-functional and self-managing team and to make it more challenging, everyone had to choose their role and teams. In this talk, I am going to share with you how we official launched the change and how we as agile coaches support in their agile journey. 

     

     

     

  • Liked Yun Ki Lee
    keyboard_arrow_down

    Yun Ki Lee - Avoiding Test Hell (with examples from FitNesse)

    Yun Ki Lee
    Yun Ki Lee
    Senior Development Specialist
    HSBC
    schedule 1 year ago
    Sold Out!
    45 Mins
    Experience Report
    Beginner

    We are entering a world where everything must be done quicker. You must deliver code faster. You must deploy faster. How can you deliver and deploy faster without compromising your professionalism? How can you be sure you are delivering what your client has asked you?

    In short, testing is the only way to be sure you're delivering what someone asked you to. Often we use BDD Tools such as FitNesse which gained popularity over the recent years

    There are a number of integration / BDD test tools out there that help you deliver a high quality software through tests. Its easy to pick up any tool from just their tutorials and start writing tests. But as I found out the hard way, this can quickly spiral into a state where the tests are giving you and your team hell and are worth less than the value the tests are delivering.

    Using FitNesse and Junit as examples, I will share things that I have learnt working on large enterprise and vendor systems and help you avoid your own path to hell.

  • Liked Teng Daniel
    keyboard_arrow_down

    Teng Daniel - Awakening Change - Influencer's Toolbox to Make an Sticky Impact

    Teng Daniel
    Teng Daniel
    Awakener
    Odd-e
    schedule 1 year ago
    Sold Out!
    60 Mins
    Talk
    Advanced

    If you give kids broccoli and tell them it is good for their health. Most likely, you will still get a no. The reason is quite simple, little kids don't care about being healthy. This broccoli principles applies to agile adoption as well. Simply telling and pushing new ideas and practices don't help very much because It is about changing people's mindset and way of thinking. Push and enforcement will always get resistance. The more push we have, the more resistance we will have as coach or change agent. To make it even worse, each individual, team and organization are so different, the culture is different, the business situation is different, the technology is different. Those are perfect excuses for not to change. One key factor for successful and sustainable adoption is to lit the desire to learn and improve, from individual, to team, to organization level. Rather than being pushed a lot of ideas, team will come for help and guidance, to pull idea from coach then apply in their context. 

     

    It is crucial to understand coachees based on their receptance of ideas. Who are the innovators, who are the early adopters, who are in the early majority and who are in the late majority. Based on the categories, as an agile coach, try to apply various tools to influence the change. 

     

    I presented early version of this talk at Scrum Gathering Paris and Beijing in 2013. 

  • 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 Joyce Ng
    keyboard_arrow_down

    Joyce Ng - Case studies: getting your team to scrum it

    45 Mins
    Case Study
    Beginner

    In this talk I would like to give tips on how to transition your IT organization from doing waterfall development to scrumming successfully. I will also share about my own experiences in the past of introducing scrum into an existing organization. Points include:

    - Why scrum? Motivating factors to change to Agile/scrum

    - How (not) to beat a dead horse (aka your CTO) into joining the scrumwagon

    - Introducing Scrum philosophy into your workplace culture

    - Two case studies of transitioning from waterfall to scrum: encountered difficulties and obstacles and how to overcome

  • Liked Teun Hompe
    keyboard_arrow_down

    Teun Hompe - So you think you can Scrum?

    45 Mins
    Talk
    Intermediate

    In this talk I'd like to share my experiences of introducing Scrum at funda. Hopefully our learnings can help you when introducing the methodology at your workplace.

    In 2012 product development (approx. 45 pax) at funda started doing Scrum. We bought post-its, we bought white-boards, we took more than the "1-per-trainee" agile card games from our agile training courses and we were good to go! Or not. Bugs messing up sprints, UX designers with never ending "design stories", developers that couldn't stop refactoring, "I'd say 3 points, because it's about 3 hours of work" and managers who feel "they're just doing whatever they want to do".

    Introducing Scrum turned out not to be as easy as we hoped. However, we kept going, kept learning and kept getting better at it. I'll share some of our mistakes, learnings and tips for others to take with them while introducing Scrum at their workplace.

  • 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"