Category archive

Agile - page 3

Words Mean Things – Efficient and Effective

in Agile/Product Management/Project Management by
[mks_pullquote align=”left” width=”300″ size=”24″ bg_color=”#117788″ txt_color=”#ffffff”]Efficiency is doing things right.
Effectiveness is doing the right things.
– Peter Drucker[/mks_pullquote]As we continue to explore words and their impact on conversations and behaviors, I would be remiss if I didn’t bring up a common set of words that generally makes me twitchy if one is emphasized more than the other — the words are Efficient and Effective. Let’s first look at the definitions of both:

effective. a. Successful in producing a desired or intended result.

efficient. a. (esp. of a system or machine) Achieving maximum productivity with minimum wasted effort or expense. (of a person) Working in a well-organized and competent way.

A lot of people talk about and use both these words — in fact, with some folks, these words are their Drinking Game words (every time they say it, you drink). If your role focuses more around management then you probably guilty of using the word “efficient” quite a bit. If your role is focused more around product quality or release management, then you probably say “effective” throughout the day. If what you do or build is largely commoditized or well established, you may tend to focus on how efficiently things get done. If what you produce is suffering in the market (either a lot of support or lack of sales), the word you probably talk about a lot more is effectiveness.

In all these cases, the context of the person or the product dictates our focus on either efficiency or effectiveness. This seems fairly harmless, but problems creep in when we might focus on one thing more than the other. If we focus to much on achieving maximum productivity, we may tend to miss key details and or skirt over a key step that insured quality. If we focus solely on effectiveness, we may see over engineering, gold plating, and an opportunity pass us by.

I’ve read several blogs lately about having efficient daily stand ups or retrospectives or planning meetings, with just a few words mentioning ensuring effectiveness. Since these meetings are about creating a team and continuously improving, effectiveness should be a key part if not the primary part of the discussion. In these situations, you could argue that efficiency would help drive effectiveness. For example, sticking to the 15 minute rule around stand-ups is meant to be a time boundary to help team members to ensure their effectiveness of their message.

EffectiveEfficientAgile and Lean principles have elements of both effective (focus on delivering value) and efficiency (while minimizing waste). If you are an efficiency junky, don’t forget effectiveness. And if you tend to be an effectiveness aficionado, don’t forget that in today’s market landscape — things have to be done efficiently. Both of these words should be used together and when we have a discussion about doing something better, we should understand how the improvement impacts effectiveness and efficiency. I quoted Peter Drucker at the beginning of this post, and it’s appropriate since his writings, specifically his book The Effective Executive has long shaped this Effective vs. Efficient model and thinking. The model shows that without effectiveness, efficiency doesn’t matter. That being said, the time window for effectiveness has gotten smaller due to competition and more demanding consumers — meaning, in his model you may not survive long.

So the next time we are innovating around our process, let’s be sure the conversation includes doing things effectively while while keeping efficiency in mind.

Twelve Awesome Interactive Facilitation Techniques for Agile Teams

in Agile/Agile Engineering/Product Management/Project Management by

If you work with a team, and possibly, you are the Scrum Master or Lead or Product Owner, or just a Team Member trying to guide a conversation — then these interactive facilitation techniques are for you. But before we move on, let’s first get it out there that we may call these “Interactive Facilitation Techniques”, but they are really games. More specifically, games that help us at work. Using games — I mean interactive facilitation techniques — help us to effectively and easily facilitate discussions. Using these games to helps to drive good team behaviors (Blunt 1993) including cooperation, clarifying, inspiring, risk taking, harmonizing, and process checking. All the while, helping to overcome the destructive team behaviors of dominating, rushing, withdrawing, digressing, discounting, and blocking. That all being said, let’s get to it. The following list of games are those that I’ve personally used with teams that I see work really well and are easy to adapt. I’ve taken the liberty to group them by the team meetings where they make the most sense; however, as I previously said — they are easy to adapt and can be used for almost any activity.

General Brainstorming

Affinity Mapping – An oldie, but a goodie — this great way to collect, organize, and rationalize ideas — even large amounts of ideas. I’ve used this to help understand the objectives of meeting attendees and get everyone on the some page. Here’s a great a time-lapse video of a team using Affinity mapping to sort 500 pieces of customer feedback…

Dot Voting – Dot voting is a simple way to get a group of people to form consensus. This technique let’s everyone have a voice and it’s a quick and easy way to rank things. By the way, here’s a cool and FREE tool to do this with distributed teams …

Pre-mortem – First off, let’s remember that words mean things and mortem is related to death. So I equate doing a pre-mortem to death planning including making your bucket list, understanding what things you should do to be health, and things to do to stay safe. The pre-mortem is a great risk management technique.


Product BoxProduct Box – Also known as Vision Box, this is a great way to discover what customers think, a way to uncover expectations, and ultimately share – or gain a shared understanding of the product or project or release. I find the product box to be a great exercise for Release Planning and project chartering.

My Worst Nightmare – This is a great way to get into heads of the team and learn from their experiences, anxieties, and expectations. An easy way to express yourself, you use pictures. They say a picture is worth a thousand words and it’s true. I use this exercise to prime the pump on understanding objectives.

Spider Web – Another game from Innovation Games, Spider Web is a form of context diagramming, but it’s no the run-of-the-mill context diagramming. First, everyone get’s to draw, second — use pictures, and finally, no rules — lines can go from one item to another. You’ll find this a great game to understand information flows between people, systems, and organizations.


Staple Yourself to Something – Have you ever found that getting started is the hardest thing to do? Well, this is the perfect game for you. This game involves mapping out processes, it helps to quickly get everyone on the same page as to how something should work. It helps with knowledge exchange, establishing process flow, and establishing a shared understanding.

Empathy Mapping – Establishing personas is a key activity at helping to understand our customers or the users of the systems we are building. This technique is a fast-and-easy way to do understand our users as a team. Even if you already understand your personas, let the team do this exercise and see what they discover.

Buy a Feature – Have you’ve ever been frustrated with stakeholders not being able to make prioritization decisions? Buy a Feature is an awesome way to help drive the discussions around prioritization. You may not land on the final ranking, but you will gain some awesome insight into what is important and where people are willing to negotiate.

White Elephant Sizing – This is the only way to estimate stories. Okay, not the only way, but it’s a good way. This game is a spin on the White Elephant gift exchange we do after the holidays. The values of this game are conversations and shared experiences of all the players. If you want to find a fast way to estimate, try this.


SailboatSailboat and 4Ls – I’ve talked about both of these games before, and I play them regularly to help evaluate coaching sessions. I encourage folks to mix it up all the time with regards to retrospectives, and these two games are great ways to do it.

Learning Matrix – This one is from Diana Larson and Esther Derby’s Agile Retrospectives book. What I really like about it is that you find things to improve upon based on looking at what you are doing right. You review where things are going well and look at how applying what you are doing well to this things that are going wrong.

Check out the AgileBacon links page for sites that are all about Games that Work.

If Your Title Rhymes with “leaf”, “erector”, or “resident” – You Should Learn About Agile and Lean

in Agile/Project Management by

If you are reading this blog, then you are either part of an Agile transformation or you are someone considering an agile transformation. If you are someone that works in a management or simply a position of authority at your organization, if you don’t know much about Agile or Lean except that they are the latest buzzwords that don’t seem to go away — well, you should learn more about them. Because, the words might change a little, but the practices and principles have been around for a while and they are not going to go away anytime soon.

Agile and Lean are a set of ideas and principles that shape principles which guide our behaviors and foster the frameworks by which teams use to get things done. These have come about because there’s a recognition that trying to build things that are a result of complex cognitive thinking cannot be done well and in a timely manner to keep up with the demands of consumers. Couple these demands with an exponentially growing and aggressive competitive marketplace — the concepts of focusing on building the right thing and eliminating the waste that keeps us from delivering things right have naturally emerged. Agile and Lean are not old ideas, there’s been a ton of learning and shaping of these ideas and principles. New frameworks and or practices emerge daily as our products evolve and the people creating them do the same.

Why Should You Learn Agile and Lean?

clone_dollyHave you ever said, “Dolly is a great leader and worker, I wish we could just clone her and have ten Dolly’s.”

Or, how about, “I wish our team would just make a decision and get it done.”

Well, Agile and Lean values promote:
[list][list_item icon=”fa-star”]Empowerment[/list_item][list_item icon=”fa-star”]Trust[/list_item][list_item icon=”fa-star”]Commitment[/list_item][list_item icon=”fa-star”]Quality[/list_item][list_item icon=”fa-star”]Value[/list_item][list_item icon=”fa-star”]Team Work[/list_item][list_item icon=”fa-star”]Transparency[/list_item][/list] All of these things involve, giving teams information and the vision, and then getting out of the way to let them deliver.

Another thing to note about the values above are that they are generally practiced by all organizations and you’ll find aspects of each word above within the corporate mission statements. By learning more about Agile and Lean, you can learn how to help your teams or leadership leverage the organizations’ values and adapt those advocated throughout Agile and Lean adoptions.

The predominant reason organizations and teams adopt agile is to respond better to change — that is market changes. The other reasons are productivity and quality, all things that help us make products people want to buy, at the price they are willing to pay, and ultimately with the right level of quality that help mitigate long-term cost of supporting. A byproduct of agile adoptions is improved morale.

How You Learning Agile and Lean Can Help

cycle, loop or feedback conceptAgile and Lean advocates shrinking the feedback loops which improve communications amongst departments and ultimately help your employees make better decisions. Well, you understanding when the feedback loops happen, your role in the feedback loops, and the types of information shared at the different levels of the organization can help you keep yourself out of the way from the team. What I mean by this is that when sometimes things are going right, we’ll go back to what we are comfortable with and understand — and generally this means metrics and reports that may be costly to gather and result in anti-patterns for good team work.

The other value of you learning about Agile and Lean is that you can help facilitate the adoption by being a good leader and facilitating change practices. Keeping a level head when things aren’t going right, and providing guidance as to how best support the teams.

What Should You Do to Learn?

There’s a ton of reading materials out there. Just keep in mind that there’s a lot of books, articles, and blogs that focus on the practices and not as much on the strategic and scaling aspects around agile. This spaces is growing as organizations have realized that not only is there the “build better software” value, but the planning and practices around Enterprise Agile give organizations a framework to make better investments and harness the short feedback loops to improve ROI.

To help get you started, here are a few resources that have been recommended to me and I can vouch for their value of learning:

The Agile Executive Whitepaper, Jim Magers, VersionOne. Nice quick read and primer / introduction to agile.

The Concise Executive Guide to Agile, Israel Gat. Nice quick read that provides a deeper dive than the Agile Executive whitepaper.

Scaling Software Agility: Best Practices for Large Enterprises, Dean Leffingwell. Foundations for the Scaled Agile Framework (SAFe) which is being advocated as a framework for leveraging Agile and Lean in the enterprise.

Principles of Product Development Flow, Donald Reinerstsen. Helps explain the way Agile and Lean works in Product Development.

Training – Agile for Executives Workshop, VersionOne. This is a workshop that I’ve performed as well as my colleagues and it’s aimed at being a concise four hour session aimed at ensuring Executives understand the history, underpinnings, and execution models surrounding of Agile and Lean.

Words Mean Things – Waterfall

in Agile/Project Management by

If you are someone who is passionate about Agile, the word “Waterfall” is usually used in a derogatory manner or, at least, when you use it — you are making the stink eye. On the converse, if you are someone who practices what is popularly known as “Waterfall” Project Management you generally get offended or defensive when the phrase “Waterfall” is used.

Here’s how the conversation plays out:

Agile Practitioner – There’s no way I’ll ever work on a Waterfall project.

Waterfall Practitioner – There’s no way I’ll ever work on that Agile project.

Agile Practitioner – Waterfall projects are never successful and I hate being told what to do.

Waterfall Practitioner – Well at least we do work and don’t practice that Agile witchcraft and all that kumbaya mumbo-jumbo.

Agile Practitioner – Well, your mama said Waterfall is for losers.

Waterfall Practitioner – Don’t be talking about my mama …

[chaos ensues]

Winston and Murphy

The sad part about this dialog is that although it’s somewhat fictitious — I’ve heard similar arguments at organizations and with colleagues that work across all spectrums of the project management continuum. The funny part about the dialog above and, in particular, the word Waterfall — no one is really clear who started calling it Waterfall. It’s obvious that when diagramming out a sequential process, it looks like a waterfall.


Often, people credit Dr. Winston Royce with waterfall, especially with respects to software engineering when, in 1970, he wrote a part in a white paper that describes this project management approach (read it here). The funny thing is that he goes on in that same white paper that is credited for starting the waterfall practices to describing how risky it is and that in order to mitigate the risks, each stage of the process should do things iteratively and incrementally.

Waterfall Project Management is really Sequential Project Management. Meaning we perform a sequence of activities and there are generally stages, maybe with sign-offs, and usually hand-offs to another group of people that are charged with performing the next sequence and consuming the output of the previous sequence. Some refer to this as Traditional Project Management, but in most environments its called Waterfall.

I’m not going to discuss the differences between the two and which approach I think is better — it should be clear since you are reading an agile blog. I will say that I think that the merits of each approach are obvious and each approach has challenges. The usage of one approach over the other really depends on the project and possibly the people engaged. What I am going to say is that the world we all live in today, it is very likely that we’ll have a mix of projects using a more Agile approach and one using a more Sequential approach. Sometimes, we’ll have to join forces and combine the output of these approaches into one. Of course, we are learning and adapting ways to do this, but that too is another discussion altogether.

Let’s face it, when words start dividing people, we probably shouldn’t use them any more. Instead call the project management approaches what they are – iterative and incremental, or sequential, or continuous, or simply ad-hoc. Also, be aware that moniker we place on people isn’t really on the people, it’s on the processes by which they may operate in and they may be really comfortable in that process. Generally, they’ve put in a lot of blood and sweat to make it work. Sometimes we need to put the monikers aside and focus on “individuals and interactions over process and tools” (crazy how I got the Agile Manifesto into this blog, isn’t it?).

For now on, be aware and instead of calling it Waterfall, try Sequential Project Management or even Traditional Project Management — unless you want to get in an argument about “your mama.”

Presentation – Doc is a Four Letter Word

in Agile/Resources by
Documentation Formula

So it’s no secret, I like to talk — and here’s a fun one I’ll do with different groups. This is a session that I have had the honor to do in a number of settings that presents ideas and techniques teams can us to help overcome the quagmire of documentation. Hopefully help folks rationalize what documents are required and those that are not. Look over the slides and let me know if you would like me to come talk to your group. I can be reached at

Go to Top