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

Splitting User Stories

A User Story can cover vast amounts of functionality with a single sentence, which requires a team many weeks or even months of work to get it done (often called epic). Splitting such stories into pieces which are valuable for users and still deliverable within a Sprint is challenging for many teams. However, there are good reasons why you should do it.

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.

Pocket Git Guide

Get Git on your Mac Get Git on Windows The Git shell Tell Git who you are Get help from Git Create a new local …

Supersize

We have to scale agile when more than one team is required to get a thing delivered. Each team, not more than ten members. There …

Self-organization

Past and present Complexity Self-organization Cooperation and communication Transparency Results, feedback, and continuous planning Performance orientation Doing Divergent-convergent thinking and responsibility Use what is already …

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 work and collaborate as a team. If you do only these two things and forget about all …

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 …

Scrum and Architecture

Cooperatively making architectural 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, serving the product, whose rights and obligations in the context of the Scrum process are being reflected in this essay.

The Box-Bullet-Line (BBL)

Dependency Flow Caller Sequences Synchronous and asynchronous Many important aspects of software development are invisible. When creating software we work through different abstraction layers by …

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.