Using Kanban to run your start-up aka Stephen Covey was the first Agile Coach
Honolulu has a thriving startup community. I decided to present on this topic after attending the kickoff of the extremely popular start-up event, Honolulu Startup Weekend. While listening to the pitches, I realized that these potential new companies were ripe for some Agile basics. Many of them were already very familiar with Lean Startup and customer driven business development, but very few were familiar with the Agile techniques designed to manage day-to-day projects or business.
I like to consider Stephen Covey as the first true Agile coach. His 7 Habits of Highly Effective People addressed key effectiveness techniques that align nicely with Agile. My favorite one is First things First, "To live a more balanced existence, you have to recognize that not doing everything that comes along is okay. There's no need to overextend yourself. All it takes is realizing that it's all right to say no when necessary and then focus on your highest priorities." This is perfectly aligned with the Agile Manifesto principle, "Our highest priority is to satisfy the customer through early and continuous delivery of valuable software."
One of the techniques he uses for First Things First is to get people to understand the difference between urgent versus important work. He wasn't the first to make this distinction, Dwight D. Eisenhower is credited with this quote: "What is important is seldom urgent, and what is urgent is seldom important." What Covey is responsible for is the creation of the following time management matrix to help people distinguish where they are spending their time:
- Quadrant 1 is for important activities you could not have foreseen, and others that you left until it was almost too late. Plan for these.
- Quadrant 2 is for important activities that help you achieve your personal and professional goals, and complete important work. Focus here.
- Quadrant 3 is for time-sensitive distractions. They are not really important, but someone wants it now. Learn to say no.
- Quadrant 4 is for activities that are just a distraction. Avoid them if possible.
The intent of this matrix is to get people to focus on daily activities and plan their time within Quadrant 2. At the time of publication (1989), the most common technique for managing your time spent on important activities was to capture them in your calendar book. This was before phone apps or even the use of Outlook calendars. They were documented in those heavy DayTimers calendars that people carried everywhere. Covey's training courses suggested that you block time in your calendar to focus on important tasks and limit the time you spend on urgent tasks.
This fits nicely with Agile prioritization approaches and managing WIP. For the purpose of the audience last night, small business owners, I compared this approach of managing your important work in your calendar to the Kanban concept of prioritization using of classes of service and managing work in progress (WIP). I personally use this approach to manage my business every day. I have an online Kanban board (LeanKit) with swim lanes of important activities and I have WIP limit of a minimum of 6 hours of important work each day. I assume that at least 2 hours of my day will be taken up with unplanned urgent activities. I also use the Kanban Board to capture a backlog of ideas that may eventually become actual work. Here is an example of my business-oriented Kanban board:
For those of you familiar with Agile techniques, it is easy to see how these techniques can be applied to many different situations other than software project management. I also believe that there are very few new ideas in Agile since these effective management techniques have been around for many decades and are just now being embraced within traditional project management. If Stephen Covey was a software developer, he would have made a great Agile coach.
About the author, Dan Tousignant
Dan is a lifelong project manager and trainer with extensive experience in managing Agile software development projects. Though the role of the professional project manager is changing dramatically through these approaches, Dan coaches organizations on how to transition teams and organizations to Agile.
Dan has over 20 years of experience providing world class project management for strategic projects, direct P& L experience managing up to 50 million dollar software development project budgets, experience managing multi-million dollar outsourced software development efforts and strong, demonstrated, results-driven leadership skills including ability to communicate a clear vision, build strong teams, and drive necessary change within organizations.
Dan holds a Bachelor of Science majoring in Industrial Engineering from the University of Massachusetts, Amherst and is a Certified Project Management Professional, Professional Scrum Master, PMI Agile Certified Practitioner and Certified Scrum Professional.
Dan Tousignant, President
Cape Project Management, Inc.