I’m experimenting with Sprintless Agile as a methodology for my personal projects. It’s agile without managers and deadlines. It removes the artificial constraints of arbitrary deadlines from software projects. Because I just spend the free time I have on my projects, there is no need for deadline tracking. The need for task estimation is therefore eliminated, leaving priority as the only criterion to be freely applied to all tasks equally. Without the “get it out the door” pressure, crunch time is lost, but releases are more continuous than planned, and life runs more smoothly. The hope is that projects will be able to focus on the important goals instead of throwaway demo work. The fear is that too much time will be spent obsessing over unimportant tasks. Therefore, the top priority becomes to continuously prioritize.
-
-
Archive
Footnote: I threw this up to test the ability to coin a term in google results. Seems to have succeeded.
The obvious problem with this is generation of quality deliverables. Without a sprint, you don’t have a specific tie-off point to make sure everything is stable and not only demo-able, but ready for a production release. That’s what I’d call a fatal flaw.
Now if you’re attempting to pull off continuous delivery… that’s another story. I’m setting myself a personal goal to attempt continuous delivery of my next (first, ha) massively popular software application. 🙂