- 114,873 hits
The Book Behind The Blog
- Salaries top out at age 40 blog.penelopetrunk.com/2011/02/07/sal… 4 months ago
- Bill Gates' top 10 books of 2012 thegatesnotes.com/Personal/My-To… 5 months ago
- interesting summary of the economic trends of 2011 in charts from leading economists bbc.co.uk/news/in-pictur… 1 year ago
- What Project Managers Can Learn From The Titanic projectcasestudies.com/?p=100 #pmot 1 year ago
Search this blog
- April 2013 (1)
- March 2013 (1)
- October 2012 (1)
- September 2012 (1)
- August 2012 (1)
- June 2012 (1)
- May 2012 (1)
- April 2012 (1)
- March 2012 (1)
- February 2012 (1)
- January 2012 (2)
- December 2011 (4)
- November 2011 (4)
- October 2011 (6)
- September 2011 (5)
- August 2011 (7)
- July 2011 (4)
- June 2011 (4)
- May 2011 (4)
- April 2011 (5)
- March 2011 (9)
- February 2011 (11)
- January 2011 (16)
- December 2010 (12)
- November 2010 (6)
- October 2010 (1)
- September 2010 (3)
- August 2010 (4)
- July 2010 (8)
- June 2010 (13)
- May 2010 (5)
- April 2010 (5)
- March 2010 (7)
- February 2010 (8)
- January 2010 (20)
- December 2009 (6)
- November 2009 (18)
- October 2009 (24)
- September 2009 (10)
- August 2009 (1)
- July 2009 (6)
- May 2009 (1)
- Project Management In A Flat Organization
- Project Management By Robots
- True Requirements
- The Perfect Game
- Read Better
- The Risks of Risk Management
- VIDEO – The Danger of Trusting Experts
- What Project Managers Can Learn From Advertisers
- Interesting Ideas For Managing Conflict
- Modelling Change Management
- The Winner’s Curse And How To Solve It
- Book Review – The Dead Hand
- Best Books of 2011
- VIDEO – 8 Factors That Lead To Success
- Listen Better
- How Fast Can You Fail?
- The Best Research On Project Management
- 17 Beliefs For Project Managers
- Book Review – Mindfire
- The Ig Nobel Prize and Innovation – Tanks and Structured Procrastination
Browse Blog By TopicAmazon Kindle bent flyvbjerg book book review business change management communication cost overrun data visualization decision making estimation Facebook game theory HBR innovation Kindle management McKinsey microsoft project muda NASA peter drucker PMI portfolio management PPM prioritization process process management project project failure project management project portfolio management RescueTime research risk management scrum Seth Godin strategic alignment strategic project portfolio management strategy Sydney Opera House technology ted triple constraint wisdom of crowds
- An error has occurred; the feed is probably down. Try again later.
View Posts By Category
May 2013 M T W T F S S « Apr 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31
New BlogMy new blog featuring only Project Case Studies can be found here
Category Archives: Uncategorized
Perhaps no task is more complex in project management than requirements gathering. The main challenges are with stakeholders asking for things they don’t need, and failing to ask for things that they do require. Prototyping or competitive benchmarking can both help with this problem. However, in many cases neither option is available. Prototyping and works for projects where the production cost is low but if costs are higher prototyping may not be feasible. Competitive benchmarking is only possible if the competitors are present, for example if you are addressing a unique market or one that’s not particularly congested. So you are left with the problems that stakeholders may be asking for they don’t need.
The 100 points method
“100 points” validation is a useful exercise, because it forces the stakeholders and to make exactly the same as those of that you have to make. This is how it works. Having collected all the requirements from stakeholders, we then ask them to allocate 100 points across all of the requirements. If, for example, one requirement is absolutely critical above all others then they might ‘spend’ 100 points on that alone. If there are five requirements of equal value then they might ‘spend’ 20 points across all five. The only constraints are that the points must sum to 100, and no score for any requirement can be less than 0. In this way you’re able and to get stakeholders to supply quantitative information on what they need to see from a project.
Unspoken requirements create a more formidable challenge. Speaking to a large number of stakeholders can reduce the risk of omission. Secondly, ethnographic observation, which involves watching people going about the tasks that the project will help address. This can help you spots areas that are important but may not be explicitly asked for in requirements for example if you might see a process which takes 30 minutes of people’s time each day and you know with the project you can help reduce the time spent on that. However it’s so commonplace in the thinking of the stakeholders that it is omitted from the project requirements. This just scratches the surface of a very thorny topic, but 100 point exercise and ethnographic observation can be useful tools for determining your next set of requirements.
Last month I was at a baseball game on a hot August afternoon. The pitcher was doing pretty well, but there had only been 22 perfect games in the history of American baseball (which is a little under 400,000 games). So, being statistically minded, the odds of any baseball game being perfect game were about 1 in 20,000. According to a dubious probability site, this is about the same probability as being murdered or becoming a professional athlete and 4x less likely than getting a hole in one at golf, now to be fair this isn’t a completely valid comparison since most people who watch baseball see more than one game, increasing the chance of seeing a perfect game. Nonetheless, as much as a perfect game looked on the cards, I could not get out of my head the complete statistical improbability of it happening.
Nonetheless, it did happen, 27 batters up, 27 down, the 23rd perfect game in baseball and the first in Mariners history.
Aside from being an electric experience, it was a good reminder that though statistics can give you a guide to what may happen after the event the odds are always 100% or 0%.
We have all been taught to read and, a fairly involved process that culminates in the teenage years if not sooner. However, we then remain stuck with those reading habits . It’s worth taking time to think about what “advanced reading” looks like. This post offers a few pointers on ways that might make your reading more effective. Reading does not have to involve going through an entire book cover to cover, although this is how we do it with fiction as we learn to read. With non-fiction it can be more efficient to dip into and out of a book based on the areas of greatest relevance to us. This is why, of course, all books have a content page. It’s unlikely that entire book in and all of its chapters are going to be exactly what we would want to read. However within any book there probably are some chapters really going to be relevant for us. So starting with the table of contents and picking out maybe two or three chapters out of the 10 or 15 in the book is likely to be in a more useful way to go about reading than just reading every book cover to cover. Ultimately that means you can read more material that is relevant to you across a number of books rather than feeling obligated to read each book entirely, and as a result you can either spend less time reading, or cover more books
Most people (including me on this blog) tend to talk about communications from the point of view of the person delivering a message or taking the active role. This 8 minute video is interesting, because it flips the perspective to that of the listener. And listeners don’t do a very good job, hearing 60% of what is said and retaining just 25%. This video provides ideas for ways to listen better and be conscious of the filters that we implicitly use to determine what we hear.
It seems counter-intuitive to want to fail fast, but if you stop to think about it, it’s far preferable to failing slowly. Killing a bad project early is superior to letting it run and not meet requirements. The faster you fail the sooner you can test another idea, and that may be the one that leads to success, and we know that psychological traps such as anchoring means that you’re likely to keep pushing a bad idea for too long, even if it’s not working out.
What this means:
- Seek feedback early (ideally critical feedback from a potential customer)
- Follow the path that will get you something testable as soon as possible (Frank Gehry builds models out of paper first)
- Determine what your criteria for success are (otherwise you might be tempted to bend the goals if you aren’t hitting your targets)
It seems counter-intuitive to make failure the goal, but getting through a large number of ideas quickly is a better way to find a good idea than plugging along with something that doesn’t work. The overall result will be more successes, faster.
“It ain’t what you don’t know that gets you into trouble. It’s
what you know for sure that just ain’t so.” Mark Twain
Here are three ‘truths’ of project management that need to be examined more carefully:
1. The triple constraint is a rule to live by.
No, the triple constraint has limitations and it breaks down at certain times. Adding more people can slow a project down because of training and network effects. Cutting scope isn’t linear, it’s binary, at some point scope is cut so much that the project can never succeed.
2. A delayed project is a bad project.
It’s critical not the miss the bigger picture, admittedly harder to measure than cost and budget but just as important, Wembley Stadium, The Scottish Parliament and Sydney Opera House were all late and over budget, but architecturally valuable. Most unimaginative structures get completed on time, but are they really more successful? Of course, the gold standard is a project such as the Guggenheim Bilbao that came in on time and received architectural awards.
3. For good estimates you need experts.
No, reference class forecasting is the answer. Using historical data is much better than using experts. Of course, if historical data isn’t available, then using experts can be a second best approach.
Projects often come in later than expected. It depends on who you ask and how you measure, but 68% is a reasonable guess for the proportion of late projects.
The cost of having a schedule
Arguably though, projects put themselves in an inherently tough position, they have a schedule and that’s precisely what makes extreme lateness possible. Without a schedule there’s no way to be late, since there’s nothing to measure against. Think of a colleague at work who never sets a deadline, but never gets anything done. They’re never late, but only because they don’t have any system in place to measure it. I’m not trying to defend lateness, but the point is projects have accountability because of schedules and deadlines, that’s a good thing.
Comparison With Planes and Trains
Airlines in the US are late about 20% of the time, and trains are late 10-70% of the time depending on the route. Now, bear in mind these are processes not projects, they repeat many times whereas projects, almost by definition have never been done before. And yet repeated activities still suffer significant delays.
What This Means
Maybe we shouldn’t be so harsh on projects. It’s great that we have exacting standards, but bear in mind that:
- Projects are actually measurable, it would be easier to avoid deadlines altogether and eliminate measurement of lateness.
- Even processes experience delays, and they have the benefit of learning through repetition whereas projects don’t.
Something to think about the next time you shoot for 100% on time completion. Even though that feels like a reasonable expectation, maybe it isn’t. On the other hand there’s a lot of value in aggressive goals.
Now Starbucks print warnings on their straws. “Not recommended for use in hot beverages.”
Relentless rules, caveats and documentation are not likely to feed agile processes and innovation.
Agility trumps process. But there a third element that determines both - scale.
Heavy process is seldom chosen, it’s a by-product of scale. You can be agile the first time, the tenth time, but the hundredth time, the thousanth? Whether it’s coffee shops, construction projects or customers the logic is inescapable and the weight of process bears down on you.
You don’t chose process, but you do want to achieve scale, and process is the baggage that comes with repetition.
Netflix embrace agility, but will they still be able to do so when they are the main player in entertainment rather than the upstart competitor?
Two perspectives on dealing with the future, one more time management oriented, the other a little more creative.
Follow Up Then
Follow Up Then (thanks Marc) is a site that enables you to set time based reminder on email. It’s a clever idea and covers for times when you expect a response, but don’t get one, or simply want to send an email away for a while to deal with it later. The ingenuity of the system is that it all works from the address line of whatever email tool you use.
Future Me which is much an art project as a tool also has an accompanying book. Has been used by people to write over a million letters to their future selves, about exam results, break ups, job searches etc. In addition to writing to yourself in the future, you can also read what others have written, here are some of the better ones.