Peter identified a couple of scenarios where he felt that 'Solo Scrum' could be appropriate:
- A full time developer doing open source development part-time
- A solo consultant developing applications for non-technical clients
- A 'work at home' contractor managing multiple clients
The traditional problems of planning don't go away when working on your own (as I said at the session 'Fail to plan, plan to fail'). Working on your own necessitates an efficient process for planning and managing the plan (a bit more than the 'back of an envelope' note). There are a number of Eclipse plugins (e.g. mylyn) which offer the right balance in terms of monitoring the work activity without distracting from the task-at-hand.
Some interesting ideas were discussed, including the observation that many team collaboration software packages often includes a free version for a small team (where small can be up to 5). This can overcome a often heard comment which was that I don't have the time/experience/etc to set up a 'professional' development environment (the minimum being a source control system, an IDE and a bug tracking system) from scratch.
Peter has now started a Google group to further the debate. I will watch with interest.