Bookmarks for December 4th through January 10th

These are my links for December 4th through January 10th:

Bookmarks for June 30th through July 2nd

These are my links for June 30th through July 2nd:

Bookmarks for May 1st through May 22nd

These are my links for May 1st through May 22nd:

Bookmarks for June 8th through June 14th

These are my links for June 8th through June 14th:

Bookmarks for April 22nd through April 24th

These are my links for April 22nd through April 24th:

Bookmarks for April 17th through April 20th

These are my links for April 17th through April 20th:

Bookmarks for April 14th through April 16th

These are my links for April 14th through April 16th:

Bookmarks for January 26th through January 27th

These are my links for January 26th through January 27th:

The Simplest of Organisation

Ever since I started implementing SCRUM for my application development at work friends of mine have expressed an interest in the way it works.

Recently even people passing through my office – there talking to my colleagues and who I don’t know very well – have been remarking on the backlogs which are displayed in a prominent position above my desk. I think they’re impressed by the simplicity of the system and how effective it seems to be for me.

I must admit my backlogs are simpler than the full blown setup. As I’m still in the process of hiring, I currently only really develop alone so I’m not bothering with the intermediate item-in-progress stickies.

I also have tasks organised in a 2-dimensional area with axes for complexity and importance. Although sprint backlog tasks are prioritised by my customers, it’s been proving useful to have my take on these attributes displayed spatially rather than just writing ‘3 days’ on the ticket.

In fact I keep my product backlog organised this way as well, as soon as tickets come in. It allows me to relay my take on the tasks to the customers straight away, whether or not we’re building a sprint backlog at the time. When a sprint has finished the product backlog is reorganised to take account of any changes, e.g. to infrastructure, affecting the tasks.