- All posts are released under CC 3.0 by-sa unless otherwise stated.
Pages
Follow me on Twitter!
My Tweets-
Recent Posts
Recent Comments
Categories
- bdd
- breaking models
- business value
- capability red
- coaching
- complexity
- conference
- csharp
- cynefin
- deliberate discovery
- evil hat
- feedback
- humour
- jbehave
- kanban
- lean
- learning
- learning models
- life
- nlp
- open source
- real options
- scale
- scrum
- spike and stabilize
- stakeholders
- stories
- testing
- Uncategorized
- uncertainty
- values
- writing
Archives
Meta
Category Archives: stories
BDD: A Three-Headed Monster
Back in Greek mythology, there was a dog called Cerberus. It guarded the gate to the underworld, and it had three heads. There was a great guy called Heracles (Hercules in Latin) who was a demi-god, which means he would … Continue reading →
The Five Whos
Many of the companies I visit start with much the same problem: the development team aren’t collaborating effectively either internally or with the business, so they would like to adopt Agile, or better forms of Agile. Usually these are pretty … Continue reading →
Commitment – a novel about managing project risk
If you’ve heard me speak at any conferences or read my blog over the last few years, you’ll know that I’m really, really into Real Options. I’m half-tempted to get “Options have value. Options expire,” added to my tattoo. The … Continue reading →
The Myth of “What” and “How”
I often hear things like, “Tell the team what to build, but don’t tell them how to build it.” Or, “A feature is what you’re building. A story is how you’re going to build it.” Or, “When you’re doing TDD, … Continue reading →
Splitting stories into tasks – when, why and how (or not)
Before I write anything about this, I’d like to clarify what I mean by a task and a story. A feature is something tangible that works and which we could potentially deliver, if it was enough to provide business benefit. … Continue reading →
ATDD vs. BDD, and a potted history of some related stuff
Another question that people often ask around or to me is, “What’s the difference between Acceptance Test Driven Development and Behavior Driven Development?” To explain, I’ll go back to the time when I first learnt BDD. BDD started at a … Continue reading →
They’re not User Stories
Reading Simon Baker’s post on metrics made me smile. I rant about similar misuse of metrics quite a lot. A common reason that I see targets and metrics fail is because they’re aimed at a perceived circle of responsibility – … Continue reading →
Mocks, outside-in, swarming features and guesswork
The paradox of mocking When we code from the outside-in in BDD, we start with the layer we know – the UI, often graphical – establish collaborators for the UI, establish collaborators for those classes, and work our way inwards … Continue reading →
Business Velocity
Pascal Van Cauwenberghe has written a great post on estimating business value, tying it into a feature-injection style template. I particularly like the idea of calculating business velocity, and showing value earned over cost on a visible chart. Even though … Continue reading →
Pulling Power and Kanban experiences
My first ever article, “Pulling Power: a new Software Lifespan” is up on InfoQ. BDD, Feature Injection, Lean and Kanban playing nice together! Big thanks to Dan North, Chris Matts, David Anderson, Amr Elssamadisy and the amalgam of developers who … Continue reading →