The Impact of the Pace Delivery
A SkillsCast for this session is not available.
In agile development, the length of an iteration tends to be somewhere between two and four weeks. But this doesn’t mean that software is delivered to customers every iteration – quite the contrary – software release cycles vary all over the map. Deliveries of new versions of software are often months or even years apart. And it turns out that this matters; organizations with release cycles of six months or longer are quite different from organizations with daily or weekly releases. Their processes are different, their governance approaches are different, even their business models are different. This talk will examine the way in which the pace of software delivery influences – and is influenced by – the development process, the business model, and the governance system.
YOU MAY ALSO LIKE:
- A Tale of Two Terminals (SkillsCast recorded in May 2011)
- Certified Agile Team Coaching with Ben Maynard & Jon Spruce (Online Workshop on 7th - 11th March 2022)
- Certified Large-Scale Scrum Practitioner: Principles to Practices (In Person) with Ben Maynard (in on 15th - 17th March 2022)
- YOW! London: In-Person (in London on 10th - 11th May 2022)
- YOW! London: Online (Online Conference on 10th - 11th May 2022)
- Roman Pichler: Agile Product Roadmaps (Online Meetup on 27th January 2022)
- Merging Kanplexity™ with LeSS (SkillsCast recorded in November 2021)
- Retrospecitves Antipatterns (SkillsCast recorded in October 2021)
The Impact of the Pace Delivery
Mary Poppendieck
Mary considered retirement 1998, but instead found herself managing a government software project where she first encountered the word “waterfall.” When Mary compared her experience in successful software and product development to the prevailing opi