This is my odd foray into the world of optimized self improvement — a glimpse of what happens when agile software methodology meets an old New Year’s resolution gone too far.

As 2015 winds to a close and we look into the year ahead, it’s once again a time to dust off the Shake Weight, blend together mysterious concoctions of leafy greens, and binge-learn the hottest new programming languages. Hopefully my experiences will be a fresh twist to the sometimes trite traditions we experience this time of year.

So — what exactly is agile software development? I’ll leave the description to the folks at Wikipedia:

A set of methods in which requirements and solutions evolve through collaboration between self-organizing, cross-functional teams. It promotes adaptive planning, evolutionary development, early delivery, continuous improvement, and encourages rapid and flexible response to change.

In other words, everything that isn’t a New Years resolution.

Of course, there are limitations to applying a team-oriented process individually (especially when you’re the product), but hey, at least it forces cross functionality. It’s also probably worth noting that I based a lot of my strategies off of scrum — one common framework of agile development. So without further adieu, here are the steps I took to become a bum master.

Step 1: Outcomes

This is usually the boring part. It’s not that setting goals isn’t important, it’s just that creating goals is something I’ve always found monotonous. Goals are like wearing deodorant: you should do it or you stink. So instead elaborately defining, planning, and acting on many large goals, I decided to made them small. Ambitions for each day.

  • Apply my attention to the present moment.
  • Maintain a focused, productive work ethic.
  • Engage the world with passionate curiosity.

These are three of the ten daily ambitions I decided on — my favorite ones were flexible and really got me pumped. You might be thinking that this isn’t really a goal, but that’s not the point. Having these ambitions allowed me define my real goals every morning. Which brings us to the next step.

Step 2: The morning stand-up

This is where the magic happens. In scrum, the stand-up meeting is a brief check-in, with each team member answering these questions:

  • What did I accomplish yesterday?
  • What will I do today?
  • What obstacles are impeding my progress?

So, I decided to give it a shot too! Each morning, all year, I took a look at the goals from step one and decided on a few measurable actions to evaluate my progress in that area. Did I wan’t to nail my first goal for that day? Then I would need to be present during conversations with family. How about curiosity? Maybe that meant googling random tidbits of information a professor mentioned in class.

If I was hitting a slump, I would just consider which obstacles were reducing my performance — usually lack of sleep or distraction.

The trick for me was to decide specific criteria of measuring my performance that day. I would then evaluate my successes at the beginning of the next stand-up based on those criteria. The most invigorating aspect of this process? It fostered one of my favorite aspects of scrum — Kaizen.

Picture description

Commonly translated as incremental improvement, Kaizen is a Japanese phrase popularized by Masaaki Imai’s book Kaizen: The Key to Japan’s Competitive Success. Improvement is wonderful in organizations, but I found it even more fun personally. Trying to do better each day was addicting. It gave the freedom to care less about my G.P.A, less about landing a top tier summer internship, and care more about quality of life. Instead of external outcomes, it was the internal effort that mattered. None of that would have happened without accountability.

Step 3: The bum master

While implementing scrum, teams are constantly in contact with the stake holder. The stakeholder could be the end customer, or it could be the business owner, sales department, or even the scrum team itself. The scrum master is a facilitator of sorts — the person “in charge”. This past year, I was the sake holder, the team, and the person responsible for the process itself. I was the bum master.

In order to keep myself in line and accountable, I appealed to the nerdy C.S. student inside: aggressive spreadsheeting.

For every week, a goal occupied a row, and each day occupied a column. Pretty basic stuff. I used the day score row to get an idea of how well the day went overall, with 50 being average. Cooler yet, I could compare how well I did in each area at the end of the week.

Assigning a score to each goal during stand-ups got hairy at times. For example, what distinguishes a six from a seven? Which behaviors qualify as a five, as opposed to higher or lower? Ultimately I decided to not allow more than two fives each day. Everything can’t be average, right? I also decided to apply a mental curve on the whole thing — 1’s and 10’s were really hard to get.

I wanted to design a system to encourage a little improvement each day, and make the best decisions possible. That’s why I did my best to evaluate based on the decisions I made — the mundane choices which cascade into behaviors which cascade into habits.

Step 4: Iterate

Once the weekly process was developed, repeating it by week and month fell into place. I played with adopting a sprint technique, which added a weekly reflection to the daily stand-ups. It was with mixed results. Looking at an entire week’s progress aided reflection, but it also distracted me from focusing on the next day. Plus I was lazy (shh.. don’t tell the bum master).

I slaved away at a few other spreadsheets tracking the weeks and months. Those weren’t too interesting, so instead I’ll share this:

This a flowy, colorful breakdown of the years ratings. As you might see, I didn’t adopt the two 5’s rule until March, leaving the first few months bound together tightly. My work ethic was fantastic during June. Compassion also looks like an area for improvement this year. Honestly — I don’t know how much I can read into it other than basic observations like those.

What I do know, is that making the lines ebb and flow as the year progressed was rewarding. Tracking progress was a blast, and feeling motivated to make the bars hit an all time crest was even better. I feel obligated to keep the agile experiment going into 2016, so expect more iterations and continuous improvement.

Anyway, enough of working on comprehensive documentation for now — time to keep working on the real deal.

Thanks for reading!