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 Course on 15th - 18th November 2021)
- Certified Large-Scale Scrum Practitioner: Principles to Practices (In Person) with Ben Maynard (in London on 22nd - 24th November 2021)
- YOW! December 2021 (Online Conference on 30th November - 1st December 2021)
- Domain-Driven Design Hands-On Workshop: A DDD-traineeship at "Carries Cars" (Online Meetup on 26th October 2021)
- Merging Kanplexity™ with LeSS (Online Meetup on 2nd November 2021)
- Retrospecitves Antipatterns (SkillsCast recorded in October 2021)
- The Myth of Team Autonomy: Why it is an Illusion and We Still Need It (SkillsCast recorded in October 2021)
The Impact of the Pace Delivery
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