Thursday, July 23, 2015

Lean Climbing

I’m on my way to Colorado for a weekend of outdoor adventures, climbing and mountain biking. As I was looking over the route for the climb (Kelso’s Ridge up Torrey’s Peak and a possible double with Gray’s Peak) I remembered an article I recently read on applying the principles of lean climbing to business (here).

I’ve done a couple 14ers before, so this will be my third and maybe fourth, all with my son. We plan on being lean on this climb. Enough water and food, but not much more. Our timebox is getting down the mountain before the afternoon thunderstorms. 

My current client seems to get lean. As we were working through the user stories for the project, they made the decision to prioritize and pull out the lower priority stories without any prompting from me. With so many of my clients, there are many discussions before they think about taking any stories out of the backlog for the current release. 


I think if I could take my clients on a climb, with each user story represented by a small rock in their backpack, they would soon realize the benefit of keeping it lean. There’s a cost with each user story, and being able to defer some stories means you get up the mountain sooner. 

Tuesday, June 09, 2015

Morning Routines

I’ve come across a number of articles lately that have talked about the importance of a good morning routine (like this one), so I have been trying to practice some of these techniques.

One practice is to start the day with meditation, not checking any electronic devices. I'll admit, sometimes when I'm working from home I'll turn on the TV while making my morning coffee before heading up to the office, but I don't start responding to email first thing in the morning.

Another recommendation is to journal. Your mind is the most sharp in the morning so that is not the time to waste responding to emails. Instead figure out what your top two or three priorities are and try to get those accomplished first thing in the morning. Journaling can help you figure out where to start your day.

I have also found that I can change my evening routine to be more productive as well. I find when I'm traveling and staying at a hotel, that if I skip the TV and put on music instead, that I'm more focused and get more work done.

So is it time to change up some of your routines?

Thursday, April 30, 2015

Time for a Demo?

When I first learned Scrum, the idea was to have 30-day (4 week) iterations with a demo at the end of each iteration. Today I see teams that have iterations from 1 to 4 weeks, or in the case of Kanban, no iterations at all. So the question is, how often should there be a demo?

I’m a believer of getting sign off on a user story once it's done. This usually comes from the person who wrote it, who may be a proxy to the product owner. So when we get to the end of the iteration, all the stories that are completed have already been reviewed by someone on the business side but not necessarily the product owner. 

So the questions is, If it’s a short iteration, does it make sense to have a more formal demo of the stories? I think in some cases the answer is “no.” 

On one of my projects where we were using Kanban, we planned the demos every 4 weeks. This allowed us to finish a set of stories that were part of a feature, so the demo was more complete. I think this approach works with short iterations as well, only conducting the demo after every second or third iteration, depending on how long your iterations are and how complex your features are. 

There's also another consideration. I work with clients building applications that will get rolled out to the organization. On these projects, we need to consider organizational change management. The demos serve as a way to help introduce the new application to the end users. So from this perspective, there may be a large number of attendees at the demos. This is another argument for less frequent demos.

So while a demo can be held at the end of every iteration, even for short iterations, there are some reasons to hold them less frequently. 

Monday, April 20, 2015

Tools

When I was young, I had a riding lawn mower. We had a big yard out in the suburbs and the riding mower made the job quicker. Today I live closer to downtown in a house with a smaller yard. I’m currently using an old fashion reel mower…no motor, just foot power to make it work. For the yard I have, it’s all I need.

With all the technology around us, it’s easy to get caught up in the latest thing. Tools can make us more effective, but sometimes they can be distractions. 

Take project management tools. There are a plethora of them around and I have used them effectively on projects. But I have also run projects with just a white board and stack of post-it notes, not letting the technology get in the way of interacting with my team.

The Manifesto for Agile Software Development says it should be “Individuals and Interactions over Process and Tools” so ask yourself if the tool you are considering is going to help you or could it just be another distraction? Put another way, A fool with a tool is still a fool."

Friday, April 10, 2015

Minimal Viable Product

I have a customer with a challenge. We've been working on an application and finished our first release. The business folks looked at it and came up with a list of "must-have's" they want before going live. The IT folks are pushing back, trying to keep additional work to a minimum before going to production. They even threw out the phrase "minimal viable product" or MVP as a way say what's the least that can be done.

However, MVP isn't about doing the least amount of work and calling it done. When taken in context of Lean Startup, it's part of a process. First you build the MVP and hypothesize what you think will happen when you go live, you measure against your hypothesis, and ideally learn something that takes you to the next step.

When I work with customers used to a more traditional approach to projects, I often see resistance to the MVP approach. They think they have one chance to get what they want, so they ask for everything. If they truly thought in terms of MVP, they would be able to think about it as what do they want first, knowing they get a chance to ask for more.

In some cases, the next step may not be in the same direction. In Lean Startup, there's the idea of the pivot, making a more fundamental change in direction. Groupon started as an online activism platform and PayPal started out building security software for handheld devices (think Palm Pilots, not smart phones). There are plenty of other examples out there of companies that didn't get the results they expected and made a pivot. Lean Startup is about getting to that point as fast as you can.

For my customer, we're going to time box another round of development, make them prioritize the must-haves, and then hopefully go to production, so they can see it they are moving in the right direction. Are you ready for your next step?

Friday, January 30, 2015

10/10/10

There's an interesting decision making technique that I came across in the book Decisive. It's called 10/10/10. The technique was developed by Suzy Welch. She has a book by the same name.

The idea is to think about how you will feel about a decision in 10 minutes, 10 months, and 10 years. The idea being discussed in Decisive is how to avoid short-term emotion when making a decision. Bad decisions, they say, are made while having strong emotions such as anger or greed.

For example, I recently bought a new car, what a lot of people would agree can be an emotional event. Ten minutes after I walked out the door, I'd be excited about the new car and happy with my decision.

In ten months, I may still be thinking about the car I didn't buy and if I would have been happier in that one.

Ten years from now I'll be happy I choose the car that was more reliable over the one that would have been fun, but probably had more problems. If I didn't keep the car ten years, I would have been happy that the car I choose was the one with the higher resale value.

So next time you have a decision to make, think about 10/10/10.

Sunday, December 28, 2014

Better Decision Making

I started reading the book Decisive by Chip & Dan Heath. They have a couple other books I've read, including Switch and Made to Stick, so I thought I'd give this a try.

I'm only about a quarter through the book, but so far, I am enjoying it. It's easy to read and has some good examples to support the ideas. The book is about how to make better decisions. It starts off outlining what they say are the four "villains" to good decision making;

  1. Defining the decision to narrow, not considering enough options
  2. Confirmation bias, we filter out information that doesn't support our position
  3. Focus on short-term emotions and not longer term outcomes
  4. Overconfidence in our ability to predict the future
From here, the book digs deeper into each of these villains and develops strategies to deal with them, starting with the issue of narrow framing. For example, they talk about the "whether or not" type decision. One example was Quaker Oats buying Snapple in 1994. Quaker Oats did buy Snapple and it turned out to be a mistake. The acquisition failed. One study they cited stated that 52% of whether or not decisions that organizations make fail. 

The key is to widen the frame of the decision. Should be buy Snapple or invest the money into internal research or another acquisition instead. Have more to decide on than just "whether or not." 

I'll have more to share on the book as I get through it, but if you're looking for something to read, I'd recommend it so far.