There’s some serious gaps in the current Agile scaling frameworks. We know that because we are the start of the scaling journey. But what are the scaling frameworks missing today that we should be looking out for? Steve shares his views on what is missing and how looking at the system performance can help us find the gap, as well as what solutions are already out there to help us close the gap. In this episode we discuss the TameFlow community as well as the concept of Throughput Accounting, from the Theory of Constraints.
About Steve Tendon
Steve Tendon popularised the Theory of constraints in some of the agile community and he is also the Creator of the TameFlow systems thinking approach which nurtures breakthrough performance innovation. This system is described in the book with the same name: Tame the Flow.
How to scale agile software development? is a question we hear often these days. Antti describes his experiences, how long it took him and his colleagues to get it right, and what they learned in the process. Scaling agile software development isn’t easy, and it is important we learn about what has failed in the past.
About Antti Tevanlinna
Antti is an agile practitioner, who got started with agile in my own very first Agile project way back in 2004. He’s been through all kinds of roles, from team member, to management, to customer-facing roles.
You can connect with Antti Tevanlinna on twitter, and check Antti Tevanlinna’s blog.
How do we help organizations to recognize the value that scrum teams can bring, and the obstacles they face in the process? Stephen Thomas shares his recipe and describes a few ideas of how the retrospectives can be an effective practice to help organizations evolve and get better.
Stephen’s recipe for organization improvement:
Help the teams understand their progress with a physical (as opposed to digital) and visual burndown (colorful if possible).
Write the principles on the wall and make sure people see them regularly. Point to them when needed.
Have lots of wall space for teams to use and create their shared view of their work.
Help start and facilitate organization-level retrospectives, because improving one team is not enough for lasting change.
Make the team independent
Before implementing all of this, make sure that the organization has the necessary knowledge to work in an agile manner, helping organize training if needed, and working with stakeholders regularly.
About Stephen Thomas
Stephen has been managing digital projects since 2004. Initially specialising in e-learning, he now looks after multiple projects that range from rapidly produced native apps to large-scale social networks. Based in Oxford, he is also one of the founders of the DOPM meetup.
You can connect with Stephen Thomas in LinkedIn, and follow Stephen Thomas on Twitter.