topleft
topright
Enter the Member Network Zone View the Top 10 Points Leaderboard View Members Who Are Currently Online View Latest Member Activity

Featured Members


Member Network Zone

Expert Blog Comments

The Trouble with Big IT
The problem has never been the technology but people who implement the technologies. The idea around...
Want To Buy a Toyota Prius?
When you have highly complex, real-time software controlling hardware systems, it's virtually imposs...
Sun Veteran Joins Google, Hates Apple
Bray's comments clearly signal the beginning of a war between Google and Apple. You have to wonder w...
What Came First, The Requirements or The Data Model?
It's unfortunate that IT has become a slave to its history. We invented flowcharts to express what w...
BlackBerry Users Rethinking Their Phones
Restlessness is one thing, practicality is another. I swapped my Blackberry for a Droid and found my...
The Price of Right Print E-mail

No, that is not an error. This story is called ‘The Price of Right’; not to be confused with the game show, ‘The Price is Right’.

What is ‘The Price of Right’? It is that toll we pay when it is more important to be right than it is to exercise tact.

What made me think of this? When I teach project management and I discuss scope creep; I usually tell a story about one of my first projects. I really wanted to get along with my customer.
I was not well versed in all of the project management bodies of knowledge. I probably did not know the term scope creep. If the customer asked for something extra, well I would just ask the team to go right ahead. I thought this was great customer service.

So let’s jump ahead to the end of the project. We came in about three weeks late. I realize now that given the changes I agreed to, this was a minor miracle.

In a wrap up meeting, I was asked ‘Why were you late?’ I replied that we had accommodated changes to the original requirements and that took more time. I knew my customer, my buddy and partner would stand by me.

WRONG. He indicated that he did not know about any changes. As far as he was concerned the product delivered was exactly per the original requirements. We were just late, because the IT department is always late.

Boy was I ticked! I wanted to scream out ‘He is lying!’ Something restrained me. I have no idea what; I can’t tell you that at that point in my life I was really that savvy about my working relationships.

If I had argued with him, I would have been right. He did ask for changes, he did know it changed our schedule and he did agree to the new schedule. But I would have paid the ‘Price of Right’; it would have seriously damaged our working relationship. It would have damaged my reputation. After all it is bad form to yell at a customer in front of the team. I would have damaged my career just to satisfy that one violent urge to be right.

But you can bet that next time we had a change log and created change requests for each new or modified requirement.


Comment on this article
RSS comments

Only registered users can write comments.
Please login or register.

 
< Previous   Next >




White Paper Library