Read Next

Two Paths to Being a Writer

Question from a reader -

You have maintained your commitment to being prolific which is made even more exceptional by the fact you are travelling around the world at the same time.

I realise your article on being prolific is about this, but accepting that I'm going to release a lot of crap before I realise something good is a tough wall to knock down. My biggest issue writing anything seems to be that it feel insufficent. Naturally no post I write has the length of Steve Yegge, the persuasiveness of Paul Graham, the content of Unqualified Reservations etc. etc. and while I can consciously accept this, there seems to be some mental block. How do you go "that's sufficient" and release it into the wild?

There's two basic approaches to being successful as a writer. The first, we could call the "Paul Graham / Derek Sivers" approach. This is where you explore a lot of ideas privately, go forward with the best ideas you have, and edit and polish the hell out of everything before you release it into the world. If you do this, and you've got talent as a writer, and you've got important ideas - then you're going to consistently only release masterpieces.

The second way is to just write a hell of a lot and know that a number of the things you write will turn out quite well, but your average quality level will be much lower. We could call this the "write every day no matter what" approach.

Agile Scrum: Delivering Broken Software Since 1991

On Imported Blog

Update: This is quite a long article. If you're looking for a quick read, it breaks down a bit like this:

Update 2: There are active and interesting discussions of this article on HackerNews and Reddit

I have a lot of love for Scrum, the software development process. I have my own little box of Index Cards and Sharpies, and I have sized Backlogs for many of my side projects. Scrum has potential to empower developers more than almost any other set of techniques.

But in almost every implementation of Scrum I've seen in The Real World™, managers are incentivized to help their team deliver broken software to a deadline, and usually end up succeeding in the former and failing in the latter. And when implemented like that, a system that should be an absolutely overwhelming win for developers becomes a tool to beat them around the head with...

So here's Scrum, simplified, and as it's meant to work: You have a Backlog of work to complete, broken down in to Stories, which ­are distinct pieces of work that should take a few hours to a few days to complete. These are frequently displayed on a Story Board, real or virtual.

Rendering New Theme...