Prioritize By

Not all stories for a ScrumOfOne lend themselves to prioritization by business value. So what other criteria am I using? Prioritize by…
  • How badly I would like it
  • How badly I want it
  • How enthusiastic I am about it
  • What gives me the greatest joy / bliss
  • Highest frequency of usage
  • Ability to develop something to mastery
  • Ability to make ScrumOfOne more transparent
  • Upkeeping & maximizing already solid investments
  • How much it would ease my mind
  • How awesome it would make me feel
  • Biggest step towards product vision

Show Then Tell

Over the past few months/sprints, I’ve been developing a system to more easily adopt Agile Living. Stories have been mainly gathering and molding stories into a proprietary format I have been developing for a while. With bookmarks to Google Docs (‘cloud’-enough for now) on my smart phone pointing to a product backlog, sprint backlog, Scrum script, Daily script, and a few other things, the motions for my own ScrumOfOne have become significantly more fluid.

Progress has gotten me to the point where I am back to dedicating time to this blog, with posts planned for twice a week: once on Sundays after my mini-retrospective and once on Wednesdays as a temperature check on mid-week execution of sprints.

Part of this reboot has been after an acknowledgement of how different facets of personal growth, as well as the numerous projects I want to implement, all feel like they should be their own product backlog. Some products represent continual improvement (physical, cultural, residential) and some represent discrete states of accomplishment (this blog, learning to sail, own music studio), so the organization and prioritization of the numerous stories from the numerous backlogs has required some work, thus why I am only getting back to blogging now.

Happy Thanksgiving!