The Community Blog for Business Analysts

Craig Brown
Craig Brown

26 reasons why projects succeed or fail

There are several studies out there that identify why projects go wrong and what you have to have in place to make sure they have a chance. Naturally the readers of Modern Analyst (and BetterProjects.net) are aware of the importance of good requirements management, a theme which permeates the list below, culled from a range of PM literature[1]
 
You will have heard of many, if not all of these issues before. Today I want to put them into a new context for you; that of the business analysts’ role on projects and what you can do to help your project achieve success.
 
Consider firstly the degree to which the business analyst can control, influence or block each of these issues, then reflect on your personal experience. What techniques have you applied in these areas, and how effective were they? 
 
Critical Factors for Projects
  1. Support from senior management
  2. Clear realistic objectives
  3. Strong/detailed plan kept up to date
  4. Good communication/ feedback
  5. User/client involvement
  6. Skilled/suitably qualified/sufficient staff/team
  7. Effective change management
  8. Competent project manager
  9. Strong business case/sound basis for project
  10. Sufficient/well allocated resources
  11. Good leadership
  12. Proven/familiar technology
  13. Realistic schedule
  14. Risks addressed/ assessed/ managed
  15. Project sponsor/champion
  16. Effective monitoring/control
  17. Adequate budget
  18. Organizational adaptation/culture/ structure
  19. Good performance by suppliers/ contractors/ consultants
  20. Planned close down/review/ acceptance of possible failure
  21. Training provision
  22. Political stability
  23. Correct choice/ past experience of project management methodology/tools
  24. Environmental influences
  25. Learning from Past experience
  26. Appreciating Different viewpoints
 
Now your mission, should you choose to accept it, comes in two stages.
 
Firstly comment below sharing your stories, and secondly go back to your project and see what you can do differently to help your team deliver success.


[1] I picked up this list from a doctoral thesis I read, but the copy I saw did not have the Author’s name on it.
This entry was published on Mar 25, 2008 / Craig Brown. Posted in Project Management, Soft Skills, Leadership & Management. Bookmark the Permalink or E-mail it to a friend.
Like this article:
  17 members liked this article

Related Articles

COMMENTS

Only registered users may post comments.


Blog Information

» What is the Community Blog and what are the Benefits of Contributing?

» Review our Blog Posting Guidelines.

» I am looking for the original Modern Analyst blog posts.



Modern Analyst Blog Latests

Jarett Hailes
Jarett Hailes
As we start a new year many of us will take the time to reflect on our accomplishments from 2012 and plan our goals for 2013. We can set small or large goals. goals that will be accomplished quickly or could take several years. For 2013, I think Business Analysts should look to go beyond our traditional boundaries and set audacious goals. Merriam-...
2 Responses
Howard Podeswa
Howard Podeswa
Recently, I was asked by the IIBA to present a talk at one of their chapter meetings. I am reprinting here my response to that invitation in the hope that it will begin a conversation with fellow EEPs and BAs about an area of great concern to the profession. Hi xx …. Regarding the IIBA talk, there is another issue that I am considering. It's p...
11 Responses
Adrian M.
Adrian M.
Continuing the ABC series for Business Analysts, Howard Podeswa created the next installment titled "BA ABCs: “C” is for Class Diagram" as an article rather than a blog post. You can find the article here: BA ABCs: “C” is for Class Diagram Here are the previous two posts: BA ABCs: “A” is for Activity Diagram BA ABCs: “B” is for BPMN
1 Responses
Featured Digital Library Resources 
Copyright 2006-2015 by Modern Analyst Media LLC