Thursday, April 22, 2010

What does a PO do?

We say a Product Owner (PO) can have a tremendous impact on the success of a team, of the team's work.

Say, double the productivity in 6 months. With the recession, we could use that about now.

Sounds nice. How is the PO gonna do that?

Well, this is a constant study, but let's summarize the summary here:

* continually improve the BV Engineering theories and practices
* improve the deliver of the Business info into the team
* become better at correctly telling the team what the customers really want
* optimize, continually, on the 80-20 rule
* identify the minimal marketable feature set, and always yet more minimal
* express the value of the customer solution so well, that the team is totally psyched to do the work
* continually integrate the Business and Technical information to make the best possible trade-offs (such as minimizing Technical Debt)

And lastly, seeing and explaining to many people how every one of these activities, when done well together, inter-link and support each other. (Why? A subject for a later post.)

Take a CSPO course and learn more.

Certified Scrum Product Owner course Apr 27-28

For the team's work, a good Product Owner is very important.

A decent PO should be able to double the value delivered by the team, just by their own efforts, in 6 months. (This assumes a normal team, as I see them.) This can make the lives of many real people better: customers, the team, managers, shareholders, etc.

There are too few of these Certified Scrum Product Owner (CSPO) courses, in my opinion. And too few really good POs.

Why our course? Many reasons. What we will say quickly here: we have an MBA and a deep interest in Business Value Engineering.

See here:

CSPO, Charlotte, Apr 27-28.

Thursday, April 1, 2010

If you wait for perfection, ...

If you wait for perfection, you might wait too long.

There are some similar quotes, but so far as I know, this quote is mine. As the father, I kind of like it. But most parents love their own children. (If I am not the father, tell me now.)

This applies to all of life. And to Scrum and Agile and Lean. As the guy said to Jack Lemmon in that famous movie, "Nobody's perfect." In fact, not a single thing is perfect. So, my advice is: Don't wait for perfection.

Still a big problem out there. Too many people doing it. I usually don't do it more than 3 times per day.

Use this quote to work on 'em. Make life better now, before it gets to 'perfect.'

One of the biggest business problems we have.