Super Power #4 – Scope Negotiation

So you are kicking butt on your first project and have completed about half the original scope, plus 25% more because of constant adjustments and additions. That is fantastic and it is what agile is all about for the end user – constant inspection and adaptation that results in better software. Unfortunately, this means that, even if you properly sized everything and executed beautifully, you are 25% off your target budget and timeline!

The 'line in the sand' conversation.

But don’t worry, you as a product owner super hero have your trusty utility belt containing a “line-in-the-sand-conversation”. And it goes something like this:

UNBREAKABLE PO: Stakeholders! I am excited to report we have completed over half of the original project scope! On top of that, we have made many adjustments and additions with your help that have resulted in a project far superior to the one we originally envisioned together.

STAKEHOLDER: That’s great! So at the beginning you said you could deliver everything by July. We’re still on track for that, right?

UPO: Hmm…no, but thankfully we have been regularly reviewing the priority with you every two weeks so those features that will not be in the application are definitely the lowest priority features. Let’s review that list now to make sure we still have it right. I have drawn a line under the last story we will be able to complete. Everything below will have to be part of the next version [or release].

STAKEHOLDER: Looks good but can we just try to squeeze in those three things right under the line?

UPO: Yes dear stakeholder, you can absolutely have those three new features before the end of the project…what would you like to tradeoff so we can make that happen for you?

STAKEHOLDER: They don’t fit huh? Well how do I know how much we need to tradeoff?

UPO: No problem. We have put a rough size estimate next to each story…we call those points. Don’t worry about what the numbers mean, you just need to trade off about the same number of points for the stories you want us to include.

STAKEHOLDER: Alright, let’s get started. How about this 3 point guy right here, that’s not critical…

…AND IT BEGINS…

This is a simple but magical technique, one I have used a number of times with different stakeholder groups and it seems to bring out the rational side in everyone. If you clearly lay out the rules like this, they tend to play by them. Crazy right?

The first time I did this I expected a big conflict but after a tiny bit of exasperation, my stakeholder/sponsor began trading. Obviously, waiting until halfway isn’t ideal so if you are tracking the project burndown and notice things getting off-course by more than a day or so, think about having this conversation. I like to give it a little time as velocity sometimes picks up as a project progresses and the team gets comfortable with what they are doing.

Let me know if you do something different or how this works for you once you try it.

Add to DeliciousAdd to DiggAdd to FaceBookAdd to Google BookmarkAdd to RedditAdd to StumbleUponAdd to TechnoratiAdd to Twitter

Posted in Super Powers | Tagged , , , , , , | Leave a comment

Super Power #3 – Energy

I know, just last week I said you had to sell and now you have to be a pom pom girl too?  YES.  Become the cheerleader, save the…project.  (You know what I mean).  And let me be clear, when I say “energy” I mean two things: (1) the raw enthusiasm you bring when you walk in the door and (2) the energy you and the team get from doing meaningful things.  This can be a potent mix to help you create excellence (and have more fun while you’re at it).

Check out this amazing illustration of what motivates us as knowledge workers:

It is not your sole responsibility to keep the team engaged, but you are one of the ‘spiritual leaders’ of the team and you must help them connect their work to the value it will provide to your end users.  Hopefully, you are working on a project that actually DOES provide value and that is something to be excited about. If the project has no value, you need to escalate that and help your steering group understand this is not the best use of the team’s time. If the team is not engaged, they will not do their best work.

I am not above being a bit over-the-top with my energy (as I am sure my teammates will tell you!) You have to find your comfort level here (and then push a little higher) but please bring a high level of excitement.  People will appreciate it if you are sincere. Likewise, they will all sense immediately if you are not sincere.

So do you bring this kind of energy to your team now?  And whether you do or don’t, what practical steps can you take to get better?

  1. Go buy something from Tony Robbins or another success coach you like. (Yes really!)
  2. Read a (good) book on leadership.
  3. On your VERY NEXT engagement with your team, make sure your focus is not only on the “what” we have to do but also on the “why” we should do it.
  4. And this may sound odd, but…exercise.  It takes energy for a while but sure does give it back later!

As always, love to hear your experiences with this and any advice you have on the subject!

And for next week, I am very excited to talk about Super Power #4 – Scope Negotiation.  It will be good fun.

Add to DeliciousAdd to DiggAdd to FaceBookAdd to Google BookmarkAdd to RedditAdd to StumbleUponAdd to TechnoratiAdd to Twitter

Posted in Super Powers | Tagged , , , , , | 3 Comments

Super Power #2 – Selling

Not a super power you say?  Well whether you are telling the team about the product vision, giving a demo to a group of users, or delivering a project proposal to a steering committee you are selling.  It becomes a super power when you are selling WELL.

Selling is just influencing others to your view.

If you are like me, you grew up thinking that ‘selling’ had to include being slimy, smarmy, or at least pushy. But somewhere along the way, I was made to realize that every day you are selling. This is because ‘selling’ is just influencing people to your viewpoint.  Why should you care as a Product Owner?

Let’s take that last example…if you are successful as a product owner, sooner or later you will need to pitch a new idea to the powers-that-be so your team can get funding right?  So, please put aside your previous concept of ‘sales’ and get psyched for your big presentation.

1. What have you done for me lately? The very first thing you need to do is tell them why they should listen.  They are busy, just like you and me, and if you start with the ‘why’ you will be sending a message that you are not wasting their time.  This isn’t rocket science — in journalism they say, “Don’t bury the lead,” and in agile it is, “Start with the most important stuff,” yet when many people create a presentation they have the important stuff on the very last slide for the ‘big reveal.’  Don’t do that.  Put it first.

2. Focus on one clear idea.  If you don’t do this, the whole presentation will likely get muddled and you may not accomplish any goal.  Resist others suggestions to expand their agenda into your presentation and resist piling in a bunch of other aims.  Simple succeeds.

3. For Pete’s sake, don’t be technical! Try delivering the pitch to your mom — if she can’t get it, they won’t get it.

4. Repeat after me, “Less is ALWAYS more.” Do NOT write your speaking points on powerpoint slides and then read them!  Use slides like a table of contents for your speech.  I like to use the notes section to write out talking points and then bring that version (just for me) to the meeting.

5. Rehearse it, then rehearse it again. When the day arrives you need to be polished so you can focus on the interaction and on being dynamic.  If you are reading or are ill prepared, they will know it and you may leave a bad impression.  Even if you think it is a waste of time right now, go into a room and pretend to present — I guarantee you will make improvements after your first run-through.

The very nature of the PO role is that you are always communicating, so I say we need to embrace it.  Join Toastmasters, read a book, practice with your fellow teammates, but DO work at this.

For our part, my team will be practicing impromptu speaking at our weekly forum — just a quick 1 minute demo of some random prop I bring.  Then we tell them what they did well and what they could do ‘even better’.  This is very similar to what Toastmasters does to give everyone the opportunity to speak every meeting.  The fantastic part about it is that, even in a 1 minute demo you need an intro, a body, and a conclusion. Practice helps make that automatic — it strengthens those speaking muscles.

How about you?  Any “C-level” presentation tips I’m missing for this super power to be complete?

(And don’t forget to come back next Friday — Super Power #3 is all about the energy you bring to the team and how critical your leadership is in helping them see the value their work brings to your organization.)

Add to DeliciousAdd to DiggAdd to FaceBookAdd to Google BookmarkAdd to RedditAdd to StumbleUponAdd to TechnoratiAdd to Twitter

Posted in Super Powers | Tagged , , , , , , , , | 1 Comment

Review – The Talent Code

See how I put the “POs are made, not born” tagline up there at the top of my page?  That’s what The Talent Code is all about.  This book will help you get better at your job – or anything else.

The Talent Code by Daniel Coyle

The key to excellence in EVERYTHING.

The author uncovers how cultures of excellence pop up around the world in “hotbeds” (think Brazilian soccer players), usually in rough looking places. In these places, a mix of desire and intentional learning combine to cause the minds of these future masters to undergo a process called myelination.  Myelin is amazing stuff that allows nerve signals to go thousands of times faster(!!!) than ordinary nerves and explains why masters (in chess, baseball, software development, etc) seem to be superhuman.  Intentional learning, which he describes fully in the book, is how YOU can myelinate ANY paths in your brain to master your chosen profession…like the skills of product ownership, for example.

As Coyle notes in the book it takes 10,000 hours to truly master something, whether that is playing piano, playing basketball, or speaking in public — nobody said it would be easy.  I like that idea because I believe hard work is the answer to most of life’s problems.  During those 10,000 hours your brain is ‘myelinating’ each neural path you fire.  Fire the right path, get more myelin.  It is that easy…except for the 10,000 hours part…which means that whatever you seek to get better at, you’d better love it.

This all means that, sadly, just reading posts in this blog will not get you to the next level.  It is all about what you do between this Tuesday book review and Friday’s super power post.

So…what are you going to do to get better today?  Wrap that myelin, baby!  It’s your ticket to becoming a super hero (here is a little inspiration – 1/3 of the way down under ‘vision improvement’).

Note: I did not receive any form of compensation for this review.

Add to DeliciousAdd to DiggAdd to FaceBookAdd to Google BookmarkAdd to RedditAdd to StumbleUponAdd to TechnoratiAdd to Twitter

Posted in Reviews | Tagged , , , , , | Leave a comment

Super Power #1 – Be Bulletproof

Depending on your particular implementation of agile, this power may be necessary for either your story sizing sessions or your main sprint planning meeting. Either way, it can be rough and you will very likely get hazed by the development team on your first outing.  This can help…

Become bulletproof in planning sessions.

If you are new to your role and especially if you are new to agile (coming from waterfall), the first time you walk into a planning session the developers (and you!) may be a bit anxious.  No requirements docs, no detailed specs.  Just a simple backlog of stories…and you.  To compensate, the team will be asking a lot of questions.

You, fearless product owner, will of course do your best and you can survive your first planning meeting if you have these four shields at the ready:

1. Prepare(!) – This is all important once you know what it means, but basically you have to really ‘get’ what the customer’s intent is and describe it clearly in your acceptance criteria.  If you don’t make it clear, the developers will say things like, “We can’t build this without more specific information,” or they will size it as WAY bigger than it really is because of the uncertainty.

2. Be decisive – As the one giving direction for the product, you need to make confident choices when presented with multiple ways forward. If people start discussing two technical paths, pick one and offer that we should size that one.  You will get it wrong sometimes but better to be wrong and learn than to suffer the ‘paralysis of analysis’ (where you may also get it wrong but will take longer to figure that out!)  Just use your best judgment when you weigh the costs and benefits of the options.

3. Size both – I occasionally even have them size two options if: (1) I have a dispute among the team members that is not resolving itself or (2) there is a real chance we might do either and I could benefit from understanding the relative cost difference.

4. Defer - This is your last resort — if you run into a story you THOUGHT you prepared well enough but turns out you didn’t, don’t be shy about deferring it until a later time it so you can clarify. Ain’t no shame in it.  Say it with me, “I think I need to clarify this story a bit more.  Let me do that and bring it back around next time.”

I won’t lie, I have been raked across the coals by two development teams and each of my product owners were by their respective teams as well, even though these are all fine teams of reasonable people.  Seems to be a right of passage, but if you use the techniques here and act with confidence, you’ll be fine.

Would love to hear your ideas, and don’t forget to join me next week for Super Power #2 – Selling (your ideas), same PO time, same PO channel.

Add to DeliciousAdd to DiggAdd to FaceBookAdd to Google BookmarkAdd to RedditAdd to StumbleUponAdd to TechnoratiAdd to Twitter

Posted in Super Powers | Tagged , , , , | Leave a comment

How to Become a Super Hero

According to Jeff Patton, the ideal product owner (PO) would be a super hero, complete with cape and spandex, though he says that these super heroes are extremely difficult to find, perhaps even mythical.

I do not claim to be that guy (yet), so my blog title is…aspirational. But I will say that I am going at this PO thing 1,000% with every waking hour. I read about 50 books a year on everything from leadership, to programming, to usability (among other topics). I am not a programmer but I am working through two books on Objective-C development to learn about object oriented programming (OOP) as well as reading Apple’s Human Interface Guidelines to understand their unique perspective on application design.  I will also be coding some experimental applications to have a bit of fun with this new info.

As chief product owner, I am working to develop financial analysis, collaboration, and calendaring software with a team of three product owners. They are all in their first year as POs so I have TWICE as much experience…umm, anyway we aspire to become a high performing team. But as I say to them and myself, “Interest is not the same thing as ability,” and that is where my high intensity learning program starts.

This blog is about sharing lessons with you, my fellow POs, because it wasn’t so long ago that I went looking for this kind of information. I couldn’t find it, but apparently that was just because I hadn’t written it yet.

The unbreakable part of my blog name comes from that great M. Night Shyamalan movie where the entire movie is our hero discovering he has super powers. That’s what we are all striving for as product owners right?

And in keeping with the heroes theme, I am going to structure my publications like the Heroes TV show. That is, once a week I’ll post the main lesson I have learned with my team that drives the plot forward but there will be those ‘in between’ episodes where I am doing quick reviews of books, conferences, etc, that will also help you survive the demands of being an agile PO…and maybe even earn that cape.

Let’s rock and roll.

Add to DeliciousAdd to DiggAdd to FaceBookAdd to Google BookmarkAdd to RedditAdd to StumbleUponAdd to TechnoratiAdd to Twitter

Posted in Super Powers | Tagged , , , , , , , | 2 Comments