Category Archives: process

On programmer behaviours that make Scrum so bad

Respectable persons of this parish of Internet have been, shall we say, critical of Scrum and its ability to help makers (particularly software developers) to make things (particularly software). Ron Jeffries and GeePaw Hill have both deployed the bullshit word. … Continue reading

Posted in agile, process | Leave a comment

Sleep on it

In my experience, the best way to get a high-quality software product is to take your time, not crunch to some deadline. On one project I led, after a couple of months we realised that the feature goals (ALL of … Continue reading

Posted in process, team | Leave a comment

There is no “us” in team

I’ve talked before about the non-team team dynamic that is “one person per task”. Where the management and engineers collude to push the organisation beyond a sustainable pace by making sure that at all times, each individual is kept busy … Continue reading

Posted in agile, team | 1 Comment

On UML

A little context: I got introduced to UML in around 2008, at an employer who had a site licence for Enterprise Architect. I was sent on a training course run by a company that no longer exists called Sun Microsystems: … Continue reading

Posted in agile, architecture of sorts, design, software-engineering, sunw, tool-support | 2 Comments

By doing it and helping others do it

We are uncovering better ways of developing software by doing it and helping others do it. It’s been 20 years since those words were published in the manifesto for agile software development, and capital-A Agile methods haven’t really been supplanted. … Continue reading

Posted in agile | Leave a comment

Self-organising teams

In The Manifesto for Anarchic Software Development I noted that one of the agile manifesto principles is for self-organising teams, and that those tend not to exist in software development. What would a self-organising software team look like? Management hire … Continue reading

Posted in agile | Leave a comment

The manifesto for anarchic software development

Go on, read the manifesto again. You’ll see that it’s a manifesto for anarchism, for people coming together and contributing equally toward solving problems. From each according to their ability, to each according to their need. The best architectures, requirements, … Continue reading

Posted in agile | 1 Comment

Stay on target…

I introduce the kind of customer who needs the Labrary’s advice with the following description: Your software team was a sight to behold, when it started out. You very quickly got to an MVP, validated its fit with early successes, … Continue reading

Posted in agile, process, team | Leave a comment

Pairing in Github

In the world of free software, it’s good to appropriately credit contributors to your community for the work they do. git makes this hard when you pair program. I was at a hackathon recently, and while I didn’t make a … Continue reading

Posted in process, tool-support | 8 Comments

Everyone rejecting everyone else

It’s common in our cooler-than-Agile, post-Agile community to say that Agile teams who “didn’t get it” eschewed good existing practices in their rush to adopt new ways of thinking. We don’t need UML, we’re Agile! Working software over comprehensive documentation! … Continue reading

Posted in agile, architecture of sorts, process | 1 Comment