Posts tagged #agile

Articles and notes about my experiences within the agile movement and the agile value system. Popular:

Splitting User Stories

User Stories are short and simple descriptions of a feature told from the perspective of the person who desires the new capability, usually a user or customer of the system. It´s called User Story because you put the user into focus. Therefore a User Story should lead to a product increment that can be seen valuable from the user- or business perspective.

The balanced organization

The agile manifesto defines a collaboration culture. But what if your current environment is not collaborative? This article describes alternatives for moving into the agile direction.


Scaling agile means more than one team is required to get a thing delivered. Each team not more than ten members. There will be adjacent topics which belong to an agile organization, but when we focus just on delivery, that´s it, multiple teams working on one thing.


Self-organization is the determining element for agile teams and companies. To think and act accordingly requires the acceptance of evolutionary forces which are an inherent part of any social system, whether we like it or not.

The agile worker

The agile worker exists because of differences between theory and reality, and because insights can be gained through these discrepancies.

The art in our work

The Agile Manifesto represents a force that is behind any particular agile procedure like XP, Scrum or Kanban. This force, the culture to challenge the status quo, attracts certain people and companies.

Five dysfunctions of a team

Deliver with each iteration a done piece of meaningful work and collaborate as a team. If you do only these two things and forget about all the concepts and procedures we like to talk about in the agile world, you already have made a good part of the agile journey.

Definition of Done

The Definition of Done (DoD) is not only a checklist that has to be executed to get a piece of work delivered. The DoD and the path to its determination opens a space for agile thinking and acting which can actively be leveraged by the delivery team and the surrounding organization. It is a great entry point for agile delivery, and it can be used in Scrum, Kanban or any other procedure with iterated delivery.

Scrum and Architecture

Cooperatively making architecture decisions, at a point in time when they are needed, and not earlier, is a quality-improving paradigm in agile software development. Conceptual integrity in the flow of architecture decisions will only be achieved if one person has the final word regarding those decisions. This is the architect, whose rights and obligations in the context of the Scrum process are being reflected in this essay.

The Box-Bullet-Line (BBL)

Many important aspects of software development are invisible. When creating software we work through different abstraction layers by analyzing symbols and writing code.

A Sprint is not a milestone

A Sprint is a sensor that allows us to see what has been done, what impediments are in our way and how we did better in comparison to previous Sprints.