MBA Project Management
Reg: 511013249
April 2012
A Study on Software Process Risk Assessment,
Evaluation & Management Practices in Indian Software MNCs
Introduction
 Project Risk Management
This thesis focuses on the software project risk, which covers both the
software development risk and the risk involved in transition of the solution
to the customer’s business environment.
A Study on Software Process Risk Assessment,
Evaluation & Management Practices in Indian Software MNCs
Objectives
 To identify the risks in software development projects.
 To explore and analyze the dimensions of project specific risks
based on primary data collected from field survey.
 A comprehensive and exhaustive study is done of an existing
real time. The risks involved in the project were identified and
risk mitigation strategy was devised using Project Management
A Study on Software Process Risk Assessment,
Evaluation & Management Practices in Indian Software MNCs
Related Work
 INFOSYS 2011 Global Risk Management Study
Areas of future development
 Organizational benchmarking using maturity model concepts.
 Integration of risk management with overall project management and corporate culture.
 Increased depth of analysis and breadth of application.
 Inclusion of behavior aspects in the risk process.
 Development of a body of evidence to justify and support use of risk management.
A Study on Software Process Risk Assessment,
Evaluation & Management Practices in Indian Software MNCs
Project Management Life cycle
1. Initiation
2. Planning and Design
3. Execution and construction
4. Monitoring and Controlling systems
5. Completion
A Study on Software Process Risk Assessment,
Evaluation & Management Practices in Indian Software MNCs
Software Development Life Cycle (SDLC)
 Waterfall model
 Spiral model
 Agile development
 Process improvement models
A Study on Software Process Risk Assessment,
Evaluation & Management Practices in Indian Software MNCs
Types of Risks
 Schedule Risk
 Budget Risk
 Operational Risks
 Technical risks
 Programmatic Risks
A Study on Software Process Risk Assessment,
Evaluation & Management Practices in Indian Software MNCs
Research Methodology
 Combination of paper and electronically surveys
 Checklists and Group work
 Questionnaire
 Documentation
A Study on Software Process Risk Assessment,
Evaluation & Management Practices in Indian Software MNCs
Case Study on a Project – ERWINA
 Introduction
The project, ERWINA, tabulates Cognizant, D&B's (Dun and
Bradstreet Account) early warning flags on companies,
indicating imminent risks from a company’s own credit
behaviors, and latent cash flow risk exposure from their supply
chain, family linkage, and industry peers. The purpose of such
data elements is to provide early warnings to the end user about
credit behaviors that may impact a public company's cash flow
and ultimately stock performance.
A Study on Software Process Risk Assessment,
Evaluation & Management Practices in Indian Software MNCs
Sources of Data
 CSAD File (Credit source archive data)
 SMAD (Small merger archive data)
 Detailed Trade file (Trade files)
 Family Linkage file (Parent – Child relationship data)
 Bankruptcy File. (Out of business Company file)
A Study on Software Process Risk Assessment,
Evaluation & Management Practices in Indian Software MNCs
The ERWINA Process
 Data collection.
 Data processing.
 Creation of Variables.
 Final Erwina File.
A Study on Software Process Risk Assessment,
Evaluation & Management Practices in Indian Software MNCs
Risks in ERWINA project
 Risk involved in Technology
 Risk involved in Deficit skills
 Risk involved in Resource constraint
 Risk involved in Oral communication
 Risk involved in Project Cost Estimation (Budget)
A Study on Software Process Risk Assessment,
Evaluation & Management Practices in Indian Software MNCs
Risks in ERWINA project
 Risk involved in Project Schedule
 Risk involved in System testing
 Risk involved in loss of resource
A Study on Software Process Risk Assessment,
Evaluation & Management Practices in Indian Software MNCs
Conclusion
 Training and mentoring
 Investment in research
 Audit reviews
 Explicit and systematic risk management is required
 React quickly to changes in the status of a risk
 Ensure the commitment of the project manager
A Study on Software Process Risk Assessment,
Evaluation & Management Practices in Indian Software MNCs
Bibliography
 Boehm, B. (1981) Software Engineering Economics. Prentice Hall.
 Chatzoglou, P.D and Macaulay L.A. (1998), A Rule- Based approach to
developing software development prediction models, Automated
Software Engineering, Vol. 5 pp. 211 – 243
 Clarke, Thomas and Clegg, Stewart (eds 1998). Changing Paradigms.
London: HarperCollins,
 Sikkim Manipal University(Spring 2010) – Project Risk Management
(PM 0016)
 Sikkim Manipal University(Spring 2010) – Introduction to Project
Management (PM 0010)
 Sikkim Manipal University(Spring 2010) – Project Management
 (MB 0049)
 www.iaeng.org/IJCS/issues_v35/issue_4/IJCS_35_4_02.pdf
A Study on Software Process Risk Assessment,
Evaluation & Management Practices in Indian Software MNCs

MBA_Project_Presentation

  • 1.
    MBA Project Management Reg:511013249 April 2012
  • 2.
    A Study onSoftware Process Risk Assessment, Evaluation & Management Practices in Indian Software MNCs Introduction  Project Risk Management This thesis focuses on the software project risk, which covers both the software development risk and the risk involved in transition of the solution to the customer’s business environment.
  • 3.
    A Study onSoftware Process Risk Assessment, Evaluation & Management Practices in Indian Software MNCs Objectives  To identify the risks in software development projects.  To explore and analyze the dimensions of project specific risks based on primary data collected from field survey.  A comprehensive and exhaustive study is done of an existing real time. The risks involved in the project were identified and risk mitigation strategy was devised using Project Management
  • 4.
    A Study onSoftware Process Risk Assessment, Evaluation & Management Practices in Indian Software MNCs Related Work  INFOSYS 2011 Global Risk Management Study Areas of future development  Organizational benchmarking using maturity model concepts.  Integration of risk management with overall project management and corporate culture.  Increased depth of analysis and breadth of application.  Inclusion of behavior aspects in the risk process.  Development of a body of evidence to justify and support use of risk management.
  • 5.
    A Study onSoftware Process Risk Assessment, Evaluation & Management Practices in Indian Software MNCs Project Management Life cycle 1. Initiation 2. Planning and Design 3. Execution and construction 4. Monitoring and Controlling systems 5. Completion
  • 6.
    A Study onSoftware Process Risk Assessment, Evaluation & Management Practices in Indian Software MNCs Software Development Life Cycle (SDLC)  Waterfall model  Spiral model  Agile development  Process improvement models
  • 7.
    A Study onSoftware Process Risk Assessment, Evaluation & Management Practices in Indian Software MNCs Types of Risks  Schedule Risk  Budget Risk  Operational Risks  Technical risks  Programmatic Risks
  • 8.
    A Study onSoftware Process Risk Assessment, Evaluation & Management Practices in Indian Software MNCs Research Methodology  Combination of paper and electronically surveys  Checklists and Group work  Questionnaire  Documentation
  • 9.
    A Study onSoftware Process Risk Assessment, Evaluation & Management Practices in Indian Software MNCs Case Study on a Project – ERWINA  Introduction The project, ERWINA, tabulates Cognizant, D&B's (Dun and Bradstreet Account) early warning flags on companies, indicating imminent risks from a company’s own credit behaviors, and latent cash flow risk exposure from their supply chain, family linkage, and industry peers. The purpose of such data elements is to provide early warnings to the end user about credit behaviors that may impact a public company's cash flow and ultimately stock performance.
  • 10.
    A Study onSoftware Process Risk Assessment, Evaluation & Management Practices in Indian Software MNCs Sources of Data  CSAD File (Credit source archive data)  SMAD (Small merger archive data)  Detailed Trade file (Trade files)  Family Linkage file (Parent – Child relationship data)  Bankruptcy File. (Out of business Company file)
  • 11.
    A Study onSoftware Process Risk Assessment, Evaluation & Management Practices in Indian Software MNCs The ERWINA Process  Data collection.  Data processing.  Creation of Variables.  Final Erwina File.
  • 12.
    A Study onSoftware Process Risk Assessment, Evaluation & Management Practices in Indian Software MNCs Risks in ERWINA project  Risk involved in Technology  Risk involved in Deficit skills  Risk involved in Resource constraint  Risk involved in Oral communication  Risk involved in Project Cost Estimation (Budget)
  • 13.
    A Study onSoftware Process Risk Assessment, Evaluation & Management Practices in Indian Software MNCs Risks in ERWINA project  Risk involved in Project Schedule  Risk involved in System testing  Risk involved in loss of resource
  • 14.
    A Study onSoftware Process Risk Assessment, Evaluation & Management Practices in Indian Software MNCs Conclusion  Training and mentoring  Investment in research  Audit reviews  Explicit and systematic risk management is required  React quickly to changes in the status of a risk  Ensure the commitment of the project manager
  • 15.
    A Study onSoftware Process Risk Assessment, Evaluation & Management Practices in Indian Software MNCs Bibliography  Boehm, B. (1981) Software Engineering Economics. Prentice Hall.  Chatzoglou, P.D and Macaulay L.A. (1998), A Rule- Based approach to developing software development prediction models, Automated Software Engineering, Vol. 5 pp. 211 – 243  Clarke, Thomas and Clegg, Stewart (eds 1998). Changing Paradigms. London: HarperCollins,  Sikkim Manipal University(Spring 2010) – Project Risk Management (PM 0016)  Sikkim Manipal University(Spring 2010) – Introduction to Project Management (PM 0010)  Sikkim Manipal University(Spring 2010) – Project Management  (MB 0049)  www.iaeng.org/IJCS/issues_v35/issue_4/IJCS_35_4_02.pdf
  • 16.
    A Study onSoftware Process Risk Assessment, Evaluation & Management Practices in Indian Software MNCs