The Value Ladder highlights how a supplier contributes to the success of the customer. The way I see it programmes and projects can be mapped onto the Value Ladder.
Continue reading
Category Archives: Musing
Continuous Delivery by Default; Timeboxes by Exception
Once I used timeboxes by default. Now I relegate Sprints and such like to exception situations.
Continue reading
Programmes can use more than one method: Kanban, Scrum, XP, BDD, etc
I have my preferences – Kanban and BDD – but don’t enforce these on my teams. That means I’ve got a couple of Scrum (ish) teams and teams that don’t use BDD. And I also have a bunch of people working in isolation – I just leave them to it.
Continue reading
Product Owner – leader, facilitator or unnecessary overhead?
Daniel Markham thinks the Product Owner is “the perfect scam in the Agile community” and recommends getting rid of the role. This might work for highly functioning teams working in highly functioning organisations, but for not normal teams. For normal teams in normal organisations the Product Owner performs a valuable role as a facilitator and, if you are lucky, a leader.
Continue reading
Test driven architecture – use your tests to inform architecture
As test-loving development teams, we are all painfully aware of the complexity of getting an application into the zen state of development – quick, test-driven red/green feedback for developers, software designs that are functionally on-the-money from a test-led, “outside-in” approach (from BDD), and a nigh on seamless continuous delivery process as a result. Very few teams achieve this, and those that do are frequently gifted a green-field project in which to engender them.
As test-savvy teams, when tests start to hamper the release process, we often assume our approach to testing needs an overhaul, but that might not be the case. Here we look at the role of architecture in test-driven applications, and examine whether we should listen to our tests to examine our macro design.
Continue reading
35 person-years worth of prototype is a fantastic spec
I once invested 35 person-years worth of effort on prototyping. From my perspective this was time and money well invested. By the end of that time we knew, really knew, what problems our customers were facing and how to solve them.
Continue reading
#NoEstimates #YesEstimates #NoEstimates #YesEstimates
I’m not a fan of the #NoEstimates hashtag on Twitter. It turns out, after many blog posts and tweets, that #NoEstimates is a Contranym – a word that can function as its own opposite. #NoEstimates can mean no estimate or yes estimate – it is up to you. Sigh.
Continue reading
I Only Trust Architects That Code
I only trust architects that code. Who have skin in the game. Who will suffer personally if they make the wrong architectural decisions. Who will dive in to fix any problems that arise from their decisions.
Continue reading
Scope Creep v Flexible Scope – Undisciplined v Agile
Bart asked “What do I do when agile is abused as an excuse for scope creep?” with the sub-text “You’re agile so you’re flexible, no?”. I say point out the difference between scope creep and flexible scope. Agile makes changing scope a zero sum game – that gives flexibility without the creepiness.
Continue reading
Choose your Lean-Agile coaches wisely; watch for Organisational Psychopaths
I’m a big fan of Lean-Agile coaches and have a list of folk that I trust to help me run transformation initiatives. But there are some cowboys out there and, at the extreme, folk who pitch themselves as coaches but are really organisational psychopaths. That is why I vet my coaches.
Continue reading