My Scrums (daily stand-up meetings) now incorporate this little question from ‘The 4-Hour Workweek’ by Tim Ferriss, highlighting a couple of Scrum principles:
If this is the one thing I accomplish today, will I be satisfied with my day?
On the outset, I know I am pretty ambitious about what I plan on doing per day, but framing the daily list in this way not only sets a clear priority as a tactical Product Owner, but also stresses that something is getting done. At the end of the day, it is not left in progress, it’s… done!
If I can’t see myself getting the one thing done that day, it might be due to impediments, or the task/story is just too large. (Hmm… really? Can’t get one thing done? Let’s address this or, heck, just accept this…)
If I can see myself getting the one thing done that day, the question not only leads to a visualization, but also to a sense of future satisfaction. (Hmm… yeah… I can get that done, I can see it now… and it’ll feel good, maybe even awesome…)
In ‘Tribes’ by Seth Godin, he essentially states:
happiness = initiative
The book is about leadership and creating movements where he encourages you to become a heretic – create something people will criticize because you so passionately and fanatically believe in challenging some status quo… and you’re most likely not the only one. Congrats – this makes you a leader, you suddenly charismatic sonuvagun, you. You feel that fire burning in your chest, driving you forward? That initiative? Seth calls that happiness.
In ‘The 4-Hour Workweek’ by Timothy Ferriss, he essentially states:
happiness = excitement
The book steps through his method for nixing the deferred-life plan of typical retirement and designing a luxury lifestyle that values freedom in time and freedom in mobility. Once you set yourself up with more time and a greater ability to travel… now what? He argues that answering “What do you want?” and “What are your goals?” are insufficient for filling this new void and nailing the essence of what we are all after. Drawing on the analogy of indifference being the opposite of love, not hate, he submits the opposite of happiness being boredom. Playing the ‘opposite game’ again, we get the opposite of boredom being excitement. (This is confusing on first read, but if you sit with it a while, it should make sense.) Tim calls that happiness.
When I now hear the phrase, “Follow your passion/bliss,” I can see how this thing called happiness, that oh so sought after goal/state, would entail an element of “Yee-haw!” excitement, and “Get out of my way or join me: I’m on a mission!” initiative.
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
I find I am less likely to execute a 15-minute stand-up meeting with myself in the morning if I’d rather be lying in bed because I am tired.
Solution: commit to getting a decent amount of sleep every night. It starts with going to bed at a consistently decent time.
This is what I am working on.
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.