Fill in the blanks

I’ve been noticing what’s missing lately. In some ways, its harder to see what’s not there than what is. But there’s lost of useful information in what isn’t said, as well as what is. For example: A manager, talking about one of the...

Helping Your Information Pipeline Flow

Successful management–of product and projects– depends on information flow. Without information about progress and problems, you’ll be blindsided when problems and new information come up, as they inevitably do. Some methods build in visibility and...

Best Argument != Best Ideas

I was talking to my friend Penny the other day about a team she coaches. She has a problem I’ve seen on many teams: a smart guy (or gal) who dominates the team. I’ll call Penny’s team member Bob. Most of the time Bob is an asset to the team. But when...

There’s I(ntelligence)Q, and then there’s I(nfluence)Q

People who work in software are smart people who take pride in their abilities to understand complex information and solve difficult problems. But much of the work isn’t only about smarts. Creating most software requires the help and cooperation of other people....

Fixing the Quick Fix

Here in the United States, our business culture tends to be action-oriented. We value the ability to think fast and act decisively. These qualities can be strengths. However, like most strengths, they can also be a weakness. Taking action when you don’t know the...

Talk, Talk, Talk

I wrote an article about the many ways that managers inadvertently plug the communication pipeline (free registration required). In doing so, they deprive themselves of the information they need to do their jobs. It reminded me of one of the most common ways managers...

Building Trust, One Iteration at a Time

A while back I talked to a CEO of a contract development shop.  He wondered how Agile could help him with fixed price, fixed scope contracts to deliver software. Of course, the requirements that come with these contracts are never complete or completely accurate. The...

Team Norms, Working Agreements, and Simple Rules

What’s the purpose of team values, norms, working agreements, and simple rules? Bob Sutton posted a piece on Team Guidelines that got me thinking how team values can be shaped and influenced. The guidelines–all Mom and Apple Pie–were handed down by a...

Policy Swings and Oscillating Systems

Leaders take action to solve problem in their organizations. They might send out a directive, announce a new policy, or re-organize the department. But, every solutions has the seed for another set of problems. When those problems show up, they reverse course. Policy...

As Goes the Contracting, So Goes the Contract

A while back, a colleague, Susan, called to ask me for some advice. “I’ve been planning a vacation with my family for months,” she said. “And now my new client wants me on-site next week. I’d be happy to come the week after next, but they keep pushing. I told them I...

5 Sources of Team Conflict

Conflict is inevitable at work. Sooner or later, people will disagree. Might be about what to test or how to implement a feature. Team members may disagree about what “done” means, or whether “always” means 100 per cent of the time or some thing else. If...

Entering Groups

An old saw tell us, “You never have a second chance to make a first impression.” This applies to one-on-one introductions, but also to entering groups. When you join a new team–as a member or a coach–those first encounters shape future...

Still No Silver Bullets

Not so very long ago, I made my living writing code. My colleagues and I did our best to understand what our customers needed, and to write code that was easy for other programmers to understand, solid, defect free.  When our managers asked us how long it would take...

Shifting Organizational Patterns

I’ve been talking about (and using) Human Systems Dynamics tools lately–Rally Success Tour, OTUG, Practical Agility and Retrospective Workshops in Stockholm. I find Containers, Differences, Exchanges offers my clients (and me) a useful way to see past...

Don’t mess with the team membership, redux

InfoQ picked up my post, Team Trap #1: Messing with the Membership, and contrasted it with Mike Cohn’s advice that a PO, manager or scrum master who observes that the team is too homogeneous might stick a couple of new team members to increase diversity on the...

Bridging Structural Conflict: Same and Different

Conflict often feels persona. However, the source of conflict is often not. Different goals and priorities create structural conflict– which can then spill over into acrimony and blame. People focus on personal differences rather than the real source of...

Changing to Agile, in an Agile Manner

A while back I was contacted by a potential client who wanted to “go agile.”  But they wanted to do it in a deterministic manner.  They wanted a plan, complete with milestones and dates–mostly indicating that other people had changed their behavior as dictated...

Seeing System Dynamics: Beyond Budget Reports

There’s a buzz about systems thinking in the software world these days. Systems thinking isn’t new. Jerry Weinberg’s An Introduction to General Systems Thinking was first published in 1975. Senge’s Fifth Discipline came out in the 90s. Still, we haven’t turned the...

Messing with the Membership

Do you really have a team when someone keeps messing with the membership? One summer, long ago and far away, I was on a softball team.  It would be an exaggeration to say I played softball, but I did participate in practices, showed up for games and imbibed of...

6 Enabling Conditions for Teams

A team is a social unit, a group of people who work collaboratively to accomplish some goal. Every team is a group of people, but not every group of people is a team. I hear the term applied loosely–describing anything from a collection of individual...

Pin It on Pinterest