I kind of enjoy it when people get all in a huff over which soda is the best.  It’s bad enough they can’t even decide what to call it. Is it soda, pop, or soda-pop?  I’ve even heard a few refer to any brown carbonated non-alcoholic beverages as a “Coke”.  I don’t get that at all.  I’m going to assume these people just don’t care.  All they want is a brown carbonated non-alcoholic beverage that will satisfy their thirst.  As far as soda-pop, I am the complete extreme opposite.  I drink Coca-Cola.  I don’t drink Coke; I don’t drink Pepsi.  If I ask you for a Coca-Cola and you ask me if Pepsi is OK, I’m going to respond with a stern but polite “No”.  But, at the end of the day, I am also just looking for something to satisfy my thirst.  But, I digress.

Since the Pepsi Challenge in the mid-70′s, there has been another battle raging.  Let’s call it the Delivery Challenge.  Regardless of what facts may be reports, detailing which approach lowers risk the most, which approach delivers the most value up front, or which approach leaves the stakeholders feeling the most satisfied, we all have our favorite.  If delivery approaches were soda-pop (yes, soda-pop) in a blind taste test, chances are we’d stick with our favorite regardless of what we may have picked.

From my own perspective, I don’t believe we should be so blind to these opportunities.  We should be open to the idea that formulas can be improved and we should be open to the idea that processes can as well.

When I’m dealing with the government client on a particular contract, I use Waterfall.  We’re talking Waterfall the size of Niagara Falls.  It’s not that I choose this approach (drink).  It’s all that is currently offered. When I’m managing my own personal projects and deliverables, I use Agile and Kanban.  I’m not saying one is better than the other!  But, when the choice is mine, I know what I like from each.  I ala carte the way I do things, so (as the customer) I get the most value while not bastardizing the original processes.

I know there are those out there who are cursing me.  They are strict Coke, Pepsi, and Dr. Pepper zealots.  Think of me as that kid down at the local Kwik-E-Mart who takes his cup and adds a little of each soda-pop in his 64 ounce cup.  It may look nasty but it sure tastes good.

…and at the end of the day, isn’t it important that I just satisfy my thirst?

Image source: USAGeorge

When you have a project, you need to find out from the customer how they will judge the success of the project.  Don’t go off giving the team high 5′s and leave the customer scratching their head looking at the bill.  At the inception of the project and at the identification of each deliverable, get agreement from the customer as to success criteria.

I just returned from a trip to New York.  Let’s use that trip to illustrate my point.  My wife and I will represent the customers.  Both of us had a different measurement of success.

For my wife, the trip would be a success if we made it to the Gershwin on time to see Wicked.  For me, the trip would be a success if I got to have dinner at John’s Pizzeria.

We identified contingency plans, so we could have different levels of success.  [1] Drive almost an hour and a half to Union Station in Washington DC.

Milestone 1 – Success

[2] Take the train to Penn Station in New York.

Milestone 2 – Success

[3] Get to the W Hotel in Time Square and check in.

Milestone 3 – Success

[4] Get to the Gershwin Theater

Milestone 4 – Success (Customer #1 is 100% satisfied)

The show was really good.  If you haven’t seen it, I would recommend it.  It was odd seeing some people not dressed up.  Call me old fashioned but if you’re going to the theater, it wouldn’t hurt you to dress up.

[5] The next milestone was get to John’s Pizzeria.  I just wanted a pie and a beer.

Milestone 5 – Success (Customer #2 is 100% satisfied)

After dinner, we returned to the hotel and then spent the evening in Time Square.  Last time we were in there, I proposed.  Not a coincidence, our hotel room was right over the spot where I popped the question. Since I take everything so seriously, we then went to a toy store, where I was promptly attacked by a Transformer.  Needless to say, that was not on my risk register.

Thank you to my wife for allowing me to check in via Foursquare and Gowalla.  I didn’t do it a lot.

How was your weekend?

Things seemed to get a little heated in the meeting yesterday.  Upon reviewing the vendor-supplied PowerPoint deck, we noticed graphs illustrating the quantity of issues found and when the vendor planned to fix them.  So, we flipped back a few slides and noticed a table detailing the quantity of requirements that passed or failed, during the last build.  What we didn’t get was something that illustrated the relationship between the two.  Since it wasn’t included in the packet, we wanted an explanation.

Never ask a question in an accusatory manner.  Don’t be condescending.  Make sure the other party hears what you say and understands.  I started with something like this

So help me understand what I’m seeing here.
I see….  …Is that what you see?

I’m looking for the relationship between the issues found and the work you were authorized to complete.  Can you help me with this?

What was missing here was a Requirements Traceability Matrix. It would have answered everything. During this build, only work pertaining to agreed upon requirements should have been done. Only work pertaining to agreed upon requirements should have been tested. Therefore, we should have known immediately which requirements had passed and which failed.  That didn’t happen.

It doesn’t matter if you’re using user stories or requirements.  There are documented expectations that need to be met.  User acceptance criteria should be known.

Any questions?

In celebration of my wife’s birthday, I figured I would make her a homemade birthday cake.  I haven’t done that since before we got married 5+ years ago.  This time, however, I actually asked her what she wanted.  That’s right.  The first birthday cake that I made for her, I didn’t even ask what she would like.  If you were the customer, wouldn’t that kind of tick you off?  Thanks for the cake but… I don’t like that kind.

Getting input (and listening) to your customer goes a long way.

Sure, I could have ordered a cake from the local (and now famous) Charm City Cakes but she didn’t ask for that.  She wanted a chocolate cake with butter cream frosting.  So, last night, our 4-year-old son and I made her a chocolate cake with butter cream frosting.  We even cleaned up the mess after!  But, it wasn’t completely uneventful.  All I can say is I’m glad there were well documented instructions.

Me: Are we a pair of knuckleheads or what?
My son:  I think we’re a pair of clowns, Daddy.

Here is my Project Management Spin

1. Find out what your customer wants.
2. Deliver what your customer wants, not what you want.
3. You’ll spend more money if you want a chef to bake and decorate your cake.
4. You’ll save more time if you want a chef to bake and decorate your cake.
5. Even a pair of clowns can bake and decorate a cake (if instructions are good).
6. You should expect lower quality from a pair of clowns.

Product Delivery

• Both cake and frosting passed unit testing. (Mmmmmm)
• We did a little beta testing last night before the final build.
• The final build was successful.
• We delivered on time.
• We delivered below budget.
• The good news is, I’m pretty sure we’ll pass user acceptance testing.

Happy Birthday to my beautiful and wonderful wife!

People who know me know that I drink a lot of coffee.  I’ll drink it hot.  I’ll drink it cold.  I’ll drink it from the pot, 9 days old.  OK, not 9 days old.  That’s just gross.  One of the places I like to drink coffee is a diner.  9 out of 10 times, diner coffee is good.  It’s simple, it’s basic, and…did I say it was good?  Don’t tell me it’s organic, fertilized with bat guano from El Salvador.  I really don’t care.  The other think I like?  It’s usually $1 for endless refills, printed with pride on the menu.

This post isn’t about cheap coffee.  It’s about a pet peeve of mine.  It applies to me ordering drinks at a restaurant.  Here comes the rant.

Today, my family and went out for lunch.  At the restaurant, I plainly saw the prices for everything on the menu but one thing.  Beverages.  Yes, drinks.  Where the hell are the prices for the drinks?  Is this some kind of trick or tactic? Am I to be embarrassed by the fact that I am unwilling to pay $3.00 for a fountain soda or $8 for a beer?  Chances are, if you don’t post the prices for your drinks, I’m going to order plain old tap water.  Screw you and your clever lack of information.  It’s not my job to ask you how much my drink is going to cost.  You are providing me with a service and that includes prices for the food and drink I’m willing to have with my meal.

If you leave the post at that, I think it stands on it’s own.  If you want me to put a project management spin on it, here goes.  If you are a vendor, and you’re doing contracted work, don’t make your customer ask.  I hate the big reveal.  If you’re going to do contracted work, and you fail to inform your customer what the cost is going to be, you should eat it.  Yep, eat the cost.  Why?  Did you promise to throw in a pair of Ginsu knives when you delivered that product?  I’m going to go out on a limb and say no.  Then why would you expect a customer to give you more money for services rendered or product delivered?

I know there are always exceptions.  What if you, as a vendor, don’t know how much it’s going to cost?  That’s fine.  Communicate with your customer.  Treat them like the intelligent beings they are.  They were smart enough to hire you, right?  Then keep them informed and guide them through the options.  Don’t sneak that $5 cup of coffee onto the final bill and expect a 20% tip.

Takeaway?
Vendors:  Keep your customers informed and don’t make them ask.
Customers:  Don’t let vendors get away with the big reveal.  It will just leave you feeling short-changed.