May 20, 2013

All Posts By: Skip Angel

Agile Coaching Blog

Skip Angel

About Skip Angel

A Certified Scrum Trainer (CST) and Certified Scrum Coach (CSC), Skip has solid experience in consulting, IT staff and product development environments over the last 20+ years, with an exposure to several industries in an technical capacity including retail, healthcare, financial and automotive. He has been involved in managing, developing and supporting the best practices relating to the product development lifecycle through modeling of known software development methodologies including agile, waterfall and iterative.

Agile Coaching Is (All) About People

“You’ve not only made things better, you have truly changed our lives.”

These are the words that every agile coach yearns to hear from the people they work with. While it’s always a goal of mine to change the mindsets of clients, I have had mixed results over my five years as an agile coach. On one six-month engagement with a client I’ll call Prosperity, though, something transformative took place. I’ve spent some time since then thinking about what made those six months so successful and why Prosperity continues to push the envelope of what it is capable of doing as an organization.

Agile Coaching: What Makes It Better With Some Clients?

At first, I thought it was all around the process. Prosperity, like many other clients, started out wanting to “learn agile.” [Read more...]

Share:

Agile Delivery: From ScrumMaster to Team Coach

Several weeks ago, one of my colleagues at BigVisible brought up an interesting concern around agile delivery and the ScrumMaster. How is, he asked, that there are so many ScrumMasters out there who are unprepared for their role on a team?

Agile Delivery Team Coach ScrumMaster

As I thought about it, I realized that the two-day CSM course basically introduces new ScrumMasters, team members, and other interested parties to how Scrum works and how to move teams through the ceremonies and artifacts associated with Scrum. What it doesn’t do—and likely cannot do in just two days—is also focus on all of the things ScrumMasters have to do to foster truly high-performing teams. The ScrumMaster role, done right, is much more than just scheduling meetings and updating a burndown chart. That leads me to conclude that the name ScrumMaster should (or will) die and be replaced with one that reflects the truly comprehensive nature of the role: team coach. Here’s why: [Read more...]

Share:

Agile Accountability

This was a great week at BVCon, our bi-annual company gathering where we build relationships, show experiences, and learn from each other. These events are core to our values and success, as it brings our virtual company together not only physically but also emotionally. While I have always enjoyed and treasure this time together, in past events I have felt something was missing. While we would have awesome discussions and a fun time, little would happen after the events. We would essentially go back to our real world with our clients and continue with our lives as coaches. Sure, we would come back refreshed and energized, but there were few tangible results that we could take back and use.

Is Agile Accountability an Oxymoron?

This year’s theme was around accountability, a topic that is difficult for leaders to talk about, especially those that have embraced agile principles. Why? Because many leaders believe that accountability resembles command-and-control leadership. A manager tells you to be accountable, instead of allowing you to be empowered and self-organize with the rest of your team. I have heard some say in the agile world that management is not needed for true accountability; instead, the team members should hold each other accountable for their success.

BigVisible & Agile Accountability

For a long time, the only goal our BigVisible leadership team gave us was to “be awesome.” They felt that to be more specific might put structure or constraints in place that would be stifling. As coaches, we felt great to have complete power over our destiny. No rules, no guidelines, just do your best and help our clients. Should be enough, right?   [Read more...]

Share:

The Flywheel of Organizational Agility: Enablement Teams

The Challenge

When I ask people if agile principles and methods have helped their teams with delivery and execution, most of them are quick to acknowledge that they have. These same people, however, often go on to describe the challenges they’ve faced in scaling agile or in their enterprise transformation. They share various organizational impediments that slow teams down and stand in the way of true, lasting change. In response, I ask the following question, “Do you have a team across the organization that is focused on addressing these challenges?” Most of the time the answer is ‘No’ — in fact, most people seem surprised by the very concept. Yet enablement teams could be the most important component for sustained success and true organizational agility.

The Flywheel Effect

In one of my favorite business books, Good to Great1, author Jim Collins talks about the slow, steady nature of lasting change by comparing it to an egg. He says that when chicken hatches, it appears to happen instantaneously. Yet in reality it is the culminating event of a long-term effort:

While the outside world was ignoring this seemingly dormant egg, the chicken within was evolving, growing, developing&emdash;changing. From the chicken’s point of view, the moment of breakthrough, of cracking the egg, was simply one more step in a long chain of steps that had led to that moment. Granted, it was a big step—but it was hardly the radical transformation that it looked like from the outside.

Collins goes on to say that creating this kind of breakthrough within the confines of a large company is akin to moving an enormous flywheel, “a massive, metal disk mounted horizontally on an axle. It’s about 100 feet in diameter, 10 feet thick, and it weighs about 25 tons.”

Image: Flywheel from an old factory by Rajesh Dhawan on wikimedia commons.

Your job, Collins writes, is to generate enough momentum to get that flywheel moving as fast possible. To move something that huge, however, will require tremendous effort. And even as you push as hard as you can, you are unlikely to see a great deal of movement at first. But if you keep pushing steadily, little by little, the wheel will begin to turn, faster and faster, until “at some point, you can’t say exactly when—you break through. The momentum of the heavy wheel kicks in your favor. It spins faster and faster, with its own weight propelling it. You aren’t pushing any harder, but the flywheel is accelerating, its momentum building, its speed increasing. This is the Flywheel Effect. It’s what it feels like when you’re inside a company that makes the transition from good to great.”

Establishing a Guiding Coalition

So how can you get the flywheel that is your company to really start moving and gaining momentum? [Read more...]

Share:

The Value (and Curse) of Velocity

Take a look at a recent article I wrote in Projects@Work (login is needed but it is free registration).  In this article, I talk about the misconceptions around velocity and how it should be used with teams. Velocity can be used for bad and good, find out what it takes to apply it effectively.

Article: Value of Velocity

Share:

Effective Daily Meetings

This entry is the first in a series  drawing upon some of the practical experience of BigVisible coaches in the field. In support of consultants, individual coaches may bring forward questions and challenges they face. We have edited and distilled one or more conversations on a topic into a format outlining a specific challenge, concrete recommendations, and lessons learned from the discussion. We hope you enjoy, and would welcome feedback on this particular challenge, as well as requests for future topics.

Objective:

The Daily Scrum (or daily standup meeting) is a critical meeting for teams to get together and do their daily planning and tracking of work. This meeting is a checkpoint that the team is working together to achieve the goals of each Sprint.  They do this by determining their current progress and identifying anything that is impeding the ability to achieve those goals.

Challenge:

However, it is a challenge to many teams to do this in a shorter meeting.  Scrum recommends that this meeting is no longer than 15 minutes.  Some teams focus on meeting the time but don’t come out of the meeting with a joint understanding of the team’s plan for the day.  Other teams find the meeting valuable but taking much longer to discuss, sometimes taking up to an hour each day for the meeting.  Eventually, the team will start to complain that “Scrum has too many meetings” and is keeping them from accomplishing the work in the Sprint.  We don’t want the Daily Scrum to become THE impediment!   [Read more...]

Share:

Executive Patterns: Becoming a Catalyst for Change

In our last newsletter, we conducted a poll asking the following question: “How much executive support do you get for your Agile initiative?” The results were encouraging, as 36% believed they were getting all the support they needed. The remaining 64% had some support, but could use more. Everyone that participated in the poll indicated that there was at least some involvement by their executives. As a coach having supported the adoption of Agile across several organizations, I usually see one of the following patterns when it comes to executive involvement. [Read more...]

Share: