When I was a tutor at university, there were three main types of students I saw in the lab: the Googlers who would search for an answer or three (in those days Experts Exchange, today Stack Overflow), mangle something together then either figure it out and simplify or give up ; the ones who cared … More Is software your vocation or just a job?
Reducing waste is one of the key concerns of agile development, and is a defining character for Kanban, where blockages are ruthlessly identified and resolved. Timeboxing provides a low-cost means of identifying waste and a framework for tackling it, but doesn’t provide many solutions on its own. For tasks that continually cause blockages, such as … More Reducing waste by automation
I’ve created teams from scratch and been brought in or promoted to lead existing teams. I’ve made a few mistakes, especially when starting, and I hope sharing them with you will help you to help your team faster. Responsibility When I started out, I often started a new team with a quick speech. And in … More Bootstrapping into a team
In the comments to the previous Everyone Has A Voice post, I was asked to expand some more on the Lean Coffee Retrospective. It’s not a new idea, but it’s definitely one worth sharing in the hope that it helps others. I first encountered the Lean Coffee format at last year’s CodeCraftConf, and read about … More Lean Coffee Retrospectives
@joe_jag a developer who practices continuous improvement, with our without the support of am agile team. — craignicol (@craignicol) September 29, 2015 A developer who practices continuous improvement, with or without the support of an agile team. You care about being better. You consider code to be craft. You’re only happy when you deliver value, … More What is an agile developer?
On a previous project, I had a long-running discussion with several stakeholders about using story points over time estimates, because how could I know that we were going to deliver without a deadline? I started using time estimates on a previous project because one release failed to deliver, and so I decided we needed a … More Story points over times in estimates, and the power of abstraction over teams
Did you learn something? Did you stretch yourself? Did you challenge your assumptions, or your practices? Do you feel like you achieved something last week? Did the frustrations inspire you to make it easier next week? Did you share them with others, in the pub, or on your blog, so others can learn from your … More Did you have a useful week?
Good architecture can respond to new requirements. It’s malleable where it needs to be. A good leader trusts their team. And builds their team so they can trust them. Architecture leads software, it defines the agility of the rest of the development, and it defines the fixed points that cannot be changed, that will always … More Embracing Agile Architecture
When doing scrum planning, trying to figure out what can be achieved in a sprint, there’s always variation. Especially in projects where you can’t rely on what came before. You can use yesterday’s weather, and break down tasks, but if you can’t estimate more accurately than “between a day and two weeks”, and you can’t … More Planning: the green and amber list
Process impedes progress. It’s the hurdles, and the red tape, that stop you from doing what you want to do. It’s why you can’t have administration rights on your machine, it’s why you can’t commit directly to master. It’s why developers don’t get logins to production. It limits your agility. Sometimes that’s a good thing. … More Cognitive load: Default to success