Tuesday, May 22, 2007

Project Management as servant, not Master

Jason Yip posted this agility is not the point post to his blog.
  • Deliver the highest possible quality and service to the customer
  • Develop employee potential based upon mutual respect and cooperation
  • Reduce cost through the elimination of waste in any given process
  • Build a flexible production site that can respond to changes in the market

I've started to work through Agile Web Development with Rails. In Chapter One, there is this section titled Rails Is Agile (1.1).
Let’s look at the values expressed in the Agile Manifesto as a set of four preferences. Agile development favours the following.
  • Individual and interactions over processes and tools
  • Working software over comprehensive documentation
  • Customer collaboration over contract negotiation
  • Responding to change over following a plan

Last week we had a talk at work about Project Management (PM), went for about an hour.

At the end I expressed my opinion that Project Management trended to make an organization too lean. Lean in another sense of the work, as in over worked!.

This weakens the organization in three ways.
  • Insufficient resources to respond to the unexpected, particularly human resources.
  • Lack of maintenance of corporate assets, like the code base.
  • Lack of deep infrastructure planning. When I say deep, I mean the shared resources used by most operational activities, including human resources.

Noone actively disagreed with me, including the three Project Managers present.

Been thinking about it more. Thinking triggered by this Seth Godin post & Jason’s post above.

The trouble with PM is when the organization develops a minimum cost/big bang approach to doing things. Be as low cost as possible, gets bodies in to do a job, gets rid of bodies at the end. The public sector is really prown to this!

One issue is that the milestone become the end all. How do you avoid this, it’s natural, the money has got to be tied to something.

PM ends up big on following Process, big on Doco, big on the Plan and big on Contract Negotiation (due to scope creep), putting it at odds with the agile preferences! These are all forms of waste in Lean terms!

Now I’m all in favour of project management (all lower case).

To steal Rowan Bunning’s tag line
"In preparing for battle I have always found that plans are useless,
but planning is indispensable." - Dwight D. Eisenhower

pm makes you think, it’s acting on the useless plans that is a waste.

Where to now?

Well the opposite of minimum cost/big bang management would be maximum effectiveness/steady state management.

What would that look like?

Maximum effectiveness means you’re not measuring costs. You are measuring outcome to expenditure ratios. Further more time and none monetary factors don’t go straight out the front door, as they do when what is being measured, is measured in dollars

Steady state implies that you keep a large core of personnel who maintain existing activities, do projects as needed and are there for the unexpected. You supplement them with specialists and contractor as they’re needed.

Another way of looking at this, is to treat employee as profit centres. That mean the organization tries to develop its employee full potential.


Gnoll110

Technorati tags:

Sunday, May 13, 2007

When to kill a product

After ordering ‘Agile Web Development with Rails’ by Dave Thomas et al, 6 week ago (expect delivery 4 weeks). I final picked it up on Friday. Started reading it on Saturday.

ISBN-10 0-9776166-3-0
ISBN-13 978-0-9776166-3-3
(as I always suspected, the last digit of an ISBN is a check digit :)

One bit in the Preface struck me as being worth a blog post. The last two paragraphs.

... Instead, I found myself rewriting the content. Some chapters from the original have been removed, and new chapters have been added. Many of the rest have been completely rewritten. So, it became clear that we were looking at a second edition-basically a new book.

It seems strange to be releasing a second edition at a time when the first edition is still among the best-selling programming books in the world. But Rails has changed, and we need to change this book with it.

Enjoy!

Dave Thomas
October 2006


For me, this is good example of when to kill a product way before the end of its economic life. All to often you see companies wait for a product to stop being profitable before they release the replacement product.

Know of one case, where a supplement company had a successful protein bar, with three flavours. They let the product get that old before replacing it, that they felt they could only justify redeveloping one of the flavours. Sadly, my favourate was one of the flavours lost. Use to buy boxes (12) of the stuff!

Today, I don’t buy any of this company’s products. Just too trailing edge!

After reading the Preface & first chapter, it looks like an interest and worth while read.


Gnoll110

Monday, May 07, 2007

Google Page Elements suck

Just being playing with Layout, something added in BetaBlogger.

The Page Element stuff sucks.

A really big suck is LinkLists. You have to add ONE link at a time. No editing the HTML to import a block of new links.

Moving from Editable HTML to Layouts is considered an 'upgrade' so there is no going back. BE WARNED!


Gnoll110