release

Conference Presentations

Reduce Release Cycle Time: Nine Months to a Week - Nice!
Slideshow

Picture this scene from three years ago: Employing the corporately mandated processes, a software engineering team is delivering system updates about once every nine months. When their senior user suddenly demands the next delivery in twenty-two weeks-half the current cycle duration-the team realize that they must quickly change development practices. Mathew Bissett describes how Her Majesty's Government did precisely that-and much, much more. First, they reduced delivery cycles from unpredictable dates every nine months to predictable releases every six weeks. Then, they cut releases cycle time to once every week. By identifying and mitigating risks early in the work intake process, enforcing quality gates, executing multiple test levels concurrently-and more-they dramatically increased throughput with the same or better quality. Today, these new processes provide their teams the best balance of structure versus agility.

Mathew Bissett, UK Government
STARWEST 2012 Keynote: State-of-the-Art Cloud Testing: Experiences with Bing Search
Video

The cloud is penetrating every technology organization and almost every software product or service. The cloud affects everything inside development, bringing profound changes to how engineers build, test, release, and maintain software and systems.

Ken Johnston, Microsoft

AgileConnection is one of the growing communities of the TechWell network.

Featuring fresh, insightful stories, TechWell.com is the place to go for what is happening in software development and delivery.  Join the conversation now!