Back in 2001, having recently arrived in the UK from New Zealand, I stumbled upon Extreme Programming (XP). This framework, and its relatives, promised to revolutionise software development. At the time, “Agile” was an enigma – a term met with puzzled looks and raised eyebrows. Fast forward 24 years, and the landscape has shifted dramatically. “Agile” has come and gone. People are shouting “Agile is Dead!” If somebody says “Agile” they are met with scepticism and, in some circles, outright disdain. Anti-Agile is the new Agile dogma but I’ve never been much for dogma. I care about what works. Despite the changing tides of terminology and perception, the core principles that drew me to Agile remain the bedrock of my daily practice. I just don’t often say that.
Continue reading
Tag Archives: agile
Software Management Triumvirate: Delivery, Product and Technical
I view Delivery, Product and Technical as the three legs of software management stool. I have people responsible for these elements at both programme and project/team level.
Continue reading
PDCA – Plan Do Reflect Improve. Um, sorry, I mean Check Act
I’m a huge fan of the plan-do-check-act (PDCA) cycle. It was originally intended for process improvement within manufacturing but I now see it everywhere. But, being an Agile kind of guy I wish Deming had put “Reflect” and “Improve” into the name.
Continue reading
Are Sprints Just a Way to Organise Releases?
Are Sprints Just a Way to Organise Releases?
I’m increasingly convinced that some teams cling to Sprints / Timeboxes because they facilitate release planning. A Sprint = a mini-Release = real simple. However, continuous delivery means these “Sprints” are not real Sprints.
Continue reading
Contracts do not fix incompetence
“Contracts are the least powerful in getting people to do something. A contract does not fix incompetence.” Not my words, they come from Rajesh Mathur, but I completely agree.
Continue reading
Programmes are more than Big Projects
Some projects deliver products and some programmes also deliver products. The difference is the goal. The goal of those projects is to deliver the product. However, the goal of these programmes is to deliver benefits deriving from the new product. I’ve written about the difference between programme, project, portfolio and product management before, but feel in need of a new rant – a rant brought on by DAD.
Continue reading
Focus – “If you chase two rabbits, you will not catch either one”
Whether a Russian hunter or a software/project/programme team the proverb “If you chase two rabbits, you will not catch either one” offers useful advice.
Continue reading
Shaping a team – Get good people and put them in the right role
“When will Stu stop playing with code?” The question was about Stu Fieldhouse, a Technical Project Manager working on my programme. My answer was “Never”. I had brought Stu in exactly because he plays with code. Or, more constructively, he fixes problems and lets us move on. Fast.
Continue reading
Unfortunately Corporations Equate Weight of Paper with Safety
I believe in barely sufficient documentation but Corporations equate paper weight with safety.
Continue reading
User Stories are Experiments
Mini-experiments are a key aspect of the Lean Startup movement, so I like the idea of user stories as experiments.
Continue reading