Skip to main content

Tag: Facilitation

The Great Facilitator: Part 3: Commitment-Based Estimation

I want to tie together two concepts I have written about during this series of articles; specifically, how proper facilitation can help a team confidently develop a plan that is realistic and manageable. This is what I call Commitment-Based Estimation. Simply put, Commitment-Based Estimation is an estimation approach that helps a team:

  • Develop estimates they genuinely believe are achievable
  • Feel ownership for their estimates
  • Manage their commitments

Why Commitment-Based Estimation Works

I’ve used the following facilitation exercise to help teams understand some of the flaws with our typical approach to estimation. This activity also demonstrates why Commitment-Based Estimation can lead to much higher-quality results.

I always do this two-part estimation exercise in person and always with a group of people. Important: when you do this with others, be sure to state the following rules:

  1. You cannot ask any questions. Do your best with the information I give you.
  2. Write down your answer. This is important (especially when doing this in groups).
  3. You cannot collaborate or look at your co-worker’s answers.

Here’s how it works:

Choose a shopping mall or large shopping center that is a typical weekend shopping destination for folks near your office. The key is that it shouldn’t be across the street from your office. It should be far enough to require a planned trip to get to. For example, where I work, there is a shopping center called Oakbrook Mall, which is about four miles from my office.

Now here is the first step. I’d like you to estimate personally how long it will take to leave your office, go to the shopping center and find a store that carries designer sunglasses. Then, purchase a pair of glasses with mirrored lenses for your spouse or other family member. Then drive back to your office and drop off the glasses. Oh … and one other thing … On your way back to the office, please pick up an ink cartridge for your inkjet printer.

Now, I challenge everyone to come up with their estimates in about 90 seconds.

The First Readout…

I then go around the room and ask everyone to read exactly what they wrote down as their estimate. It is important they use the exact words! Sixty minutes is not the same as one hour.

If you do this with a group, you will get all different answers. Typically you will get:

  • Someone who is optimistic and estimates a very short time. From the office, they might say around 30 minutes.
  • A few folks will give a pretty precise estimate. For example 53 minutes, or one hour and 12 minutes.
  • Someone who might be swagging it at one hour or “an hour and a half.”

That Was the Setup. So Now You Change the Game…

After everyone has done their readouts, I then say “great job” and explain that I want them to estimate again. However, this time they have something to lose. I pretend that I am giving away an iPad or some other prize to the three folks who provide actual estimates.
So, I want them to redo their estimates. Knowing there is a prize at stake, they now have something to lose!

And Then the Fun Begins…

I now give the group another 90 seconds to redo their estimates.

If you actually created an estimate while reading along, I’d like you to take the opportunity to make it “more accurate.” Pretend you’ll win a real iPad if you create an estimate that you’re confident you can deliver on.

I then go around the room and ask everyone to give both estimates. So again, here are some typical results during the second readout:

  • The person who was optimistic at 30 minutes now says: “My original estimate was 30 minutes and my new estimate is 42 minutes.”
  • The folks with the precise estimates of 53 minutes either stay the same, or they may go up a little to 61 minutes.
  • There’s always someone that will take their estimate and actually lower it. They may go from 80 minutes down to 70. (This baffles me.)
  • And every once in a while someone “pads” their estimate and says “one full day.”

Seriously — The Lessons We Can Learn …

While this may seem like a hokey exercise, let’s look at some very valuable takeaways:

  1. When we give our estimates, do we take them seriously enough? The goal of the entire activity is to realize that if we have something at stake, we will actually estimate differently and come up with an estimate we can confidently deliver on. So when our project teams are estimating, are they approaching this as the first go round? Are they saying, “You want an estimate? 53 minutes.” Or, do they understand there is something at stake … something much more significant than an iPad? If so, they should re-think and verify that they can deliver on their estimate.
  2. Do we assume that an estimate should be as low an estimate as possible, even if it creates risk to delivery? When we estimate, are we so afraid of estimating for real-world contingency and risk that we always estimate optimistically? We probably shouldn’t pad to a full day, but we aren’t asked to make the estimate the “best case scenario” either. It should be an estimate that we all believe is achievable and can be managed too!
  3. Can we estimate effectively without asking questions? When I do this in group, everyone wants to ask questions. Is there construction? What time of day are they going? Do they already know which store has the glasses? But as part of the rules, I say no questions are allowed. When they do this exercise, they can even be frustrated that they are being asked to create an estimate without knowing these answers. They think, “How am I supposed to estimate this”? And this is exactly what happens in real life with our project teams! It is the nature of our world that teams will always have some questions that can be answered and many others that cannot be answered. Yet, we are still asked for estimates that we can plan and execute against.

Commitment-Based Estimating is about helping a team deal with all three of these challenges and develop a plan that is both manageable and achievable.

Don’t forget to leave your comments below.


Bob Zimmerman’s career in custom software development spans more than two decades and has been largely dedicated to the process of leveraging technology to drive innovation and growth. As Geneca’s CTO, Bob Zimmerman continues to build on his work as the driving force behind Getting PredictableS.M., the requirements definition and project best practices that are the foundation of Geneca’s mission to make software development predictable. He continues to extend these best practices to leverage more value for clients and new growth opportunities for Geneca.

The Great Facilitator: Part 2 – Check In and the Chair

In Part 1 of this series, I talked about how facilitation is a key role most of us in the IT world play at some point. I also described the two pitfalls facilitators sometimes fall into: the Presenter vs. the Scribe. Now, I am going to share two basic practices I’ve seen facilitators use to manage a room and deliver effective facilitation sessions. These aren’t the only two recommendations, but I’ve found these practices have helped me personally manage some very strong groups.

First, the Check-in…

One challenge facilitators face is having a single person in the room dominate the discussion. There are two typical causes for this situation:

·         The first possibility is that others perceive the ‘dominator’ as having all the answers. This person has been around twice as long as us. He is also a genius. So rather than the rest of us spending 30 minutes trying to solve the problem, we can just let “Joe” tell us the answer now and finish up the meeting early.

·         The other possible reason for the ‘dominator’ is that the person who is dominating believes no one else has anything to add. They shut down others by interrupting or attacking an idea before it gets a chance to grow.

In either situation, it’s obvious that the room is in dire need of a strong facilitator. Someone who makes everyone feel that their opinion matters and the team can collaborate to achieve their desired goals.

One simple way to get ahead of this curve is a practice I call the “Check-in.” Here’s how it works: At the beginning of the meeting, as the facilitator, you describe your understanding of the overall team objective and the specific goal of the session. For example, the team objective may be planning the company’s summer picnic. The purpose of this particular meeting is to choose a theme for the picnic.

This part is simple enough. But now you need to go around the room and ask everyone to share their specific role related to today’s meeting. Now it gets trickier. Maybe one person was part of the planning committee for previous events and is there to share her experience. Another person from HR is there to help choose the theme and, more importantly, to make sure the theme is appropriate, professional and compatible for special-needs employees. There may be an individual who is there to observe, learn and support the team in activities like coordinating picnic vendors.

Because everyone shares their “role,” as a facilitator, you can clearly ask individuals to speak up. In this way, you prevent a ‘dominator’ from interrupting by explaining that “Jerry from HR” needs to express concerns from an HR perspective.

As the facilitator, you aren’t trying to control the room or shut down any individual. You are simply asking everyone to both play their role and support others in their roles.

Next, the Chair…

This technique is useful when you are facilitating a group of people and standing in front of the room. Maybe you’re at a whiteboard or easel, recording decisions or helping others capture ideas. The idea is that while you’re standing up front, there are usually four to 12 folks in the room.

When I am in this position, I always make sure to have a chair at the front of the room. If I am not physically at a table, I will have a chair just to the side of the whiteboard where I am standing. The purpose of the chair is to allow me to relinquish and regain control of the room.

For example, if there is good discussion around a topic, even if it’s disagreement, I want to encourage this discussion and let the participants feel in control of the room. I will sit down at my chair and really listen to every word.

If things get off-track or out-of-hand, or if the energy gets too low, I will get out of my chair and show my intent to start facilitating. I usually do this by raising a question.

You’re probably thinking, “Bob — are you serious?” While this seems like a very small tactic, if you are trying to lead a group, especially one that you don’t work with often, and need to make sure you are facilitating without confrontation, this is a natural way to control the energy and rhythm of the room.

Don’t forget to leave your comments below!


Bob Zimmerman’s career in custom software development spans more than two decades and has been largely dedicated to the process of leveraging technology to drive innovation and growth. As Geneca’s CTO, Bob Zimmerman continues to build on his work as the driving force behind Getting PredictableS.M., the requirements definition and project best practices that are the foundation of Geneca’s mission to make software development predictable. He continues to extend these best practices to leverage more value for clients and new growth opportunities for Geneca.

 

Facilitation Top 5

As any instructor will tell you, one of the best things about teaching is learning from your students.  It happens in some way, big or small, every time you get in front of people who are expecting to hear how to do it “right.” 

Of course, there is no “right” a lot of the time.  In my classes, for example, I instruct and inform, but I also facilitate discussions about the options, and the students decide what’s going to work for them.

This brings me to the recent Facilitation Skills Workshop class I taught.  In this class, we learn about different facilitation techniques and then the students do the work; they actually facilitate each of the 12 sessions throughout the class.

Maybe you are like many of the students in this class who are terrified of speaking in front of groups. Their hands shake, they sweat, and some have a hard time breathing.  This fear is not unlike other fears and there is often a visceral response.

It is amazing to watch those folks who are terrified of facilitating get up in front of a group and, with some preparation, tools, and guidance, actually help the group accomplish a goal.  It is enormously validating- for them, the participants, and me.

The last session of the 12 sessions is one in which the facilitator brings the class to consensus on the top 5 characteristics of a good facilitator.  My last class came up with the following Top 5 Characteristics of a Good Facilitator:

1.     Neutrality
The facilitator cares that the group achieves their goal in the session, but they don’t care what the results look like specifically.   

2.   Preparedness
A facilitator needs to be prepared for their session. Facilitation might look easy, but it is hard work. Taking time to understand the group and issues, as well as practice the skills and techniques to be used make for a far more effective facilitator and one who will be much more likely to help the group achieve its goals.

3.   Energetic
A facilitator needs to be neutral, but that doesn’t mean they should be comatose.  Bringing some energy to the session helps keep people focused and engaged. 

4.   Clear idea of Purpose/Agenda
A good facilitator needs to start with a clear understanding of the goal of the session and the tools they might use to achieve that goal.  In short, be flexible, but have a plan. 

5.   Positive
An effective facilitator makes the participants want to achieve the session objective.  Even if it’s addressing a problem, a positive tone will encourage participants to own their part of the outcome.

It wasn’t necessarily the list I would have come up with, although those are certainly things we talk about in the class.  As I sat in the back of the room watching them come to this conclusion together as a group, facilitated by one of the students, it was an interesting and, in some way, teachable moment.  For me.

Don’t forget to leave your comments below.


Andrea Brockmeier is the Client Solutions Director for Project Management at Watermark Learning.  Andrea is a PMP® as well as Certified ScrumMaster.  She has 20+ years of experience in project management practice and training. She writes and teaches courses in project management, including PMP® certification, as well as influencing skills. She has long been involved with the PMI® chapter in Minnesota where she was a member of the certification team for over eight years. She has a master’s degree in cultural anthropology and is particularly interested in the impact of social media and new technologies on organizations and projects.

 

 

The Great Facilitator

Part Business Analyst. Part Orchestra Conductor. Part Psychologist. 

Think about what it takes to lead 100 musicians to make beautiful music together.  Or how much sensitivity it takes to understand why people behave the way they do.  While the qualities that separate a great conductor or therapist from a mediocre one may be subtle, the outcomes are obvious. The same holds true for facilitators.

Do you think of yourself as an effective facilitator but unsure how others perceive you?

Maybe you’ve been at a meeting recently where the facilitator is doing a fantastic job but you just can’t figure out exactly she is doing differently.

The differences are subtle.  This series is about those subtleties that separate the great facilitators from the mediocre ones. 

Part 1:  Scribe vs. Presenter:

Whether we like it or now, somewhere along the line we all play the role of a facilitator. How do we make sure we don’t make one of the most common and damaging facilitator blunders: Pushing our own agenda.

In the IT world, we all play the role of a facilitator.  Technical architects facilitate sessions for estimating and creating designs for their teams.  Project managers facilitate team and client meetings and make sure the team is on track to reach its goals. When Business Analysts collect requirements, they may facilitate large requirement meetings.  With so many kinds of facilitation roles, can we assume we know what being a facilitator really means? Do we, as facilitators, recognize that this is a significant role we need to work at in order to be effective?  And, most importantly, how do we make sure we stay “within” our role as a neutral facilitator and not push our own agenda?

So you think to yourself, “Yes, this is obvious. Of course I am an effective facilitator.” But let’s test ourselves to find out how effective we really are. 

The Two Extremes of Ineffective Facilitation

When I’ve been a less-than-effective facilitator, I’m usually acting in one of two extremes. I either go into “Presenter” mode or into “Scribe” mode.  Let me demonstrate these two extremes.

First, the “Presenter”.  Although their role is to facilitate a discussion (e.g. illicit requirements from business users or help a team arrive at estimates), “Presenters” actually come to the meeting with an opinion, specifically, a desired outcome. They are there to help others meet his or her agenda, rather than facilitate the room to develop its own opinions.  When a facilitator starts presenting, he or she does not allow others in the room  to collaborate towards finding their own solutions.  This shuts down the energy in the room. This also means the participants may not “own” the solution.

At the other extreme, a facilitator goes into “scribe” mode. When a facilitator is in scribe mode, it means that when he or she walks into the meeting, they sit and take notes or  meeting-minutes but do not influence the dialogue.  This approach makes it easier for  others in the meeting to go off-topic and start discussing points not related to the objective of the meeting. Also, if someone is “checked-out” or “shut down”, there is no true facilitator in the room to make sure their voice is heard.

What Makes a Great Facilitator?

While most facilitators bring their own approaches to a session, the best facilitators allow  the solution to be defined and owned by the individuals they are facilitating. She has the tact and skill to:

  • Help the team clarify and align on their objective. Then, facilitate by making progress towards the objective.
  • Help keep the group’s energy high so everyone contributes, is engaged and feels heard.
  • Keep momentum or rhythm flowing towards the objective. (Although they can help the team change direction if the team believes it is required.)   Staying on track can be tricky since the facilitator needs to balance discussion on side topics that are helpful to the objective vs. topics that derail the goal. 

What About You .. Presenter? Scribe? Not sure?

Even if we believe we are doing an effective job at facilitating, we may actually be playing a Presenter or even Scribe.  Here are some ways we can test our effectiveness:

  • Are you directing conversations with your own agenda? Or, are you enabling the team to have its own conversations?
  • Are you making sure the team stays on topic and on track to meet its objectives?
  • Are you making sure everyone in the room is being heard? Is anyone’s  idea’s being  shut down? (This can affect the energy of the room.)
  • Did you leave your opinion at the door? A good facilitator helps get to a solution, not give a solution.
  • If you had not attended the meeting, would the team have accomplished the same result? (Maybe you are not being as affective as you think you are.)

When It Comes Together…

Simon Sinek recently shared the following quote:  “Don’t show up to prove; Show up to improve”.

When great facilitators lead meetings, they enable a dialogue that allows the room to make a decision. They do not abuse their role to force an outcome. Instead, they help everyone do a better job and accomplish fulfilling work. The room fills with energy and momentum that can’t avoid delivering results. When meetings feel this energy, you know you are leading the room as a great facilitator.

Be sure to watch for the rest of the series in upcoming articles:

Part 2 – Check in and the Chair:  Why can some facilitators effortlessly lead their team to achieve brilliant clarity and enthusiastic alignment? This article includes some basic practices great facilitators use to manage a room and deliver impressive results.

Part 3 – Commitment Based Estimation: In order for an estimate to have teeth, the team must feel ownership of the process and genuinely believe the estimates are achievable. This article includes exercises to facilitate estimates that are realistic and manageable. 

Part 4 – What Great Facilitators Know about Estimating: While estimation sessions can be tricky to facilitate, a great facilitator can make their teams super confident about their estimates. This article includes some ideas on overcoming the subtle challenges that can undermine the estimation process.

Don’t forget to leave your comments below.


Bob Zimmerman is the Vice President & CTO at Geneca. His career in custom software development spans more than two decades and has been largely dedicated to the process of leveraging technology to drive innovation and growth.

As Geneca’s CTO, Bob Zimmerman is the driving force behind Getting PredictableS.M., the requirements definition best practices that are the foundation of Geneca’s mission to make software development predictable.

An Inquiry, Not an Inquisition

Sept27thFEATRURE

The Business Analyst as Explorer, Part 1 of 6 by Karl Wiegers

Many years ago, my manager, Jerry, sat in on a discussion I had with a customer named Steve to explore his requirements for a new application. After the meeting, Jerry pointed out that I had been rather aggressive in my questioning of Steve. He was right. I hadn’t realized how hard I’d been pressing Steve to make up his mind on certain points and tell me exactly what he wanted. Fortunately, when I contacted Steve to apologize, it was clear that he wasn’t offended. Nonetheless, our discussion probably felt like an inquisition to Steve, rather than an inquiry into what he was asking us to build. Not the best strategy for a business analyst to take.

Another extreme approach to requirements elicitation is for the BA simply to record whatever the customer says and pass that information on to the developers. This doesn’t work very well, either. As with most things in life, the appropriate behavior lies in between the possible extremes.

Requirements elicitation is a process of exploration and discovery, not just collection (which is why I don’t talk about “gathering requirements”), and the BA is the guide. BAs need to recognize that customers won’t be able to present all their requirements in a single workshop or discussion. They probably don’t even know what their real requirements are yet. Elicitation requires multiple cycles of refinement, clarification, and adjustment as the participants move back and forth between high-level concepts and specific details.

But First, Some Questions to Avoid

The worst question you can ask during a requirements discussion is “What do you want?” The second-worst question is “What are your requirements?” No one knows quite how to answer these questions. Customers and other elicitation participants might not share the BA’s understanding of what the word “requirement” even means. When customers attempt to answer these questions in good faith, they typically generate a large number of random—yet important—thoughts.

I’ve observed this in some of my training classes, in which small groups of students conduct a practice requirements elicitation workshop on a sample project called the Cafeteria Ordering System. The groups are trying to learn how to employ use cases to explore user requirements. One member of each group plays the role of a user who would employ this system to order meals. Some groups begin by asking this student, “What do you want?” because this is how they’re accustomed to launching requirements discussions. They typically get responses such as:

  • I need to be able to pay by either credit card or payroll deduction.
  • I want to be able to order group meals for lunch meetings.
  • The system has to be available from home as well as from work.
  • I’ll have to submit delivery instructions for my meals.
  • I shouldn’t have to pay any delivery charges.
  • Can contractors order meals or just employees?
  • I want to be able to order meals at least a week in advance.
  • It would be nice if I could easily reorder the same meal I ordered sometime in the past.
  • Could I get nutrition information for a whole meal?

 

These are unquestionably important thoughts and ideas. However, when asked “What do you want?” the workshop participants tend to spew out these thoughts in a random sequence with no organizing structure. This makes it hard for both the BA and the customers to know what the information means, what to do with it, where to store it, and what to discuss next. The student groups who take this approach invariably flounder in the sea of random input. In contrast, those groups that grasp the use case approach early on make much faster progress. An important BA skill is to structure the dialogue and ask questions that will guide elicitation participants through progressive layers of refinement in an organized fashion.

 

The BA should remember his role as a neutral facilitator. We all filter what we hear through our own biases, preferences, experiences, and hot button issues. Avoid asking leading questions that steer customers to agree with your own intentions. Also avoid overruling a customer’s idea just because it doesn’t agree with your own point of view. I once observed a 60-participant “voice-of-the-customer” workshop that one of my consulting clients conducted to explore requirements for a major new product. The workshop facilitator was the senior manager responsible for the product. He had strong opinions about the project’s direction and didn’t hesitate to steer the discussion toward his predetermined outcomes. This is discouraging for participants, who will feel that they’re wasting their time if the facilitator already knows what the answers will be.

In the next installment in this series, I’ll explore some questions that are helpful for eliciting business requirements. These requirements define the organization’s business objectives for undertaking the project, define the product vision, and enable scope definition and management.

This series of articles describes some questions a BA might consider asking during elicitation discussions—as well as some to avoid. The articles are adapted from my book More about Software Requirements: Thorny Issues and Practical Advice (Microsoft Press, 2006). A classic resource of good questions for discussing requirements for any type of project is Exploring Requirements: Quality Before Design by Donald Gause and Gerald Weinberg (Dorset House, 1989). Roxanne Miller also suggests hundreds of questions to help the BA with requirements elicitation in her book The Quest for Software Requirements (MavenMark Books, 2009).

Don’t forget to leave your comments below.


Karl Wiegers is Principal Consultant at Process Impact, www.ProcessImpact.com. His interests include requirements engineering, project management, peer reviews, and process improvement. His most recent book is a memoir of life lessons titled Pearls from Sand: How Small Encounters Lead to Powerful Lessons.