Over a million developers have joined DZone.

A Simple Framework for Complex Product Delivery

DZone's Guide to

A Simple Framework for Complex Product Delivery

Gunther Verheyen explains his four main points pertaining to Scrum, and why it makes such an effective tool for developing complex products.

· Agile Zone ·
Free Resource

Download this white paper to learn about the ways to make a Scrum Team great, brought to you in partnership with Scrum.org


On the 3rd anniversary, and the 5th reprint, of my book “Scrum - A Pocket Guide,” I created a short introduction to Scrum, which was recorded by my publisher Van Haren Publishing.

Here are the highlights of the video, explaining why I think Scrum is a great, yet simple framework for complex product delivery.

1. Scrum has been around for a while. It was officially introduced to the general public in 1995. Since then, as more and more people, teams, and organizations started using Scrum, Scrum became the most adopted method for Agile product delivery. At the same time, Scrum grew lighter and lighter, thereby, in a way becoming less and less complete and ‘perfect.’ Prescribed practices and techniques were gradually removed from the official definition of Scrum, The Scrum Guide. Scrum turned into the framework it was always designed to be, a framework upon which people devise their own solutions, create their own working process. A Product Owner brings product ideas to a Development Team. No later than by the end of a Sprint the team turns these ideas into releasable versions of the product. Sprints take no more than 4 weeks and are often shorter. The Scrum Master creates and fosters an environment for such self-organized and creative collaboration to happen.

2. Scrum not only restores simplicity, Scrum brings empirical process control. All elements of Scrum support the process of regular inspection and adaptation. Empiricism is the way for people, teams, and organisations to deal with the complexity, uncertainty, and unpredictability typical of product development. The Scrum events set the frequency of the inspection and adaptation process. The artifacts provide transparency to all information required. As all waste has already been removed from the Scrum, the framework is highly cohesive. Every element has a clear ‘why,’ or purpose. Omitting any core elements breaks the cohesion, and is likely to cover up existing problems and impede the transparency required to continuously adapt, i.e. to be Agile.

3. Scrum, when employed well, allows a continual discovery of what is possible, what is not, of what works, and what doesn’t work. Throughout this journey of discovery, the value of the work done is incrementally optimized. The product is regularly delivered to the market. It is extremely helpful to have a simple, yet proficient, tool like Scrum in highly unstable circumstances.

4. Employing Scrum is a journey in itself. Mastering Scrum takes practice and time.

Learn more about the myths about Scrum and DevOps. Download the whitepaper now brought to you in partnership with Scrum.org.

scrum ,product development ,agile

Published at DZone with permission of

Opinions expressed by DZone contributors are their own.

{{ parent.title || parent.header.title}}

{{ parent.tldr }}

{{ parent.urlSource.name }}