Question

What are some of the potential sources of risk in a systems analysis and design project? How does the project manager cope with these risks throughout the duration of the project?

Answer 1

Introduction:

All outcomes have risks. If a possible risk of the project isn't known early, then the project is going to be at a high risk to finish as per schedule, inside budget and to fulfill the expected quality. one in each of the present difficulties Janus-faced by a brand new Project Manager nowadays isn't having a sample or general risk list to check with once distinctive the project risk.

Project Risk Identification
Project Risk Management includes the processes of conducting risk management designing, identification, analysis, response designing, and dominant risk on a project. The objectives of the project risk management area unit to extend the probability and impact of positive events, and reduce the probability and impact of negative events within the project.

Project Risk identification is that the most vital method within Risk Management designing. Risk Identification determines that risks may have an effect on the project and document their characteristics. However, we should always not pay an excessive amount of time in distinctive risks. once the list is formed, qualitative and measuring are finished to work out the risks you pay time and/or cash on.

There are some specific tools and techniques for distinctive risk as listed below:

Documentation Reviews

1. Information Gathering Techniques - group action, urban center Technique, Interviewing, Root cause analysis
2. Checklist analysis - previous similar project, lowest level RBS
3. Assumption analysis
4. Diagramming Techniques - cause and result in the diagram, system, and method flow chart, influence diagrams
5. SWOT Analysis
6. Expert Judgment

The common Project Risk List Reference below that area unit divided into a variety of risk classes area unit samples of potential risks of a project could also be exposed to and will solely be employed by the Project Team as a reference and place to begin for risk identification throughout the project risk management designing.

Risk class: Schedule

1. Schedule not realistic, solely "best case".
2. Important task missing from the schedule.
3. A delay in one task causes cascading delays in dependent tasks.
4. Unfamiliar areas of the merchandise take longer than expected to style and implement

Risk class: demand(Requirements) Risk

1. Requirements are baselined however still modification.
2. Requirements area unit poorly outlined, and additional definition expands the scope of the project
3. Specified area unitas of the merchandise are additional long than expected.
4. Requirements area unit solely part legendary at project begins
5. The total options requested could also be on the far side of what the event team will deliver within the time offered.

Risk class: Project Management Risk

1. PM has very little authority within the organization structure and small personal power to influence decision-making and resources
2. Priorities modification on an existing program
3. Project key success criteria not clearly outlined to verify the self-made completion of every project section.
4. Projects inside the program typically want identical resources at the identical time
5. The date is being wholly driven to be compelled to meet promoting demo, trade show, or different mandate; very little thought of project team estimates

Risk class: Product/Technology Risk

1. The development of the incorrect computer program ends up in design and implementation.
2. The development of additional code functions that aren't needed (gold plating) extends the schedule.
3. Requirements for interfacing with different systems aren't underneath the team’s scope.
4. Dependency on a technology that's still underneath development lengthens the schedule.
5. Selected technology could be a poor match to the matter or client

Risk class: client Risk

1. The customer insists on new necessities.
2. Customer review/decision cycles for plans, prototypes, and specifications area unit slower than expected.
3. The customer insists on technical choices that lengthen the schedule.
4. The customer won't settle for the code as delivered although it meets all specifications.
5. The customer has expectations for development speed that developers cannot meet.

Risk class: Human Resources & Contractors Risk

1. Critical development work is being performed by one developer
2. Some developers could leave the project before it's finished.
3. The hiring method takes longer than expected.
4. Personnel wants additional time to be told unknown code tools, hardware, and artificial language.
5. Contract personnel leave before project is complete.
6. Conflicts among team members lead to poor communication, poor styles, interface errors and additional retread.
7. Personnel with the vital skills required for the project can not be found.
8. A contractor doesn't deliver parts once secure.

Conclusion

Risk Identification within the project is vital so as to manage and complete the project with success. the sooner the danger is often known, the sooner the set up are often created to mitigate the consequences of the potential risks. There area unit loads of tools and techniques or methodology offered to spot the project risks. {the methodology|the tactic|the strategy} steered during this article can complement the present risk identification method to induce an additional comprehensive risk list for Risk Management designing. distinctive the danger is associate degree unvaried method, and also the entire project team ought to be concerned from the start of the project. Comprehensive and sensible risk identification can manufacture decent project results.