I’m proud of all my teams – good people doing great things. But I’m particularly proud of my current team because it was the hardest to form, being split between London and Berlin. I formed this team by turning up. A simple message although quite painful for myself and my family. Actually that pain is part of the reason my approach works. Leaders turn up and the team appreciates that.
Continue reading
Tag Archives: flow
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
Albert Einstein would have liked Retrospectives
I believe Albert Einstein would have liked retrospectives.
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
Need an unsolvable problem solved? Call in the Development Paratrooper
A guy walked up to me and said “I hear you’ve got a problem with Flash”. I hadn’t met him before but I’d heard about him. Mike Brown the Development Paratrooper.
Continue reading
Work Item Tracking, to See or Not to See?
Work Item Tracking, to See or Not to See? This is always an interesting debate. The lists are much longer but for simplicity I’ve surfaced a few salient points. So which is best? Physical or virtual? For me physical boards win hands down, but there are occasionally good reasons for a careful blend.
Continue reading
How to Distinguish Between Activity and Queues on a Kanban Board
My Kanban boards follow a certain pattern, what I call the “Step In Progress then Done” pattern. By default each step in my process has an “In Progress” column and a “Done” column. Some people don’t like that. You wouldn’t believe the number of conversations I’ve had about it. These conversations more or less boil down to me explaining that “Done” is a queue, not an activity. And I want my Kanban board to make it clear that each activity has an associated queue.
Continue reading