Reduce Release Cycle Time: Nine Months to a Week - Nice!
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. Join Mathew to see if what works for Her Majesty's Government might just work for you and your company.
Recommended Web Seminars
|Jan 05||Completing the Promise of CI/CD with Continuous Merge|
|On Demand||Building Confidence in Your Automation|
|On Demand||Leveraging Open Source Tools for DevSecOps|
|On Demand||Five Reasons Why Agile Isn't Working|
|On Demand||Building a Stellar Team|