Soweto Marathon (Ubuntu for the average middle-class white guy)

Share:
[MARATHON #168 / 11th Soweto Marathon / 4 Nov 2017]

The annual trek to Soweto Marathon did not get off to a good start… The Saturday morning race number pickup was frustrated by terrible traffic on the M1 (down to one lane for barrier repairs) and when I finally got to registration it was with a flat tyre and two moaning kids.

Things you need to bring to race registration:

  • Identification
  • Championchip
  • Printed confirmation of entry

Things you don’t want to bring to race registration:

  • Kids

Things you want to avoid bringing to race registration at all costs:

  • Moaning kids

Continue reading “Soweto Marathon (Ubuntu for the average middle-class white guy)”

Share:

How George Costanza, Frogger & a Craving For Sushi Help Explain Features & User Stories

Share:

In classes I teach, there is often confusion between what is a feature and what is a user story. This article is a simple analogy (a quest for sushi) that helps to explain:

  • The difference between a feature and user story.
  • How user stories can be broken into incremental chunks.
  • Why George Costanza is not agile.

Continue reading “How George Costanza, Frogger & a Craving For Sushi Help Explain Features & User Stories”

Share:

Phoenix “It’s a Numbers Game” Marathon – Mixing with UK’s Lunatic Running Fringe

Share:
[MARATHON #167 / UNIQUE MARATHON #85 / 7 OCTOBER 2017]

In my opinion, the best way to get a good night’s sleep on a long-haul transatlantic flight is to run a marathon: A marathon (combined with a few “nightcap” beers) is the perfect recipe for a blissful flight!

The first challenge was a logistical one – find a marathon close enough to my hotel in central London to get there, run, get back, shower and make my flight (plus have enough time to rehydrate with a beer or two before boarding).

Spoiler Alert: I managed to find time for a beer before my flight home.

Continue reading “Phoenix “It’s a Numbers Game” Marathon – Mixing with UK’s Lunatic Running Fringe”

Share:

Cape Town Marathon

Share:
[marathon #165 / unique marathon #83 / 17 September 2017]

I was looking for an excuse to take a long weekend in the Mother City – and the Cape Town Marathon more than justified a trip down south.

Plenty to see in the heart of Cape Town including the Mount Nelson Hotel, South African National Gallery, South African Holocaust Museum, St Mary’s Cathedral, Houses of Parliament, City Gardens, City Hall and the Castle of Good Hope.

Continue reading “Cape Town Marathon”

Share:

6 Reasons: From 12 Months to 2 Weeks for Feature Delivery

Share:

This article is a supplementary appendix to the post: The Power of Feature Hypotheses.

Where We Were: 12 Months to Deliver a Small Feature

The graphic below is an example of a feature that previously took 12 months to deliver when we were working waterfall. This was the typical cycle-time for a small feature. Larger features would usually take over two years to flow through the system. With agile, we would now expect this same feature to be complete in a two week sprint. This article provides the six main reasons for the massive cycle-time reduction.

An example of a small feature that took 12 months to deliver in waterfall. In agile this can easily be done in two weeks.

Continue reading “6 Reasons: From 12 Months to 2 Weeks for Feature Delivery”

Share:

Using Hypothesis Statements for Features in Software Development

Share:

This article is an supplementary appendix to the post: The Power of Feature Hypotheses

Experiment-Based Approach

Instead of making up-front decisions based on assumptions and imperfect knowledge we create hypotheses and run a series of experiments to determine whether each hypothesis is true or false. The results determine what we should stop doing, start doing and continue doing. Based on complexity, uncertainty and rapidly changing environments, most software development projects are “research and development” exercises ideally suited to this hypothesis-based approach. Continue reading “Using Hypothesis Statements for Features in Software Development”

Share: