|Attend the world’s largest conference for Agile teams, developers, managers, and executives. Join colleagues, peers and teams from around the world to explore the depth and breadth of Agile software development across all practices, and perspectives.|
|August 13-17, 2012|
Gaylord Texan Hotel & Convention Center
|Date||Time||Net Objectives Presentation||Room||Speaker|
|Tue Aug 14|| 1:30pm - 3:00pm
||Scaling Agile with Multiple Teams: Using Lean to Drive Business Value
||Austin 1-3||Alan Shalloway|
|Thu Aug 16|| 9:00am - 10:30am
||De-Mystifying Kanban: Understanding Its Many Faces
||Texas 3||Alan Shalloway|
This program will share Lean-Agile principles that guide both what to build and how to coordinate the teams that need to build it. We will cover how to apply these principles when there are several teams involved in creating software using either Scrum or Kanban development approaches. A common intent of all Agile methods is threefold: 1. Build the most valuable features 2. Build them efficiently 3. Minimize creating extra work The challenge to accomplishing this is not that great for one team working independently. However, when several teams have to coordinate, the challenges greatly magnify. When implementing software over several teams, we have found it to be valuable to manage the workflow from the perspective of what will provide value to the business – not quite the same thing as customer value. This can be used to guide how to slice work up into smaller chunks, enabling at least quick feedback, if not quick delivery, to ensure the right products are being built. A lot of thrashing can take place when teams work with poor coordination – greatly lowering efficiency. In large scale development, it is clear that working on the right functions, and coordinating their construction across teams is essential. Having teams coordinate amongst themselves has been the popular method. Unfortunately, this approach, typified by Scrum-of-Scrums, has a dismal track record. Having discovered the correct principles underneath large scale development, we now believe we understand why coordinating teams as a set of peer development organizations, can rarely be an optimal approach. Teams need to be guided by the value they are building, while self-organizing to improve the embedded feedback loops of development. The self-organization techniques required vary, depending upon several factors. These principles, not surprisingly, are directly related to the 3 intents mentioned above. This seminar will present both the principles underneath large scale feature implementation, as well as a few case studies demonstrating different implementations of these principles.
There is a lot of confusion about what Kanban is. Some of this is due to the fact that many people who have never used Kanban have been deriding it – saying it is a mechanistic team management method that doesn’t respect people. The fact that Kanban is quickly growing and gaining a reputation for success where other Agile methods have had challenges belies that categorization. But what is Kanban? Even when listening to Kanban thought leaders one will hear different answers. 1) it’s a power agile management system based on lean-flow. 2) it’s a transition management method to assist teams to achieve continuous learning. 3) It’s a way to create visibility for executives to improve their product portfolio management. I can almost here Gilda Radner and Dan Aykroyd on Saturday Night Live describing New Shimmer! This talk discusses how Kanban actually is a multi-faceted method that assists process, transition and collaboration. Kanban is not a mere tool, or even a set of practices. It’s a mindset that attends to people, their culture, and the systems they find themselves working in. The talk presents a few of the basics of Lean-Flow and theory of constraints that it is based on as well as some of the psychological aspects of people adopting new methods. While this talk is intended for those considering adopting Kanban, those currently using Scrum will find it helpful as many of the principles and practices of Kanban fit well into the Scrum framework.