We didn't stop the train? Early thoughts on lean flow in a SAFe Enterprise.

During a recent leadership team meeting one of the leaders asked, "aren't we supposed to value people over process?" "We are spending to much time 'in process!' " We started to inspect and adapt our time together and reduced meeting time by 80%. We then went a step further and asked what other processes are not effective any more? Come listen to my lightning talk to see the strawman of what happened when we decided that time boxes were actually getting in our way and we wanted a different way to work. You'll see my sketches of what Lean Flow might look like in an SAFe enterprise. I will also share some of our early learnings.


Outline/Structure of the Lightning Talk

  1. The before!
  2. The guidelines we set for change
  3. The idea!
  4. Early feedback

Learning Outcome

To gain insight into one possible way a team of teams can be agile using Lean Flow principles.

Target Audience


schedule Submitted 2 years ago

  • Trent Hone
    Trent Hone
    schedule 2 years ago
    Sold Out!
    45 Mins

    Agile at the team level fosters self-organization by leveraging constraints. Timeboxes, Work in Progress (WIP) Limits, and clear operational definitions are excellent examples of the kinds of constraints teams regularly employ to deliver reliably. Are you familiar and comfortable with these ideas, but uncertain how to apply them at larger scales? Are you looking for techniques that will allow you to harness the creativity of your teams to enable self-organization at scale? If so, this session is for you.

    I’m passionate about applying concepts from Complex Systems Theory (as developed by Dave Snowden, Alicia Juarrero, Bob Artigiani, etc.) to the work of software teams. My colleagues and I at Excella have been exploiting these ideas by using a variety of patterns borrowed from different theories and frameworks to allow our teams to grow like healthy plants in a garden. From Large-Scale Scrum (LeSS) we leverage the concepts of a single product backlog and a shared cadence. Kanban principles of visualizing the work and limiting WIP help align the teams and foster greater collaboration. Dave Snowden’s emphasis on Homo Narrans—the human as storyteller—has provided a framework for clarifying and promulgating common values, which are essential for decentralized decision-making. Collectively, these mental models created an environment that helped us scale one of our engagements from three teams to eight over the course of a single year.

  • Matthew Kleiman

    Matthew Kleiman - Pair Programming: Better Than Adderall

    45 Mins

    Not all programmers are comfortable with coding alone for 10 hours a day. Matt Kleiman spent years programming inefficiently in a cubicle. His Attention Deficit Disorder (ADD) and other learning disabilities deterred his success on traditional development teams. Seeking out an environment that would nourish his strengths, he found Pivotal Labs. Pivotal's Extreme Programming practices empowered Matt. Attend his talk to learn how pair programming and test-driven development transforms ADD into an asset in the workplace.