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.
The following are my notes from a Scrum Alliance article – its title is that of this post.
By Bachan Anand, CSM, CSP, he shares ways to tune the scrum / daily stand-up meeting. Building up to a very neat table, he outlines how to run the scrum of a high-performance team in terms of self-organization, focus, collaboration, rhythm, courage, and respect. My favorite example is a solution for one particular self-organization issue, where team members share status as if reporting to managers (ScrumMaster and Product Owner), instead of sharing status with their fellow pigs.
Each time a pig looks at a chicken during the scrum, the chicken should look at his/her shoes.
It’s finally Spring in Boston! It’s nice outside! I want to BE outside! This yearning is effectively an impediment!
Thus, the balance of a game plan and reality results in a strategy that makes me feel less guilty for enjoying the weather while still accomplishing the most per time spent on these sprints: Ruthless Story Completion.
I am now spending time on getting one story done at a time – this results in two levels of satisfaction. Sure, I get the points associated with that story – a shallow sense of feeling good; however, I then know I have attained a piece of functionality associated with the story – THAT is the deeper level, the fulfillment.