enterprise

Enterprise Agile Transformation: The Two Year Wall

Level: Practicing

As Agile is adopted by large enterprises, the number of transformation success stories has grown. But, transformation is an ongoing process, and maintaining organizational change is difficult. So, what happens after the success stories? What can IT leaders expect once the honeymoon is over? In this talk, Chuck Maples, SVP of R&D at Borland, will address these questions head-on, sharing his experiences in Borland’s Agile transformation. He’ll discuss the challenges that can emerge after the initial phases of transformation give way a new stage in the journey.

How to run 4.5 Million tests per day ... and why!

room: Crystal B — time: Wednesday 14:45-15:30
Level: Practicing

Given the size and scope of Google’s code base, and speed of development, typical off-the-shelf continuous integration are unable to meet our needs. So, we decided to create a continuous integration and testing system as a centralized service on an unprecedented scale. When fully completed and operational, it will probably be the world’s largest continuous integration and testing system, running millions of tests every single day.

In this talk, we will report on our experience running such a program in an agile manner and will also describe the basic design and features of the CI system.

Moving to Agile in an FDA Regulated Environment

Level: Practicing

This session will focus on the unique challenges companies face when using agile on projects that involve FDA governance: large company conservative culture, regulatory documentation, requirements tracing, and a bias towards waterfall development.

Skeptics argue that agile is best suited to small- and medium-sized companies and wrongly perceive agile as a limited, negating its use in the highly regulated corporate world.

In reality we will show you how we’ve successfully implemented agile in large sized companies operating in a highly regulated world.

Accidental Adoption - The Story of Scrum at Amazon.com

room: Regency C — time: Monday 14:00-14:45
Level: Practicing

This report describes how scrum was adopted by more than half of the software developers at Amazon.com (and counting). The adoption was due largely to the efforts, both accidental and purposeful, of an internal employee. Amazon’s corporate and development cultures played important roles, both positive and negative. With no executive sponsorship, adoption occurred primarily a team at a time. The wide range of success across teams and organizations leads to a number of important lessons learned with regard to enterprise scrum adoption. The lesson: you can cause this to happen.

Syndicate content