hypothesis Archives - The Running Mann

16th August 2022

A Behavioural Science Experiment to get Leaders to Complete an Agile Maturity Assessment

When it comes to behavioural science, I am an enthusiastic amateur. I guess the same could be said for my marathon running infatuation which, although prolific with over 250 completed, is still firmly footed in the ‘recreational amateur’ category. My payslip reads ‘Agile Coach’ so I’d like to think that I’ve managed to breach the amateur category in my chosen career (but you might need to check with my colleagues to confirm whether I do indeed qualify as a professional). It’s not often that running, behavioural science and agile coaching intersect but recently they did, so I decided to use the opportunity to run an experiment and this is what happened. Continue reading “A Behavioural Science Experiment to get Leaders to Complete an Agile Maturity Assessment”

25th September 201726th May 2020

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

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”

24th September 201717th February 2020

Using Hypothesis Statements for Features in Software Development

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”