Your SlideShare is downloading. ×
How To Assess Project Proposals
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

How To Assess Project Proposals

6,153
views

Published on

Some notes on how to assess a project brief or business case proposal. …

Some notes on how to assess a project brief or business case proposal.

Don't buy what you hear on face value.

Published in: Business

0 Comments
5 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
6,153
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
433
Comments
0
Likes
5
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. How to assess project proposals
  • 2. Project Options papers will be my death
  • 3. 3 Bloody Options
  • 4. Not more, not less!
  • 5. 3
  • 6. Why do we do them and why are they a mistake?
  • 7. As far as I can work it out, you present 3 options for two reasons
  • 8.
    • To get stakeholder buy-in
  • 9. 2. To force yourself to think through comparisons
  • 10. We are recommended to investigate at least 3 options because it helps us stretch our imaginations
  • 11. And these days we are often asked to put up the “do nothing” option for comparison purposes.
  • 12. (So technically you’ll be getting 4 for the price of 3.)
  • 13. So, 3 bloody options.
  • 14. After a while you’ll find a pattern.
  • 15.
    • Buy, build, partner
    • Tactical, Strategic, Hybrid
    • Team 1’s goals, Team 2’s goals, Everybody wins
  • 16. Are these really options?
  • 17. Here is another example
  • 18. Tactical, partial functionality Full blown integrated IT solution Partly developed IT solution with significant limits
  • 19. Tactical, partial functionality Full blown integrated IT solution Partly developed IT solution with significant limits Obviously you’ll pass on this. This is the under promising mode The team’s jobs depend on this one
  • 20. Which one would you pick?
  • 21. And lifecycle costing means the big up front investment always wins.
  • 22. As an executive what else can you do but go with the analysis & recommendation?
  • 23. Well, there is one or two questions you could ask.
  • 24. 1. What are the delivery risks?
  • 25. How do we know we can pull this off?
  • 26. They sound like the same question but they aren’t
  • 27. What are the delivery risks
    • People capability
    • Requirements stability
    • Dependency on other projects
    • Goal alignment
    • The Stakeholders (your frontline management) are ‘on board’
    • You are ready to spend the time on this project
  • 28. How do we know we can do this?
    • Have we done something like this before?
    • How often to we succeed, partially succeed, or fail?
    • Does our Project Management team have a track record of success?
  • 29. You might also like to ask this:
  • 30. What happens if we fail?
  • 31. Projects cost a lot of money.
  • 32. Just because you are in front of experts, don’t let them drive you into a corner.
  • 33. www.betterprojects.net Questions and comments are welcomed. (Title page photo by llawliet and CC via Flickr )