February 4, 2012

BigVisible Blog

Three Simple Tools for New Teams

When I am delivering Certified ScrumMaster (CSM) classes or starting up new agile teams, I share three simple tools that really help collaboration: creating a working agreement (also called team agreement), the art of the possible, and the fist of five. Based on feedback, these three items are often some of the important tools that team members take back and use immediately. Below is a simple way to introduce these by facilitating creating working agreements with your agile team.

Photo by Greencolander via Flickr.

Before you kick off your new agile team, get the team together and let them know the goal is to come up with some team agreements so that we all agree on how we’re going to work together. You might have some ideas, but first go around and hear others first. If you’re in a large group, pair up, otherwise each person can individually write down one statement about how their time together should be – everything from working hours to working conditions. Now collect these and put them on the wall, under the title “Working Agreements.” For general work, I often hear: take personal calls out of the working area, headphones on for music, keep your chat program on, put a flag or sign up if you don’t want to be interrupted (for less than an hour), shower regularly (seriously), no eating fish at your desk (yep, that too). Some common ones for meetings that I’d recommend are: one conversation at a time, start and end on time, electronics by exception (that is, no cell phones or computers unless it’s an emergency and everyone understands that), and have an attitude of the art of the possible.

The art of the possible means keeping an open mind that something covered here could work or might be true, even if you disagree, instead of an attitude of “that could never work here” (even if that is your experience). There’s always a first time, and the difference of our attitude, effort and approach differ vastly when something “just might be” possible, rather than impossible. MacGyver believed in the art of the possible.

Now that we have everyone’s recommendations, decide on what the final working agreement list will be. My preferred way of collaborating on quick yes/no group decisions is with the technique called the “Fist of Five.” When you’re in a group deciding on something (such as where to go to lunch that day), you can simply say the recommendation and then have everyone hold up one to five fingers. The number of fingers represent where they stand: 5 means they love the idea, 4 means they like the idea, 3 means they’re not that happy but they won’t get in the way, 2 means they have some questions or concerns that if answered they’ll get on-board, and 1 means “No way, ever, never!” (and make sure the one finger is the index finger…) Fist of five is a great way to hear everyone’s voice and quickly see who’s not in agreement and why (and then work to get them in agreement).
I hope these tools help your team get off to a great start.

A Map of Organizational Agility

Invariably, when presenting or teaching about applying Agile principles in organizations, someone always asks me, “are there places where you can’t be Agile?” or  ”how do you decide whether or not you want to be Agile?”. These questions trouble me, as it seems like we’re offering a false binary choice. Either you are “Agile” or you aren’t. This perspective fails to communicate the nuance that, when considering an organization, there is a spectrum of Agility and the question really becomes, “how Agile can we make our organization?” [Read more...]

Avoiding Pitfalls of Agile Incorporation: Free Webinar Event

Putting agile principles into practice can take a lot of work. In order to realize the benefits of increased productivity and responsiveness characteristic of effective agile organizations, teams must be trained, new tools and infrastructure acquired, and broader areas considered.

Join BigVisible’s Brian Bozzuto and AccuRev’s Chris Lucca on Thursday, November 17th from 1:00-2:00pm for a free lunchtime webinar on Incorporating Agile Methods: Top Traps for Development Teams to Avoid.

In this session, BigVisible’s Brian Bozzuto and AccuRev’s Chris Lucca will explore several dimensions of moving to agile practices and how they can magnify the benefits possible with agile or ultimately undermine the agile adoption –depending on how they are managed.

Specifically, this webinar will explore:

  • Common hurdles a team adopting agile may experience
  • Team training needs to consider, including agile certifications like Certified ScrumMaster and Certified Scrum Product Owner
  • Criteria for evaluating or selecting agile development tools to enable agile methods
  • How Agile impacts a broader scope, such as compensation, evaluations, finance, and sales

Reserve your space today!

The Journey from Analyst to Product Owner

I owe a special thanks to my colleague Jason Novack for pairing with me recently on a presentation to the Boston International Institute of Business Analysts (IIBA) about making the leap from business analyst to a product owner. It was a great experience that really got me thinking about some of the journeys I’ve seen analysts go through as they moved into Agile teams and began playing the role of Product Owner. This blog encapsulates some of the concepts we came up with in that discussion and the archetypes I’ve seen for behaviors that these people go through, specifically analysts from large organizations that find themselves dropped into the role of product owner.

[Read more...]

Extreme Stand-ups: The Cocktail Minute

a black-and-white, from the 50s, of folks dressed in business attire, apparently at a cocktail partyI’ve been lucky enough to be coaching a rather open-minded team who’s getting on in their journey of “going Agile.”  By most accounts, the team has been thriving: self-selecting prioritized work, organizing around it, taking pride in improved flow and reduced waste.  For the most part, they have been genuinely experiencing the joy of working in an iterative, collaborative and open way… except for one glaring exception: their daily stand-ups.

“Painful.”  ”Boring.”  ”A waste of time.”  What should be the frosting on their morning flakes was leaving the team feeling soggy and needing another cup of coffee.  A 15-minute jazz of collective focus had become a dreary 30 minute-long plodding through the task board.  No good.

Part of their challenge is that this agile team tackles a variety of flavors of work.  Many the work items are pure analysis: another team in the enterprise wanting to make a change and asking for a spot-check on the impact to this central system.  A good number are enhancements: a new column on a report for this line of business; a new field on that form for another…  There’s a real dispersion to the work.  It’s clear that some percentage of the work being done in this group does not need the undivided attention of the entire crew.  Discuss this mix of work in the traditional stand-up format, there’s a lot of noise to the signal and people begin to tune-out.

In these kinds of situations, I sometimes suggest I like to call “The Cocktail Minute.”  Here’s a typical scene (names have been changed to respect the privacy of the talented):
[Read more...]

One Week Down, Two Weeks Behind

“Hey, man! One week down, two weeks behind…” -Kirk Lazarous, Tropic Thunder (2008)

While not a terribly serious movie, I have always enjoyed this quote from the comedy movie about the ill fated making of a war movie. The concept of being only one week into a project, and yet somehow already two weeks behind seems so absurd as to be impossible, and yet it has been the reality for a lot of projects encountered. Invariably, ambitions around projects can get so high, with so many stakeholders that our definition of success rapidly becomes so great we watch the possibility of completing our project recede into the horizon. Properly defining and then managing project success is a critical activity in any project. There are a number of excellent resources I’ve drawn upon over the years to do this. This blog post is more a compilation of my thinking on this topic threading through some of these techniques. [Read more...]

The Math Behind Agile and Automation

Every once in a while, we encounter individuals on our teams who have a healthy dose of skepticism about these new Agile practices they are learning. For those who tend to be scientifically-minded, or need more evidence than just a good story, I have found that it is important to give them real data to look at.

As an example, it is interesting to combine the usual Cost per Defect curve for a software project with a histogram that maps the probability or frequency of finding defects to the corresponding project phase. The result is mathematical support for both Agile as well as the value of Automation and good Agile QA practices.

Figure A below shows the typical Cost curve for a waterfall project (source: The Economics of Testing, Rice Consulting) along with an overlay showing the probability of finding defects in various phases of the project.
[Read more...]