No, it’s not those two. Software Development is in part a technical challenge. Can we leverage this technology and this equipment to achieve some sort of purpose. It can be a hard challenge, often made harder by compounding mistakes along the way. One of the most frustrating things that can happen when a developer presents… Continue reading The Two Most Powerful Words in Software Development
I’m guilty of this. Many software engineers and software leaders are. Here are some examples: This story is nearly closed, but I should probably also… This story sort of includes that story, so why don’t we merge them… This sprint is nearly done, let’s delay planning the next one a bit This release could go… Continue reading Just one more thing…
A fundamental principle Don’t ask your stakeholders to pay for a stoppage while you fix all the technical debt. The above does not apply to some sort of massive expansion and rearchitecting in order to do future awesome things – people like deliberate expansions. Why? Once your time is up, the stakeholders never want to… Continue reading Spotlight on Continuous Improvement
This is one of those reality check retrospectives. A team can work hard at achieving something, but the real value generated is the value of what they’ve made, not the hours they’ve put into making it. It’s not nice to criticise or attack the effort that goes into the work because people are, on the… Continue reading Retrospective: Effort/Value Graph
When the team has been finding itself a bit constrained by niche knowledge only being known by a few people, it’s time to start bidding for knowledge transfer. The KnowledgeBay technique is ridiculously simple: Everyone considers what they think they’d like to know Everyone has a think about subjects they’d like to teach You list… Continue reading Retrospective: KnowledgeBay
You need a bit of time aside for this retrospective. It’s heavily based on the method of: Gather data – funnel all observations via cards put on a wall Model the data – try to find themes – in this case in the “uncool” areas Suggest improvements – the hottest two or three subjects should… Continue reading Retrospective: The Cool Wall
This is not a retrospective in itself, but it’s a lovely way to start a meeting. Everyone is asked to thank one or two people for something they’ve specifically done this sprint. It’s a good way to reward collaborations and remind the team the value of each and every one of its members.