Making Change Happen

I was delighted the other day to have a brief conversation with Mary Lynn Manns, who is the co-author of Fearless Change, an excellent book on making change happen.

And I told her I had this idea: We can let change happen to us. (This is mostly to be passive in the face of bad change.)  Or we can make change happen (the good change).

This dilemma was expressed by Shakespeare:

Whether ’tis Nobler in the mind to suffer
The Slings and Arrows of outrageous Fortune,
Or to take Arms against a Sea of troubles,
And by opposing end them…

We mean something slightly different.  Not just to oppose the negative changes.  But to advocate for positive change.

It takes guts.

I think, for many, it does not feel like guts. It feels like this: “I have to make this change happen, and I don’t care if I get nicked or scratched along the way.” The nicks and scratches are a ‘small price to pay’…is the way they feel.

Anyway, we are better people for making the good changes happen.  It makes us better people.

To make it happen, we must be by turns aggressive and patient.  By turns, emotional and thoughtful.  By turns, with laughter and with all seriousness.

How do we make this happen?

Well, this change and we ourselves are the stuff that dreams are made on.  There is no science here. But there are still many good ideas, and some of these ideas have been tried many times.  And in the hands of the professional, they are usually or often successful.

Mary Lynn Manns and others call them patterns.

The first pattern is Evangelist. That would be you.

The Evangelist comes up with the good idea (somehow).  (Hint: I think the first idea to implement is Scrum.)  And then starts to…well, to evangelize. To get others to try the idea.  To help the idea.

A couple of more patterns:

Ask For Help: The Evangelist asks others for help with the new idea. Maybe help defining it. Maybe help implementing it.  Maybe help evangelizing. Also, have you noticed how wonderfully seductive it is to be asked for help.  Who could possibly have more taste, brilliance, and acumen than the person who would ask me for help?

Innovator:  Usually you have in your group some Innovators. Ask them especially for help.  Get them on your side. In part, they are the ones most likely to have a positive attitude toward trying new things.

Just Say Thanks: Again, it is remarkable how a few bits of good manners can get people to go along with a new idea.  Saying ‘thanks’ for the help can…well, help a lot.

Step by Step: Some of us want to make one big grand change. And be done with it.  But the experience is that it is almost always best done, in some sense, step by step. One smaller change at a time. And they become added together into something quite big.

Small Successes: This is a similar idea, but somewhat different. As you have successes, even if small, be sure to celebrate them.  The small celebrations will delight the change’s supporters, and confound its enemies. (Mark Twain said: When in doubt tell the truth. It will confound your enemies and astound your friends.)

***
In the book Fearless Change, Mary Lynn Manns and Linda Rising have gathered much more detail on these patterns. Indeed, on a total of 48 patterns.

You will find patterns you have done (but probably not done recently).  You will find patterns you have heard of other people trying (but you have never used). And you will hear of completely new patterns.

The main problem is: use one pattern each day.

I think, if you do that, you will win.

Latest Reading List – Books

We have a list of recommended books at LeanAgileTraining.com, here.

In addition, we can recommend the following:

A Sense of Urgency by John Kotter

Fearless Change: Patterns for Introducing New Ideas by Mary Lynn Manns and Linda Rising.

Toyota Production System by Taiichi Ohno.

The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition)by Frederick Brooks.

Fit for Developing Software: Framework for Integrated Tests (Robert C. Martin Series)by Mugridge and Cunningham.

Continuous Integration: Improving Software Quality and Reducing Risk (Addison-Wesley Signature Series)by Duvall, Matyas, and Glover.

Agile Retrospectives: Making Good Teams Greatby Esther Derby and Diana Larsen.

Lean Software Development: An Agile Toolkit (Agile Software Development Series)by Mary & Tom Poppendieck.

Project Retrospectives: A Handbook for Team Reviewsby Norman Kerth.

Test Driven Development: By Example (Addison-Wesley Signature Series)by Kent Beck.

The Wisdom of Teams: Creating the High-Performance Organization (Collins Business Essentials)by Katzenbach & Smith.

Working Effectively with Legacy Code (Robert C. Martin Series)by Michael Feathers.

The Knowledge-Creating Company: How Japanese Companies Create the Dynamics of Innovationby Nonaka and Takeuchi.

Good to Great: Why Some Companies Make the Leap… and Others Don’tby Jim Collins.

Software by Numbers: Low-Risk, High-Return Developmentby Mark Denne and Jane Cleland-Huang.

Agile Estimating and Planning (Robert C. Martin Series)by Mike Cohn.

User Stories Applied: For Agile Software Development (Addison-Wesley Signature Series)by Mike Cohn.

Implementing Lean Software Development: From Concept to Cash (Addison-Wesley Signature Series)by Mary & Tom Poppendieck.

The Five Dysfunctions of a Team: A Leadership Fable by Patrick Lencioni.

Comment: I have given links to Amazon, which has some benefits. I am slightly concerned that it may appear too commercial. There is certainly no obligation to buy from Amazon.

Suggestion: Some of these books are technical (in one area or another) and some are more about people. Mix and match. Consider what you need to learn. Consider what you are most ready to learn. And don’t think too much in the sky. See how much you have really learned by putting your ideas into action.

You’ve got to find what you love (says Steve Jobs)

There was an excellent article in the Wall Street Journal on August 24th.  About Steve Jobs. It gives the text of his commencement address at Stanford in 2005.  A quote from his talk is: “You’ve got to find what you love.”  This is maybe the punch line of one of the three stories he tells.  Please go read the address

I think this is a wonderful idea.

I don’t know much about Steve Jobs, just the obvious stuff.  Maybe he is sentimental, but I don’t think so. (I do salute all he has done. Some failures, but I mostly remember all the successes.)

What I do find is this:
* life is wonderful, and a wonderful gift. (Ok, not always, eg, when Hurricane Irene has just beaten you up.)
* far, far too many people are doing things that they don’t really want to do.  Things they only feel they somehow must do.
* life is short.
* why not live full-out today?  As best you know how.

None of these is a terribly original idea.  No doubt you have heard each one before. But I tell you, they are compelling to me these days. Perhaps you can see a logic, of a sort, in how they are connected.

Let me tell you a story.
The other day I was with a small group, getting ready to practice Hapkido (a Korean martial art, like Aikido roughly).  A few friends were talking. One guy was talking about how he was working with this 23 year old girl, who did not understand money and credit cards. Absolutely no understanding. She has 15 credit cards, and an enormous debt on them, compared to her earnings (which are probably meager, compared to you).

The guy who was trying to help her said: “I am trying to teach her the practical realities of life.”  And my immediate thought at that instant was: “No, money is not practical. What is really practical is changing her spirit.  That is what she will live and die with. When we die, we leave all the money and stuff behind…it has no practical use then. When we die, the spirit is all we have.”

Not sure I have stayed convinced, since then, that spiritual work is the most practical.  I doubt, if you are a skeptic, that my story convinces you.

But I will suggest this, perhaps more seriously.  If you work and work at something you love, you will be more successful at it than at anything else.  By whatever definition of success you give yourself.

To make this just a tad Scrum specific: Product Owners, it is for you to help them feel, if they will, that what you are proposing they do will in some important way fulfill their lives. At least for the time they will work on it. You hold their lives in your hands…well, at least their lives for those days and weeks and months of that effort. Don’t waste it.

Why should a Product Owner care?  On the beautiful Sunday that I see as I write this, one can think of many reasons.  But, to deal with the skeptics, let me quote Little’s Second Law: “People are remarkably good at doing what they want to do.”  And the more they want to do it, the better it will be.

***

Let me end with another quote from his talk:
“The only way to do great work is to love what you do….Don’t settle….Don’t settle.”

Recommended Reading – June 2009

We have a list of recommended books, here.

In addition, we can recommend the following:

A Sense of Urgency by John Kotter.

Fearless Change: Patterns for Introducing New Ideas by Mary Lynn Manns and Linda Rising.

Toyota Production System: Beyond Large-Scale Production by Taiichi Ohno.

Taiichi Ohno’s Workplace Management

The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition)by Frederick Brooks. One of his famous quotes: “How does a project get one year late? One day at a time.”

Fit for Developing Software: Framework for Integrated Tests (Robert C. Martin Series)by Mugridge and Cunningham.

Continuous Integration: Improving Software Quality and Reducing Risk (Addison-Wesley Signature Series)by Duvall, Matyas, and Glover.

Agile Retrospectives: Making Good Teams Great by Esther Derby and Diana Larsen.

Test Driven Development: By Example (Addison-Wesley Signature Series)by Kent Beck.

Working Effectively with Legacy Code (Robert C. Martin Series)by Michael Feathers.

The Knowledge-Creating Company: How Japanese Companies Create the Dynamics of Innovation by Nonaka and Takeuchi.

Good to Great: Why Some Companies Make the Leap… and Others Don’tby Jim Collins.

Software by Numbers: Low-Risk, High-Return Developmentby Mark Denne and Jane Cleland-Huang.

The Five Dysfunctions of a Team: A Leadership Fable by Patrick Lencioni.

Comment: I have given links to Amazon, which has some benefits. There is certainly no obligation to buy from Amazon.

Suggestion: Some of these books are technical (in one area or another) and some are more about people. Mix and match. Consider what you need to learn. Consider what you are most ready to learn. And don’t think too much in the sky. Quickly see how much you have really learned by putting your ideas into action.

AgileBusiness – new yahoo group

Quick notice that we just started a Yahoo group called Agile Business.
See here.

Key words might include: Agile, Business, Business Value, Agile Project Management, Product Owner, business analyst, Lean, Product Management, Marketing, Executive, Manager, Agile for non-SW projects, etc, etc.

Come and share your questions and your comments.

Yahoo Groups – 4 easy lessons

Apologies to those used to Yahoo groups. This is for beginners.

First, why should you care? Because lots of really smart people use Yahoo groups (and ScrumDev in particular).

Second, why should you worry? Because lots of people hear stupid things or get into flame wars on Yahoo groups (and similar). You must Think For Yourself.

1. How to get there.

Go to http://groups.yahoo.com/
In the search box, type in Scrum (one example)
Click on Scrum Development

2. How to join

At the home page, click on Join This Group!
You will be asked to Sign In or Sign Up (become a “member” of Yahoo…it’s free)

3. How to read

From the home page, click on Messages (upper left)
In your Edit Membership (or when you join a group), you can say if you want single or daily emails when posts happen. I like Daily.

4. How to Post

One way: Under Messages, click on Post. That gives you a window to make a post.
Or you can send an email.
Or you can reply to someone’s post.

OK. Now change the mindstream.

Reading List CSM Sutherland/Little course

We recently led a course in Atlanta.

Suggested reading included the following:

The New New Product Development Game by Takeuchi and Nonaka. hbr.com

The Contradictions That Drive Toyota’s Success by Takeuchi. hbr.com

The Concept of “Ba” by Nonaka and Konno.

Comment: For the books, I think it is more colorful and more useful to provide you with a picture of the book and access to Amazon’s info about the book. Hope this is not otherwise a problem; I am slightly concerned that it may appear too commercial.

Suggested Reading – For 2 CSM courses last week

Here are some of the resources we mentioned in the courses.

Caution: “Words, words, mere words, no matter from the heart.” W. Shakespeare. Ground your learning in the heart, and in the fire of experience.

The New New Product Development Game by Takeuchi and Nonaka. Let me ask you to go to www.hbr.com and look it up. It’s a Harvard Business Review article. It costs $6 (softcopy). If you need to see it before you buy it, contact me.

The Knowledge-Creating Company: How Japanese Companies Create the Dynamics of Innovation by Takeuchi and Nonaka. This is the stepping-stone to their discussion of “Ba”.

The Concept of “Ba” by Nonaka and Konno. This article gives an introduction to this subject. “Ba” is the place or context where great teams perform.

Extreme Programming Explained: Embrace Change (2nd Edition) (The XP Series)
by Kent Beck and Cynthia Andres. This may be the best written book on Agile. Certainly XP has a lot to add to the game.

Extreme Programming in Practice
by Newkirk and Martin.

Working Effectively with Legacy Code by Michael Feathers. Great book if you have to work with legacy code. And who doesn’t.

Ssh! We’re Adding a Process by Mark Striebeck at Google. Story of how Ad Words (arguably the highest business value piece of software ever written) adopted Agile/Scrum.

Agile Retrospectives: Making Good Teams Great by Esther Derby and Diana Larsen. Retrospectives will normally be extremely valuable if you follow their advice. (If you just talk, and take no action, retrospectives could be a waste of time almost.)

Fearless Change: Patterns for Introducing New Ideas by Mary Lynn Manns and Linda Rising. One could argue that, since Agile is still new, we need these tools to influence others to adopt Agile. I think a better argument is that we need these tools to influence others because we are always learning what Agile really is. Extremely useful book, whether you are a team member, a Product Owner, a ScrumMaster or a manager.

Rolling out Agile in a Large Enterprise by Gabrielle Benefield. This is about Yahoo. Many good suggestions.

Software by Numbers: Low-Risk, High-Return Development by Mark Denne and Jane Cleland-Huang. This book explains what you should go to Minimum Marketable Feature sets to get incremental funding. Or…it pays to go Agile.

The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) by Frederick P. Brooks. It includes the famous essay on No Silver Bullet.

User Stories Applied: For Agile Software Development (The Addison-Wesley Signature Series) by Mike Cohn. Key stuff.

Agile Estimating and Planning (Robert C. Martin Series) by Mike Cohn. Again, key stuff.

* * *

There are many other great resources. This is a start. You may also want to look at earlier posts of this sort. Start here.

Suggested Resources for CSM Course NYC Feb 28-29

Here are some of the resources we mentioned in the course.

First, a suggestion and two cautions.
Suggestion: Always tightly link thinking and action.
Caution: “Words, words, mere words, no matter from the heart.” W. Shakespeare
Caution 2: “Of making many books there is no end, and much study is a weariness of the flesh.” Ecclesiastes 12:12

The Mythical Man-Month: Essays on Software Engineering, Anniversary Edition (2nd Edition) by Frederick P. Brooks. It includes the famous essay on No Silver Bullet.

The New New Product Development Game by Takeuchi and Nonaka. Let me ask you to go to www.hbr.com and look it up. It’s a Harvard Business Review article. It costs $6 (softcopy). If you need to see it before you buy it, contact me.

Rolling out Agile in a Large Enterprise by Gabrielle Benefield. This is about Yahoo. Many good suggestions.

Software by Numbers: Low-Risk, High-Return Development by Mark Denne and Jane Cleland-Huang. This book explains what you should go to Minimum Marketable Feature sets to get incremental funding. Or…it pays to go Agile.

User Stories Applied: For Agile Software Development (The Addison-Wesley Signature Series) by Mike Cohn. Key stuff.

Agile Estimating and Planning (Robert C. Martin Series) by Mike Cohn. Again, key stuff.

Leading with the Heart: Coach K’s Successful Strategies for Basketball, Business, and Life by Mike Krzyzewski and Donald T. Phillips. I live the Duke Blue Devil basketball team. Not surprisingly, I find basketball an apt metaphor for a software development team. Coach K gives a lot of great advice about building a winning team.
The Concept of “Ba” by Nonaka and Konno. This article gives an introduction to this subject.
***
There are many other great resources. This is a start. You may also want to look at earlier posts of this sort. Start here.

Suggested Resources for attendees at the Jim York Certified ScrumMaster course on Dec 4-5

Here are some suggested resources that came out of a Certified ScrumMaster course that Jim York and I just led.


Books



On the Web

http://www.mountaingoatsoftware.com/
http://www.planningpoker.com/

http://groups.yahoo.com/group/scrumdevelopment/ – The Scrum-Dev yahoo discussion group. Enter with salt.

Articles

New New Product Development Game by Takeuchi and Nonaka. (See http://www.hbr.com/) This is the article that directly led to Scrum (along with other sources). It also gave Scrum its name.

Key Words

Kaikaku – a rapid or radical change event (such as the initial implementation of Scrum)

Kaizen – continuous improvement (also used to refer to continuous improvement actions)

“Go to the Gemba” – Gemba in Japanese means “actual place” or the place where truth is. Similarities to the Godfather phrase “Go to the mattresses”. With “go to the Gemba” we are typically asking a manager to go visit the Agile Team Room.

Genchi Genbutsu – Japanese for “Go and see for yourself”. More roughly translated as “don’t manage from behind a desk”. In Agile, we might say, “Come to the demo and see for yourself” to a stakeholder. Or, to a manager “if you want to really know how the project is going, come to the Daily Standup or come to an Iteration Review.” Closely related to “go to the Gemba” and Gemba Attitude. See http://en.wikipedia.org/wiki/Genchi_Genbutsu
The ScrumMaster role:
“…whose end, both at the first and now, was and is, to hold as ’twere the
mirror up to nature: to show virtue her feature, scorn her own
image, and the very age and body of the time his form and
pressure.” Hamlet. (That’s a lot of what a ScrumMaster does.)


Pictures

Communications Nodes PDF. See http://agileconsortium.pbwiki.com/Presentations
The idea here is to show why we need small teams.
See also earlier posts tagged Recommended Reading.
* * *