Agile Development

Much of the technology, in particular in the software industry or technology area is large and complex. In the meantime, for example, large technology companies need to invest several hundred thousand person days to come up with their next release of a product.

The new way to do things

In the past, the product development cycle was often organized sequentially. After a requriements-rollin of several weeks, and development phase of several months followed, and then the production, testing and shipment.

At the end and after several years, the finished product was delivered, often with a time delay, or with budgets exceeded.

The main disadvantages of such product development organization are the high amount of inflexibility or overhead, and the high risk to develop a product, which does not meet any longer the changed customer needs.

In the last years agile methods were put into operation, which help technology companies to tackle these disadvantages. These split down the development process into smaller slices, and bring it closer to the teams.

Here references to two short videos on, which explain the SCRUM method. Although they present similar content, they use alternative approaches to present the information:

The videos help you to understand the initial concept. They make you used to terms, such as the Product Backlog, the Release Backlog, Sprints, Burnout Charts, or daily Scrums. They further introduce roles, such as Product Owners, Scrum Masters, Customers or Executives.

Weiterführende Informationen

Das Original dieses Artikels ist auf Der Produktmanager erschienen (©Andreas Rudolph). Regelmäßige Artikel gibt es über die (→Mailingliste), oder indem Sie →mir auf Twitter folgen. In der Online Version finden Sie hier die versprochenen weiterführenden Links:

Comments are closed.