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)
- ICAgile Certified Agile Team Facilitator with Ben Maynard & Jon Spruce (Online Workshop on 12th - 15th September 2022)
- Agile at Scale (In-Person) with Joakim Sundén (in London on 19th - 20th September 2022)
- YOW! Perth Developer Conference 2022: Online (Online Conference on 19th - 20th September 2022)
- YOW! Perth Developer Conference 2022: In-Person (in Perth on 19th - 20th September 2022)
- The Role of the LeSS Practitioner (SkillsCast recorded in April 2022)
- Panel: What to Expect When you Might (or not) be Expecting (SkillsCast recorded in March 2022)
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