Abstract/Description

You're leading a team as it becomes agile. You've got the planning process under control. You're realizing the benefits of improved transparency and your teams are communicating better with the customer. But you know that many of the key advantages - faster release cadence, improved quality, reduced cost of change - come from changing the core development activity.

Some of these changes, such as basic TDD, are obvious. But even they can be difficult to measure. Beyond the basics, the technical practices become difficult even to describe. Your teams give you transparency into what they do. How can you get similar transparency into how they do it? What should you realistically expect a team to do, and how can you tell whether it is doing that?

This talk targets managers and executives for agile teams. We discuss helping people see what is possible, creating feedback systems so that everyone knows where they are at, and ways to choose practices that align with your business needs.

Additional Resources

About the Speaker(s)

No bio currently available.

James Shore teaches, writes, and consults on Agile development processes. He is a recipient of the Agile Alliance's Gordon Pask Award for Contributions to Agile Practice, co-creator of the Agile Fluency™ Model, co-author of /The Art of Agile Development/, and host of “Let's Code: Test-Driven JavaScript.” InfoQ has named him as one of the “most influential people in Agile.” You can find his screencasts at letscodejavascript.com, essays at jamesshore.com, and more about the Agile Fluency Project at agilefluency.org.