The document outlines various risks associated with the nine knowledge areas (KAs) of project management according to the PMBOK guide. For each KA, examples of potential risks on software development and delivery projects are given along with brief explanations and links to additional resources. The top risks identified for each KA include issues like improper integration, unclear requirements, unrealistic timelines, budget miscalculations, poor quality control, inadequate resources, miscommunication, underestimating risks, and contractual failures. Managing these risks effectively is important for project success.

1. Real-World Identified Risks
For All 9 KAs In PMBOK
Submitted By:
Khushboo Wadhwani
Computer Sciences & Information
System Dept.

2. 1.1.Integration Management
Risk#
Integrating the employees, products, services,
operations, systems, and processes is a daunting
thing and is of course a risk to take into account
Here CISCO managed this Integration risk and did a good
job at Integration Management
http://www.cisco.com/web/about/ciscoitatwork/downl
oads/ciscoitatwork/pdf/Cisco_IT_Case_Study_Acq
uisition_Integration.pdf
Case study of: CISCO

3. 1.2.Integration Management
Risk#
Most large IT projects are planned these days, but that is
not enough. Most projects have major milestones,
and the problem is that the work continues
throughout each milestone; implementing
sometimes starts before plan completion and
continues through most of the testing.
This is a case of Bad Integration Management without
taking the planning risk into account
http://www.projectperfect.com.au/info_it_projects_fail.
php
Case study of: Virtual Case Software Project

4. 1.3.Integration Management
http://www.icmrindia.org/casestudies/catalogue/Enter
prise%20Risk%20Management/Enterprise%20Risk
%20Management-
Wipro%20Software%20Services-
Case%20Study.htm
Risk#
Poor Integration of Planning and Designing the
Approach and Process acts as a risk for project all
the time and which impact cost and time handling
as well
This is a case of Bad Integration Management
Case study of: WIPRO

5. 1.4.Integration Management
Risk#
Unstable development of operating system “Copland “for
Apple was a bad step as it was not properly
managed and coordinated so they found
alternative to meet their requirement by
purchasing NeXT which is eventually a good
example of analyzing risk and act at the very right
time in order to fulfill the objective
Example of Good Integration Management
http://www.computerworld.com/article/2533563/it-
project-management/it-s-biggest-project-failures--
--and-what-we-can-learn-from-them.html?page=3
Case study of: Apple’s OS Development Project

6. 2.1.Scope Management
http://www.computerworld.com/article/2533563/it-project-
management/it-s-biggest-project-failures----and-what-
we-can-learn-from-them.html
Risk#
Poor business analysis capability will have three times as
many project failures as successes in IT industry. If we
don’t spend time in formal requirements gathering to
identify project scope it will turn into unclear objective
and arbitrary moves .Unclear requirements is cause of
project failure in IT industry.
This is a case of Bad Scope Management
Case study of: IBM Stretch Project

7. 2.2.Scope Management
Risk#
Number of projected changes to the requirements for
the product before delivery after delivery &
during development impact the quality of product
and sometime leads the project to run out of
time.
This is a case of Bad Scope Management
Case study of: Canada’s Gun Registration System Project
http://www.computerworld.com/article/2533563/it-
project-management/it-s-biggest-project-failures--
--and-what-we-can-learn-from-them.html?page=3

8. 2.3.Scope Management
Risk#
Customers don't (really) know what they want so
eventually project ended up without focusing on
what is the most preliminary requirement of
project.
This is a case of Bad Scope Management
Case study of : FBI Virtual case file
http://www.computerworld.com/article/2533563/it-
project-management/it-s-biggest-project-failures--
--and-what-we-can-learn-from-them.html?page=3

9. 2.4.Scope Management
Risk#
Unclear project goals and objectives, and project
objectives changing during the project as key
factors in project failures i.e. Requirements
change during the course of the project.
This is a case of Bad scope Management
Solution: http://www.techrepublic.com/article/five-
common-errors-in-requirements-analysis-and-
how-to-avoid-them/
Case study of:FBI Virtual case file
http://www.projectperfect.com.au/info_it_projects_fail.p
hp

10. 2.5.Scope Management
Risk#
Objective Changes during project is ultimately slow
down the project, increases labor , increases cost,
increases risk and maintenance and disastrously
degrades the quality too
This is a case of Bad Scope Management
Case study of:FBI Virtual case file
http://www.projectperfect.com.au/info_it_projects_fail.p
hp

11. 3.1.Time Management
http://www.computerworld.com/article/2533563/it-
project-management/it-s-biggest-project-failures--
--and-what-we-can-learn-from-them.html?page=2
Risk#
Customers have unreasonable timelines A common
mistake is to agree to such timelines before
actually performing a detailed analysis and
understanding both of the scope of the project
and the resources necessary to execute it.
This is a case of Bad Time Management
Case study of : FoxMeyer ERP Program
Yellow=risks at QM
Green = risks at TM

12. 3.2.Time Management
Risk#
Another common problem is using linear approximation
when estimating schedule for a project .
This is a case of Bad Time Management
Case study of:FBI Virtual case file
http://www.computerworld.com/article/2533563/it-
project-management/it-s-biggest-project-failures--
--and-what-we-can-learn-from-them.html?page=2

13. 4.1.Cost Management
Risk#
We generally forget to analyze Costs associated with late
delivery and Costs associated with a defective
product External environment
This is a case of Bad Cost Management
http://www.computerworld.com/article/2533563/it-
project-management/it-s-biggest-project-failures--
--and-what-we-can-learn-from-them.html?page=2
Case study of : DMV Projects
Yellow=risks at CM
Green = risks at QM

14. 4.2.Cost Management
Risk#
Every modification turn to increase cost of project and
sometime risk appears in the form that client
remains with zero money because of poor
estimation of budget and cost at initiation
This is a case of Bad Cost Management
http://www.computerworld.com/article/2493658/it-
management/the-scariest-software-project-horror-
stories-of-2012.html
Case study of : Software for California Courts

15. 5.1.Quality Management
Risk#
If we don’t take no. of defects, customer satisfaction,
control of process variance, reliability, security,
into account it’s a risk at quality management
This is a case of Bad Quality Management
Case study of:Microsoft
http://www.icmrindia.org/casestudies/catalogue/Enter
prise%20Risk%20Management/Enterprise%20Risk
%20Management%20at%20Microsoft-
Case%20Study.htm

16. 5.2.Quality Management
Risk#
Performance issues, security issues should be take care
of during the project development but those
issues if experienced after product delivery cause
the reputation of company at stack.
This is a case of Bad Quality Management
Case study of: DVM Projects
http://www.computerworld.com/article/2533563/it-
project-management/it-s-biggest-project-failures--
--and-what-we-can-learn-from-them.html?page=2

17. 5.3.Quality Management
Risk#
Poor quality of new version of product than the older
one thus, the product is not even able to achieve
primary objective of project quality wise.
This is a case of Bad Quality Management
Case study : Sanbury’s Warehouse Automation
http://www.computerworld.com/article/2533563/it-
project-management/it-s-biggest-project-failures--
--and-what-we-can-learn-from-them.html?page=3

18. 6.1.Human Resources Management
Risk#
Workforce planning in terms of risk management comes
as HR management risk.
To analyze in best possible way that :
Who is good for what??
Case study : Sanbury’s Warehouse Automation
http://www.computerworld.com/article/2533563/it-
project-management/it-s-biggest-project-failures--
--and-what-we-can-learn-from-them.html?page=3

19. 6.2.Human Resources Management
Risk#
Lack of manpower development is a HR risk so
Manpower Development is a Human Capital
function which is responsible for developing the
skills, knowledge and competence of the
company's most important asset, its people in
order to meet current and future business
requirements.
This is a case of Good HR Management
Case study of: Infosys
http://www.icmrindia.org/casestudies/catalogue/Enter
prise%20Risk%20Management/Enterprise%20Risk
%20Management%20at%20Infosys-
Case%20Study.htm

20. 7.1.Communications Management
Risk#
Failure to communicate and act as a team to
collaborate and understand project details.
This is a case of Bad Communication Management
Case study : FBI
http://www.computerworld.com/article/2533563/it-
project-management/it-s-biggest-project-failures--
--and-what-we-can-learn-from-them.html?page=3

21. 7.2.Communications Management
Risk#
Two teams who need to work together for a project
have conflicts with each other which results into
bad delivery because at no matter of time they
will communicate properly.
It could be under HR risk as well
This is a case of Bad Communication Management
Case study : FBI
http://www.umsl.edu/~sauterv/analysis/6840_f03_pap
ers/frese/

22. 8.1.Risk Management
Risk#
Not pre -analyzing items of project in danger is a risk of
risk management area; the identification,
assessment, and prioritization of risks(as the effect
of uncertainty on objectives) followed by
coordinated and economical application of
resources to minimize, monitor, and control the
probability and/or impact of unfortunate events .
This is a case of Bad Risk Management
Case study : ABC Company
http://www.sterlinghoffman.com/newsletter/articles/
article485.html

23. 8.2.Risk Management
Risk#
Risks associated with risk management is something all
project leaders, teams and stakeholders need to
delve into during project initiation to analyse all
possible risks.
This is a case of Bad Risk Management
Case study : Polaris
http://www.sterlinghoffman.com/newsletter/articles/
article485.html

24. 8.3.Risk Management
Risk#
Derive all risks at all the stages of SLDC is the potential
step to reduce risks associated with risk
management.
This is a case of Bad Risk Management
Case study : TradeNet
http://jitm.ubalt.edu/V-3/JITM%20Vol%20V%20No.3-
4.pdf

25. 9.1.Procurement Management
Risk#
Greater confidence of right project outsourced at right
time, to right company to fulfill specific activity
goal and take better control of uncertainty
This is a case of Bad Procurement Management
Case study : CN Group
http://file.scirp.org/Html/6-9900055_3213.htm

26. 9.2.Procurement Management
Risk#
Outsourcing of projects leads to some risk factors are
identified, including contracts risk, requirements
definition and change, lack of communication,
political and legal environment differences, and
exchange rate fluctuations
This is a case of Bad Procurement Management
Case study : Microsoft, Oracle
https://books.google.com/books?id=9wXyBwAAQBAJ&pg
=PA656&lpg=PA656&dq=decline+of+software+com
panies+case+study&source=bl&ots=DqUs5dgckp&si
g=x7K7wewkD-
xVSyZspe814gb34Eg&hl=en&sa=X&ved=0CB0Q6AE
wAGoVChMIqe-
275iPyQIVicImCh3GQQmM#v=onepage&q=aCCENT
URE&f=false

27. HW#10#TABLE-ONE

28. Name of Knowledge areas Examples of possible risks for this KA in software D&D projects
with brief explanation) –outcomes should be based on
shttp://www.itexico.com/blog/bid/97592/How-To-Time-
Management-in-Software-Development-and-Project-
Managementearch on internet(Reference links here are for
depicting the detailed solutions or explanation of risks
associated with that KA)
Integration Management RISK#1:
Improper monitoring and Review of the Approach and Process
http://www.slideshare.net/srengasamy/project-monitoring-
evaluation-s-presentation
RISK#2:
Improper Planning and Designing the Approach and Process
http://www.tbs-sct.gc.ca/hgw-cgf/pol/rm-gr/girm-ggir/girm-
ggir02-eng.asp
Scope Management RISK#1:
Poor requirements specification and Lack of a master schedule
http://www.techrepublic.com/article/poor-scope-
management-practices-could-precipitate-project-failure/
http://blog.gichure.me.ke/?p=154
RISK#2:
Change in acquisition strategy
Wrong team choice and resources allocation
http://www.techrepublic.com/article/four-approaches-to-
staff-reallocation-in-project-management/1060462/

29. Time Management RISK#1:
Unrealistic project goals
Badly defined system requirements
Poor reporting of the project's status
http://www.itexico.com/blog/bid/97592/How-To-Time-
Management-in-Software-Development-and-Project-
Management
RISK#2:
Inability to handle the project's complexity
https://www.projectsmart.co.uk/six-time-management-tips-for-
project-managers.php
Cost Management RISK#1:
Longer a project is scheduled to last, the more likely it is that it
will run over time and budget
Wrong budget estimation.
http://galorath.com/wp/software-project-failure-costs-billions-
better-estimation-planning-can-help/
RISK#2:
Cost overruns
Project scope expansion
http://www.sitepoint.com/10-reasons-why-software-project-
estimates-fail/
http://smallbusiness.chron.com/reasons-cost-overruns-project-
management-63225.html
Quality Management RISK#1:
Badly engineered software
http://www.datamation.com/entdev/article.php/3827841/Top-
Five-Causes-of-Poor-Software-Quality.htm
RISK#2:
Poor acquisition practices
http://www.netobjectives.com/blogs/cause-poor-software-
quality
http://blog.smartbear.com/sqc/5-reasons-why-software-quality-
matters-to-your-business/

30. Human Resources Management RISK#1:
Resource shortfalls
Learning curves lead to delays and cost overrun
RISK#2:
Training is inadequate
Resources are inexperienced
http://management.simplicable.com/management/new/130-project-risks
Communications Management RISK#1:
Ensure each team member clearly understands their role on the project. Communicate this at the
beginning of the project and reinforce it as you make progress
http://quickbase.intuit.com/blog/2010/08/27/miscommunication-can-derail-even-the-best-planned-
project/#sthash.eVNrlDqJ.dpuf
RISK#2:
Poor project communication among stackholders and communication gap i.e. less meetings leads to
abstrusely understand project goal will cause many projects to end unsuccessfully.
http://www.projectkickstart.com/downloads/tips11-poor-project-communication.cfm
http://quickbase.intuit.com/blog/2010/08/27/miscommunication-can-derail-even-the-best-planned-
project/
Risk Management RISK#1:
Experienced staff leaving the project and new staff coming in.
Change in organizational management.
Requirement change or misinterpreting requirement.
http://www.cio.com/article/2391872/project-management/12-common-project-management-
mistakes--and-how-to-avoid-them.html
RISK#2:
Under-estimation of required time and resources.
Technological changes, environmental changes, business competition.
http://www.cio.com/article/2434788/project-management/project-management--the-14-most-
common-mistakes-it-departments-make.html
Procurement Management RISK#1:
Failure to negotiation a reasonable price for contracts
http://procurementclassroom.com/checklist-of-potential-risks-in-the-procurement-process/
RISK#2:
Service quality is low
http://www.protiviti.com/en-US/Documents/Surveys/ProcurementContracts.pdf