DAY 4… Where we get friendly. Business people and developers must work together daily throughout the project.

DAY 3 …This one is pretty self explanatory: Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. We like to deliver frequently in short bursts, and this enables many good things.

DAY 2 ... Anticipate and account for change. Expect change. Because you don't want to deliver the wrong thing just because you planned it. The plan is just that, a plan. 'The map is not the territory'.

Day 1 .. and the first of the series! Kicking off with… our highest priority is to satisfy the customer through early & continuous delivery of valuable software

PART 3

…of a three part blog series about a history of Agile as told from our protagonists view.

PART 2

…of a three part blog series about a history of Agile as told from our protagonists view.

PART 1

… of a three part blog series about a history of Agile as told from our protagonists view.

A few years ago I was working at a company who had started a digital incubator as a protected and contained special project, outside of the large corporate. It was peopled with a team of the brightest and best from within the organisation and I was part of the coaching cohort supporting their incubator with skills and facilitation.

There’s nothing I like better than using a physical wall to make a team’s work visible and communal, and seeing it's impact on team communication.