This blog is now obsolete. Go to scott.arbeitman.id.au for all new content.

Showing posts with label management. Show all posts
Showing posts with label management. Show all posts
0

Don't Diss the MBA

| Tuesday, October 28, 2008

One of my first blog posts was in praise of Joel Spolsky whose insights into the software sector from both a business and technology perspective are invaluable. But last month Joel wrote an article for Inc magazine on commissions, taking two opportunities to blame poor commission schemes on corporate MBAs:

I can picture the M.B.A. who worked at corporate headquarters. I bet he reaped a big bonus for coming up with an incentive program that dramatically increased the sales of the high-profit silicone spray.

Meanwhile, did anybody notice that the sales of shoes fell by about the same amount?

Or that I started buying my shoes on the Internet?

Sure, blame the MBA for the success of Zappos!

And then:

...Instead of buying the exciting new products I wanted, I was hurled into a mass of people scamming one another -- and all because of stupid, perverse commission systems that seemed like good ideas to the M.B.A.'s back at corporate.

Why Joel has chosen to single out this with a postgraduate degree in business is beyond me. During my MBA class Managing People for High Performance (MPFHP) [see description of the class] we learned of the pitfalls of poor incentive systems, as well as scheme to motivate people through a sophisticated, multi-tiered reward system and to develop them through feedback, not to mention consideration to

  • organizational structure and design
  • investment in training
  • impact and analysis of corporate culture

and lighting the fire to make implement these changes in a dysfunctional organization.

Joel shouldn't blame the business school graduate (or degree) for the demise of companies with poor incentive schemes; he should be engaging MBAs and MBA students to further improve his company, and to articulate and enhance what makes his people high performers.

There will be some MBA students looking to analyze companies in the MPFHP class beginning in Term 1, 2009. I suggest any company skeptical of MBAs to engage the school for these projects.

1

When Projects Go Wrong: Scrum vs. Waterfall

| Tuesday, April 22, 2008
I was thinking of the comparison between a traditional IT project going over budget or late vs. a Scrum project. In Scrum, we reduce scope instead of moving milestone dates. So whereas a project manager might tell the business sponsors
I need another 3 months and $250,000 to finish this project

a Scrum-master might say
As the product stands right now, a few minor features have yet to be implemented. The software is documented, tested and ready for use. For another $250,000 we could get the other features done.

I know which one I would prefer to say, and which one I would prefer to hear. Luckily, they are the same.

Update: As a I get a lot of traffic to this page, I thought of the problems mentioned in CIO magazine about when Agile projects go wrong is also important. What resonates with me is the tendency to avoid getting into too much detail with the client, even though you probably should.

Still, we just deployed a new CRM system over 1 year in the making, and I think an iterative, agile approach would have been much better (and yes, the project was late and over budget).