Tuesday, February 19, 2013

The Lean Leadership mindset

In his excellent Gemba Walks, Jim Womack suggests a Lean Leadership mindset. The Lean Leader will:
  1. Embrace the practice of problem-solving by going to the actual place of work, seeing the actual situation, asking great questions about the issues and impediments found, seeking root causes, and showing respect for the lower-level managers and for colleagues at the same organizational level by continuing to ask hard questions until good answers emerge.
  2. Understand that no manager at a higher level should attempt to solve a problem at a lower level on their own. Instead, the higher-level manager can assign responsibility to a manager at a lower level to tackle the problem through continuing dialogue, both vertically with the higher-level manager and horizontally with everyone actually touching the process causing the impediment. This is where Communities of Practice may shine (such as the ones fostered by our Agile Transformation Offices in our various organizations and accounts), by providing ready access to the people most closely involved with and familiar with relevant topics. Problems are best solved right where they are found, in conversation with the people that live with them, rather than pondered in abstract in some remote executive suite.
  3. Know that all problem-solving is about experimentation, preferably by practicing a plan-do-check-act habit of continuous inspection and adaptation. No-one can know the best answer before experiments are conducted, and the many experiments that fail will yield great learning to be applied for the next rounds of experiments.
  4. Appreciate that no problem is ever solved forever. Introducing a promising countermeasure is sure to create other new problems elsewhere in the system. This is not bad - it is to be expected, and it is good, provided that the critical, probing minds of the Leaders keep pursuing continuous improvement.

Sunday, February 17, 2013

So, what's the role of the Agile Project Manager then?

I find that invariably, after I give a brief introduction to the Agile mindset, someone will ask "So, what's the role of the Project Manager in an Agile work process then?"

Let's take the Scrum framework as an example of a typical Agile way of work. Since it only includes the Product Owner, Team Member and ScrumMaster roles, some people may wonder what is to become of Project Managers? Surely, there must be a role for Project Managers in the Agile work process, right?

The short answer is that there are multiple roles available for the Project Manager - each person will have to choose according to their personal experience and aspirations.

All effective Agile work processes take advantage of sound project management practices. The various PMBOK knowledge areas still need care and attention - using an Agile work process doesn't involve any magic that would effortlessly resolve issues of managing integration, scope, time, cost, quality, people, communications, risk, procurement or stakeholders (the fifth version of the PMBOK guide now includes a new chapter on Stakeholder Management).

Agile teams address these issues in a manner culturally different to traditional project management approaches. Rather than concentrating the responsibility to manage the concerns of all project management knowledge areas into a single person (the Project Manager), effective Agile teams rely on all members of the team to contribute their efforts and expertise. Experience teaches us that synergy drawn from diversity is consistently far more effective than individual effort, no matter how heroic a single person might be.

Project Management or Product Management?

A vital distinction is that Agile work processes tend to be focused on perfecting the art of product management, by creating, adjusting and sustaining a product over time in response to feedback from its user community - a product may have an indefinite lifespan, and ever-evolving scope, limited only by its market relevance. On the other hand, by definition:
A project is a temporary endeavor undertaken to create a unique product, service or result.
This dynamic leads to a number of significant implications for the practice of project management in an Agile product development context. The project management disciplines are still vital, regardless of the nature of the work process one might use.

However, there is no room for a traditional Project Manager in an Agile work process, as long as the person insists on behaving with exactly the same habits. For example, in an Agile work process, we cannot continue to expect to have a single person assign tasks to people. Instead, team members self-organize to identify and agree which tasks they should best perform and hold each other accountable for achieving them to meet the Team's commitments.

Does this mean there is no need for Project Managers in Agile work? Not at all - on the contrary, there is a desperate need for Agile Project Managers. If people with a project management background are willing to transform the way they work, they are best placed to make a decisive contribution to changing the world of work for the better for everyone.

The Project Manager as Product Owner

Some Project Managers may have sufficient depth of knowledge in a particular industry or market such that they would make outstanding Product Owners (or Proxy Product Owners).

The Project Manager as Product Manager

For large or complex products that may involve quite a few aspects besides software-intensive systems development, a Project Manager may consider the role of Product Manager.

Using a Product Manager/Product Owner pair for such products, the Product Manager may focus more attention on the customer-facing and non-software aspects, while the Product Owner may devote their attention with priority to the software-intensive systems development activities. For best results, these two people must keep their thinking synchronized at all times. Otherwise, waste and disruption follows.

The Project Manager as Program Manager

For product development efforts that involve many teams, Project Managers may consider playing the role of Program Manager, working with the various teams to coordinate their deliveries. Most of the program management disciplines can continue to be applied in a rather straightforward manner to Agile product development programs, provided the Program Manager develops a good understanding of the nature of the Agile work process used by the teams, paying close attention to the way in which scope evolves over time in the pursuit of value for the customer.

The Project Manager as Scrum Master

As more organizations embrace Agile work processes in their quest to delight customers and make work joyful at the same time, we have a dire need for Scrum Masters to act as Chief Obstacle Removers, defending the health of the Team and its work process from impediments and predators in the form of people making unreasonable or absurd demands. Therefore, we hope that many Project Managers will embrace the Scrum Master role in its full spirit, while steadfastly resisting any lingering command-and-control temptations.

The Project Manager as Team Member

One of the factors which is significantly putting at risk the long term health of software-intensive systems development organizations is the way in which they nurture their technical communities. If the only way to achieve career advancement is to let go of hands-on creation of valuable systems components and turn to a management path of some sort, then the organization will consistently bleed most of their hard-won experts away.

There is a significant challenge in the task of invigorating the approach to nurturing a Technical Career Path such that it becomes much more attractive as a long-term investment and many more people would be able to achieve a satisfying career progression without having to leave it.

If work as a Team Member becomes sufficiently valued and respected socially, then it is conceivable that some Project Managers may choose to join teams back again. They might try their hand at testing, designing the user experience, coding, writing - whatever needs doing in an Agile team. Project Managers as team members would most likely prove excellent mentors, helping all other team members to develop a deeper appreciation of the various aspects of effective project management and increasing the overall effectiveness of the team. If their background was technical to begin with, Project Managers may simply delight in coming back up to speed and then refining their technical expertise in one or more domains, taking a more direct involvement in creating amazing systems.

The Project Manager as Agile Coach

Some Project Managers may have the desire and talent to serve as great Agile Coaches. For more on Agile Coaching, consider the Agile Coaching Institute.

The Project Manager as Strategist or Entrepreneur

Many Project Managers have a wealth of contacts within one or more industries. Some may be able to help organizations to identify and pursue promising product development efforts, shape joint ventures where appropriate, and may help to draw together key teams and experts that can bring them to life.

When preparing programs to start producing new system increments, seasoned Project Managers are well placed to identify and attract the most promising talent.

The Project Manager as Evangelist

In time, some Project Managers may even become Agile evangelists, bringing the good news of continuous improvement to various organizations, helping them to transform their work processes using Lean and Agile thinking.

Your Voice

The usefulness of such ideas multiplies considerably when people add their perspectives. Please consider contributing your thoughts to this topic in the comments. I would warmly welcome a robust dialogue - all views are welcome, from intense support to abject disdain and everything in between.

Wednesday, September 19, 2012

Seven Unbreakable Rules of Software Leadership

Seven Unbreakable Rules of Software Leadership Steve McConnell, of Construx and Code Complete fame, gave a webinar on this topic earlier today. He started by observing that there's no shortage of number-based leadership advice, from the One Minute Manager, to The 30 Management Principles of the US Marines and nearly everything in between.

He argued that leaders of Software organizations must articulate a vision for the future of the organization - be sure that you're actually going somewhere where people might want to follow. What might the future of work in our organization look like? What kinds of improvements do we want to see in our work? How will we get there?

Steve then observed that the more successful leaders of software organizations don't just expect responsibility to be parceled out to them - they claim it. They don't "play the victim card", saying things like "my boss won't let me do X". Instead, they take an active role in explaining great ideas and initiatives, with tenacity and tireless determination. In other words, don't expect to be "assigned" or "allowed" to do something valuable or useful. Jump in, and make it happen as fast as you can.

In software, there's no "perfect" fore-knowledge. That's why great software leaders must figure out how to make viable decisions even in ambiguous circumstances. Figuring out what's the "last responsible moment" to make a decision is a critical art to master.

You also have to put the organization first - which means you might need to take some hard decisions, provided they contribute to the long-term health and viability of the organization. Some people observed that there's an apparent conflict of rule 4 with rule 7, "Treat Your Staff as Volunteers"- the astute leader will find a good balance of decisive decision-making and community engagement, possibly through habits like nemawashi and Gemba walks.

The trouble with lack of "passion" or engagement is that no business leader wants a software leader that's lackadaisical about their business. While discussing the need to find passion for your company's business, Steve offered the personal experience that although you might not feel particularly passionate about a topic at first (like he didn't feel particularly passionate about software engineering when he started writing the first version of Code Complete), you might find yourself develop an intense passion over time (like he did by the time he finished writing the 900+ pages of that tome).

Habits can inspire emotion. Even if you don't feel particularly joyful and you smile, the body will tend to release "happy" chemicals in your blood-stream. Pretty soon, you might notice you feel better. Similarly, if you should need to "fake" passion in your business for a while, that's OK - after a spell, you may well get swept in the excitement and your passion may just become "real".

Becoming a student of communication means that great software leaders must master the art of adapting their communication style to the needs of their audience. A CFO might want numbers. A marketing executive will want stories of exciting features. Developers may want exciting new tech. This may seem obvious for sales or marketing professionals, but it looks like it needs to be spelled out explicitly for software leads.

And finally, Steve concluded by observing that command-and-control is essentially dead. You can't afford not to treat your staff like volunteers, doing your best to give them purpose, autonomy and chances to practice mastery in their work.

What do you think of these seven rules?

Monday, September 3, 2012

You think "that" about teamwork?

TeamworkHere are six misperceptions that HBR's J. Richard Hackman found out through research:

Misperception #1: Harmony helps. Smooth interaction among collaborators avoids time-wasting debates about how best to proceed.

Comment: A bit of creative tension is indeed useful. High-performance teams are usually also high-energy teams, that know how to navigate conflict well. I suggest that a deeper harmony exists in high-performance teams, not just superficially. People trust each other to express diverging opinions and then creatively integrate them for the benefit of all involved. That's true harmony - not just the surface appearance of it.

Misperception #2: It's good to mix it up. New members bring energy and fresh ideas to a team. Without them, members risk becoming complacent, inattentive to changes in the environment, and too forgiving of fellow members' misbehavior.

Comment: No surprises here - longer lived teams fare much better. We can safely continue to push for long-lived Agile teams in pursuit of high performance.

Misperception #3: Bigger is better. Larger groups have more resources to apply to the work. Moreover, including representatives of all relevant constituencies increases the chances that whatever is produced will be accepted and used.

Comment: No surprise here either - 7+/-2 still seems to work best.

Misperception #4: Face-to-face interaction is passé. Now that we have powerful electronic technologies for communication and coordination, teams can do their work much more efficiently at a distance.

Comment: Yes, we must keep pushing for more face-to-face contact in order to improve the flow of value.

Misperception #5: It all depends on the leader. Think of a team you have led, or on which you have served, that performed superbly. Now think of another one that did quite poorly. What accounts for the difference between them? If you are like most people, your explanation will have something to do with the personality, behavior, or style of the leaders of those two teams.

Comment: Yes, self-organizing teams matter most for achieving success. It's not just the leader - it's up to all of us to make our teams run like greased lightning...

Misperception #6: Teamwork is magical. To harvest its many benefits, all one has to do is gather up some really talented people and tell them in general terms what is needed--the team will work out the details.

Comment: Yes, teamwork requires work. High performance doesn't just emerge or happen as soon as you've dropped the "ingredients" together and stirred a bit.

Wednesday, August 29, 2012

Confronting Reality - are you ready to become Fierce?

Surfacing issues or current states of mind to top levels of leadership in organizations with deep hierarchies is fraught with peril. Some top leaders seem afraid of transparency. Some resist the idea of nemawashi - of showing deep respect for their people, of acknowledging that in order to improve our collective lot we should engage everyone's intellect. Vital constraints and facts are closely guarded, and decisions are made in relative secrecy.

Top leaders don't have to attempt to carry the full burden of imagination. They don't have to do all the thinking for all of us, and then issue directives. And yet, many of them don't yet know how to let go. Some haven't managed to muster the courage to become fierce. Some are likely Very Afraid of just such Anarchy as Tobias Mayer's Spirit of Change implies. And attempts at tightening grips of control will only generate more backlash and discontent, more frustration & misery.

Ultimately (and rather amazingly), it comes down to what we believe matters most. Belief is so insubstantial, it's a fleeting pattern of dynamic electro-chemical reactions in the neural networks of humans. And despite this fragility, belief and intent are perhaps the most powerful forces in the human sphere of affairs.

What we believe in drives our habits. It informs our reactions and choices. It shapes who we are, and what we want to be remembered for.

What do you believe in? How do you want to be remembered? What will you do to make it so?

Tuesday, August 28, 2012

STEP – A Map for an Agile Journey

I recently published an article on InfoQ, about how one might look at a journey of continuous improvement inspired by Agile thinking. Would love to hear what you think of it. Which ideas are most helpful to you?

Sunday, April 29, 2012

Delight and Joy - unalienable rights

The Agile Manifesto is an excellent foundation for creating better software development organisations. However, on its own, it lacks a unifying foundation - a means of bringing everyone together, across any organisational boundaries.

Many people still predominantly think in terms of applicability of Agile for specific projects: "Can this project be run using Agile?" or "Would Agile be appropriate for this project?". That kind of attitude slows organisation-wide improvement - it implies that in some areas, the existing ways of work might be "good enough" and therefore exempt from scrutiny and improvement.

The Agile Manifesto, as it currently stands, doesn't directly help people to think in more holistic terms, like: "How may we delight our customers better?", or "How may we best improve our way of work?", despite the fact that agile techniques are very well designed to support improvement.

A few hundred years ago, a nation was born with a proclamation that included the following words:
We hold these truths to be self-evident, that all men are created equal, that they are endowed by their Creator with certain unalienable Rights, that among these are Life, Liberty and the pursuit of Happiness.
In my experience, nothing fundamental has changed in the mean time - we can still safely perceive these truths as self-evident. All of us that work for a living deserve the opportunity to delight our customers and find joy in our work.

Recent research shows that positive emotions play a significant role in achieving success. Consider Shawn Achor's TED Talk: The happy secret to better work, and Barbara Fredrickson's work on positivity.

We all deserve to have ample opportunities to pursue happiness. Since our work lives use up most of our waking hours each week, we had better make sure we can find great joy in our work. Focusing on delighting customers is an excellent and sustainable source of joy and satisfaction in work.

Dan Pink proposes that in our current culture we are primarily motivated by autonomy, mastery and purpose - I find it fascinating how well that parallels with spirit of the Declaration of Independence. Liberty matches autonomy (the freedom to choose our own course of action), mastery matches life (the opportunity to work at improving our skills, minds and bodies), and happiness matches purpose.

I suggest we may find ways of improving upon the Agile Manifesto, quite possibly by harnessing the influence of positive emotions to achieve lasting success in our organisations. What do you think?