We here at AgileScout.com manage our workload in an Agile fashion. We use a kanban board to manage our backlog, our in-process, and complete articles ready for publication.
We have found that using Agile for work just makes sense, and since we’re still a small shop, it makes managing the workload easy.
So what if you took an Agile approach to other tasks in life?
Well that’s exactly what Brock Bigard did when he prepared for a marathon run. He used user stories, iteration lengths of one week, iteration planning, and a retrospective.
- User Stories – User stories describe something a user wants to accomplish. Stories can refer to new features or functionality and are typically written in the “As a, I want, So that” format. In regards to marathon training, a story equates to a workout session.
- The Iteration – An iteration is a cycle of development. It starts with a group of stories and ends with a release. The release should include enhancements from the prior release. Since most training programs are broken out into weeks, it makes perfect sense to have our iteration be a week long.
- The Planning Game – The planning game is when developers and customers get together and plan the upcoming iteration. Our planning game will consist of looking at our schedule and seeing what workouts we think we can perform in our week long iteration.
- Retrospective – This is time scheduled after the iteration is complete and before we plan for the next iteration where we reflect on the iteration and highlight successes as well as look for ways we can improve going into the next iteration. An example would be to not drink a lot of alcohol and eat Mexican food the night before a long training run.
Way to go Brock, let us know how the marathon went!