How to Turn Agile Delivery into Continuous Development
Agile development is near-mainstream: 88 percent of enterprises say they are committing resources to devops and agile principles. Yet developer bootstrapping, distributed workspace security, and team workspace configuration are still cited as the biggest drags on productivity. And once development commences, stakeholders cannot provide feedback until after a merge where test environments are made available. These issues inhibit collaboration and speed, leading to longer feature iterations that break the agile ethos.
This session introduces the concepts around Continuous Development, a set of practical strategies, practices and recommended solutions for extending the agile ethos throughout ideation, development, and delivery. With continuous development your teams can iterate in the moment with developers before code has been merged. When attached to a culture supportive of continuous improvement and tools that enable in-context changes, continuous development will let you increase release frequency by 100% and eliminate time spent with configuration by 30%.
Outline/structure of the Session
Introduction: the state of agile development
Problem: the biggest drags on developer productivity
Solution: introducing the idea of "continuous development," an extension of continuous delivery
Examples: talking through how Codenvy uses continuous development and metrics of how it's improved our development process
Future: discuss the potential impact and ways continuous development could be further extended or applied
Explain how to make your development truly agile, increase release frequency and decrease time spent configuring.
Discuss the different ways continuous development, integration and delivery can be applied and how to use them most efficiently.
Look at the current state of agile development, its impact and where it might be heading in the future.
Developers and product managers