1)Firstly, to ensure success of information system projects there is need for a clear and well defined IS goal. Every member of the IS project management team as well as stakeholders should know the specific information requirement of the organization as well as how to go about satisfying it. This is important to guide the information requirements phase of the development process. Failure in this area will lead to fragmented efforts and lack of focus in assembling facts to guide the rest of the development
2)Secondly, the selection of competent and qualified staff to serve as members of IS project team is very vital for successful project implementation . Team members should be those with real prior experience and who are equally familiar with the technology being deployed. Improved training of the end users will significantly reduce system failures and improve the integrity of data stored on the computer systems.
3) the imposition of structure on the developmental effort of the project helps to guide it to successful completion. It involves the division of the project into phases which helps the project team realize what deliverables for each stage are and to know the extent to which they have been met.
4)It is also important that clear lines of authority, communication and responsibility among team members be drawn. This is important since the team members are drawn from diverse units.
Selection of competent leaders who will ensure that proper management and control practices are adhered to and enforced in the implementation process of an Information system is vital. Adequate safeguards and oversight by management is necessary to ensure technical personnel’s compliance with accepted industry standards for reporting and dealing with problems uncovered in any phase of system development. The leader should be one with both application-domain knowledge and software knowledge.
5)The technological infrastructure available in a company needs to be critically assessed to determine it is adequate to support the kind of system development that is to be implemented. Care should be taken not to embark on IS project development until management have the assurance that the company’s technological base is adequate. Assurance from the Management Information System management should be taken to reduce the risk s and uncertainties associated with system development works.
6)Planning/development /budgeting are necessary for the success of an information system project. Planning should be intimately identified with maintaining scope during an implementation. Ineffective planning results in cost overruns and development delays. There is need for the maintenance of scope. The ability to maintain scope is related to planning and this is attainable for companies both small and large
7)Internal readiness/training is also vital for the successful implementation of an information system project. The most common failure factor recorded was that of “readiness for change”. All employees must be trained on the new system in order to prevent underutilization of the system. Also managers must understand the implication of the system and the changes it will cause.
8)Adequate testing of the system is a key element for the successful implementation of the system.
Hello professor, here is my answer:
Establish measurable goals. All changes in the organizations need to support the case, and a measurable goal will provide organizations with a clear direction which will be of great help for the implementation process.
Providing the developer with a complete set of test data and test scenarios which will not only help organizations with the development but can also prevent many problems with data migration.
The requirements analysis should support the development throughout the implementation phase and provide ways to prove how well the requirements are being met.
The person in the role of project technical lead must be experienced, and the project also needs skilled developers, and carefully supervised by the appropriate technical lead.
Test any system thoroughly before placing it into production.
Research from the Project Management Institute (PMI) uncovers that most projects go through five stages, including Initiating, Planning, Executing, Monitoring & Controlling, and Closing.While project failure risk is present in every stage, the likelihood of project failure derives mostly from the Initiating and Planning stages.
Organizations should spend more time on initiation and planning to ensure project risks are properly accounted for. And at the early-stage organizations should understand potential risks.Risk analysis occurs throughout a project lifecycle, but is most critical in the first stages to ensure the team and organization have a good understanding of the project and are aware of what could go wrong.
If it’s unforeseen, it’s more difficult to control for the risk directlyWhile most organizations don’t have (and might not need) a full Project Management Office or robust project management processes, incorporating basic planning and risk analysis strategies will help increase the likelihood of project success. Most of the tips and suggestions offered here can be easily implemented by any organization and can have a positive impact on a project’s outcome.
Dear Professor, the following is my answer
Organizations should spend more time on initiation and planning to ensure project risks are properly accounted for.
Risk Mitigation, Control, and Acknowledgement
There are many risk assessment strategies that organizations can implement to impact risk and overall project success. Depending on the level of risk, a company may consider one of the three following approaches:
A.Mitigation: Understand the risk and deploy strategies to eliminate its occurance. Mitigation strategies are ultimately focused on ensuring the risk does not materialize throughout the project.
B.Controlling: Understand the risk, allow the potential for it to come up, and control the direction of the risk. Controlling strategies focus less on removing risk and more on changing the impact of the risk. This means that the risk may still arise, but its impact will be lesser felt or can be controlled into a positive risk.
C.Acknowledgement: Usually reserved for the lowest impact risks, acknowledgement strategies focus on understanding the risk and not deploying any unique strategies to account for the risk. Acknowledgement should only be used where the impact of a risk on a project is minimal.
Ultimately, accounting for risk has a significant impact on the outcome of a project. How a risk is accounted for is dependent on the project, the organization, and the risk’s potential impact. Regardless, risks need to be accounted for prior to engaging a project.
1.Early-Stage Risk Analysis to Improve Success
As two areas that present the most risk to a project, the Initiating and Planning stages should receive more focus than they typically do. In many organizations that lack a formal project management office or standardized processes, these stages are often overlooked or mini
mized in favour of more resource- and cost-intensive Executing and Monitoring stages.
2.Controlling for Unforeseen Risk
If it’s unforeseen, it’s more difficult to control for the risk directly. You can account for and control some of this risk by implementing stronger project management processes.
3.Strategic Project Management Starts with Effective Planning
While most organizations don’t have (and might not need) a full Project Management Office or robust project management processes, incorporating basic planning and risk analysis strategies will help increase the likelihood of project success.
Here is my answer.
I think risk can be controlled in the following ways.
First, decide whether to use a traditional IS development approach or an Agile one depending on the complexity of your IS requirements. We need to know the correct things to do during the development are:
Individuals and interactions over processes and tools.
Working software over comprehensive documentation.
Customer collaboration over contract negotiation.
Responding to change over following a plan.
Second, Assign a person to follow the development process, in order to report to shareholders and make decisions on whether to change requirements. To achieve information symmetry between developers and customers.
Third, make the effective PM. For example, good cost management, budget management. In the initial stage of IS design, all aspects should be considered, including function realizability, compliance and so on. To avoid subsequent frequent changes and waste of resources due to non-compliance.
Hello professor, here is my answer:
1.It is very important to start and plan the project life cycle during the IS project.
2.Project managers and stakeholders jointly manage the project. Establish comprehensive risk analysis to improve the success rate of the project.
3.Clarify the requirements of information system and build a good team division of labor.
1、Set up control of risk countermeasures
First, adopt stronger legal constraints and include special protections for venture capital in agreements. Second, promote the standardization of internal governance structure of investment enterprises.
2、Set up five stages.
Planning、Analysis、Design、Implementation、Maintenance
The likelihood of project failure derives mostly from the Initiating and Planning stages. Risk analysis and accounting are key components of a project, By taking more attention during the Initiating and Planning stages, organizations can better be got risks throughout the lifecycle and mitigate them before they become a critical project risk.
1. When the organization is in the step of planning, they should consider more about the feasibility of the project.
2. During the project, there should be a supervisor to check the deliverables.
3. There should be a backup IS when the IS project fail.
Add something more.
4. Identify the critical path and pay more attention on it.
5. Find reliable vendors.
6. Take prevention measures for power failure.
7. Company should appoint a specific person be accountable to the project.
8. Company have to achieve an alignment between different components of the project.
Here is my answer:
1.Choose one of the approaches that best match to the project.
2.Dynamic feedback
3.Focus on adaptive rather than predictive methodologies,focus on people rather than roles, and focus on self-adaptive processes.
One way to avoid the IS project failure is to adopt a modern view of project assurance methodology.
project assurance methodology is based on the following principles or best practices:
1.Identify the real issues
2.Set realistic time frames.
3.Align the work streams
4.Look beyond the indicators.
5.Manage the expectations
6.Seek objectivity
Hello, professor
Here is my answer:
1.Choose the appropriate SDLC: For example, it is more appropriate to apply traditional methods that a project is considered to be high-risk and highly complex, and has a development team made up of hundreds of people, while less risky, smaller, and simpler development efforts lend themselves more to agile methods.
2.Hire a professional IS auditor: we could know from CISA that an IS auditor could control risk. Because throughout the project management process an IS auditor should analyze the associated risk and exposures inherent in each phase of the SDLC and ensure that the appropriate control mechanisms are in place to minimize risk in a cost-effective manner.
3.Using software development methods: As we all know, the higher the technology, the less risk. For example, benchmarking is about improving business processes.
Dear Professor, here is my answer:
1. The project risk analysis helps the organization to define business risk, project risk and technical risk.
2. The requirements definition addresses key system controls, such SoD and methods for granting and controlling privileges.
3. Strict change control should be applied.
4. Full, complete and open participation, coordination and communication among all stakeholders should be ensured.
5. The alignment of the three subsystems, including process, context and content, is critical in obtaining an optimal outcome.
Thank you
Applying the risk management process to the SDLC to ensure appropriate protection for the information that the system will transmit, process, and store.
Planning phase:
a. Identification of key security roles to be carried out in the development of the system
b. Make sure all stakeholders have a common understanding of the security considerations
c. Empower managers and supervisers. The Information System Security Officer (ISSO) should be identified as well.
Development phase:
a. Conducting a risk assessment and using the results to supplement the baseline security controls
b. Analyzing security requirements
c. Perform functional and security testing
d. Prepare initial documents for system certification and accreditation
e. Design the security architecture
Implementation Phase:
a. Perform design reviews and system tests before placing the system into operation
b. Additional acceptance tests of new controls
c. Document and update the results of the design reviews and system tests
Maintenance Phase:
a. Monitor performance of the system
b. Document information system changes and assessing the potential impact of these changes on the security of a system
Hi professor,
here is my answer:
1. Choose the right methods, techniques and tools to support system development. For example:
a. When using SDLC, use Agile Methodologies to alleviate the shortcomings of The traditional waterfall SDLC. Or take a more appropriate approach.
b. Use both Extreme programming and Scrum
2. Objective analysis to ensure that the project can achieve the goals and objectives.
3. Strictly implement the project planning work to ensure that the project is delivered on time and that resources and budgets are within the control range.
4. Have professional management personnel to supervise the software development process
5. At each stage of software development, a phased review and risk analysis is carried out.
6. Timely maintenance and update of software.
(1)Stakeholders’ needs and operational goals often contradict each other, so the organization should discuss and determine appropriate goals to avoid the difficulty of satisfying stakeholders.
(2)At the beginning of the project, it is important to understand the background, such as the environment, technology development, etc. Make sure the project is feasible with sufficient preparation and planning at the beginning, thus protecting the project from failure.
(3)The organization needs to have a clear determination of the objectives of the project and thus a clear plan of the project process. Every step should be strictly designed and every specific target should be set reasonably.
(4)The organization should determine which steps should be taken and who should be responsible for each possible problem, which facilitates timely feedback and modification.
(5)Constant updates, iterations, and constant testing are also factors that help projects survive for a long time.
(6)How to operate to achieve a given goal also needs to be rigorously planned, and many details need to be carefully considered.
First, the project manager should do better to review schedules and communicate with clients about the scope and terminology of project and have a clear understanding of what have to complete.
Secondly, to solve the problem on low-effective or low-frequency communication, the team should make a meeting weekly. Seniors understand his/her staff productivity. The manager tracks real-time project schedule.
1. Controlling: Understand the risk, allow the potential for it to come up, and control the direction of the risk.
2. Usually reserved for the lowest impact risks, acknowledgement strategies focus on understanding the risk and not deploying any unique strategies to account for the risk.
3. Understand the risk and deploy strategies to eliminate its occurrence.
4. Account for and control some of this risk by implementing stronger project management processes.
Hello professor, Here is my answer:
1)Firstly, to ensure success of information system projects there is need for a clear and well defined IS goal. Every member of the IS project management team as well as stakeholders should know the specific information requirement of the organization as well as how to go about satisfying it. This is important to guide the information requirements phase of the development process. Failure in this area will lead to fragmented efforts and lack of focus in assembling facts to guide the rest of the development
2)Secondly, the selection of competent and qualified staff to serve as members of IS project team is very vital for successful project implementation . Team members should be those with real prior experience and who are equally familiar with the technology being deployed. Improved training of the end users will significantly reduce system failures and improve the integrity of data stored on the computer systems.
3) the imposition of structure on the developmental effort of the project helps to guide it to successful completion. It involves the division of the project into phases which helps the project team realize what deliverables for each stage are and to know the extent to which they have been met.
4)It is also important that clear lines of authority, communication and responsibility among team members be drawn. This is important since the team members are drawn from diverse units.
Selection of competent leaders who will ensure that proper management and control practices are adhered to and enforced in the implementation process of an Information system is vital. Adequate safeguards and oversight by management is necessary to ensure technical personnel’s compliance with accepted industry standards for reporting and dealing with problems uncovered in any phase of system development. The leader should be one with both application-domain knowledge and software knowledge.
5)The technological infrastructure available in a company needs to be critically assessed to determine it is adequate to support the kind of system development that is to be implemented. Care should be taken not to embark on IS project development until management have the assurance that the company’s technological base is adequate. Assurance from the Management Information System management should be taken to reduce the risk s and uncertainties associated with system development works.
6)Planning/development /budgeting are necessary for the success of an information system project. Planning should be intimately identified with maintaining scope during an implementation. Ineffective planning results in cost overruns and development delays. There is need for the maintenance of scope. The ability to maintain scope is related to planning and this is attainable for companies both small and large
7)Internal readiness/training is also vital for the successful implementation of an information system project. The most common failure factor recorded was that of “readiness for change”. All employees must be trained on the new system in order to prevent underutilization of the system. Also managers must understand the implication of the system and the changes it will cause.
8)Adequate testing of the system is a key element for the successful implementation of the system.
BR
Yidi Xu
Hello professor, here is my answer:
Establish measurable goals. All changes in the organizations need to support the case, and a measurable goal will provide organizations with a clear direction which will be of great help for the implementation process.
Providing the developer with a complete set of test data and test scenarios which will not only help organizations with the development but can also prevent many problems with data migration.
The requirements analysis should support the development throughout the implementation phase and provide ways to prove how well the requirements are being met.
The person in the role of project technical lead must be experienced, and the project also needs skilled developers, and carefully supervised by the appropriate technical lead.
Test any system thoroughly before placing it into production.
Thanks
Hello Professor
Here is my answer:
Research from the Project Management Institute (PMI) uncovers that most projects go through five stages, including Initiating, Planning, Executing, Monitoring & Controlling, and Closing.While project failure risk is present in every stage, the likelihood of project failure derives mostly from the Initiating and Planning stages.
Organizations should spend more time on initiation and planning to ensure project risks are properly accounted for. And at the early-stage organizations should understand potential risks.Risk analysis occurs throughout a project lifecycle, but is most critical in the first stages to ensure the team and organization have a good understanding of the project and are aware of what could go wrong.
If it’s unforeseen, it’s more difficult to control for the risk directlyWhile most organizations don’t have (and might not need) a full Project Management Office or robust project management processes, incorporating basic planning and risk analysis strategies will help increase the likelihood of project success. Most of the tips and suggestions offered here can be easily implemented by any organization and can have a positive impact on a project’s outcome.
Dear Professor, the following is my answer
Organizations should spend more time on initiation and planning to ensure project risks are properly accounted for.
Risk Mitigation, Control, and Acknowledgement
There are many risk assessment strategies that organizations can implement to impact risk and overall project success. Depending on the level of risk, a company may consider one of the three following approaches:
A.Mitigation: Understand the risk and deploy strategies to eliminate its occurance. Mitigation strategies are ultimately focused on ensuring the risk does not materialize throughout the project.
B.Controlling: Understand the risk, allow the potential for it to come up, and control the direction of the risk. Controlling strategies focus less on removing risk and more on changing the impact of the risk. This means that the risk may still arise, but its impact will be lesser felt or can be controlled into a positive risk.
C.Acknowledgement: Usually reserved for the lowest impact risks, acknowledgement strategies focus on understanding the risk and not deploying any unique strategies to account for the risk. Acknowledgement should only be used where the impact of a risk on a project is minimal.
Ultimately, accounting for risk has a significant impact on the outcome of a project. How a risk is accounted for is dependent on the project, the organization, and the risk’s potential impact. Regardless, risks need to be accounted for prior to engaging a project.
1.Early-Stage Risk Analysis to Improve Success
As two areas that present the most risk to a project, the Initiating and Planning stages should receive more focus than they typically do. In many organizations that lack a formal project management office or standardized processes, these stages are often overlooked or mini
mized in favour of more resource- and cost-intensive Executing and Monitoring stages.
2.Controlling for Unforeseen Risk
If it’s unforeseen, it’s more difficult to control for the risk directly. You can account for and control some of this risk by implementing stronger project management processes.
3.Strategic Project Management Starts with Effective Planning
While most organizations don’t have (and might not need) a full Project Management Office or robust project management processes, incorporating basic planning and risk analysis strategies will help increase the likelihood of project success.
Here is my answer.
I think risk can be controlled in the following ways.
First, decide whether to use a traditional IS development approach or an Agile one depending on the complexity of your IS requirements. We need to know the correct things to do during the development are:
Individuals and interactions over processes and tools.
Working software over comprehensive documentation.
Customer collaboration over contract negotiation.
Responding to change over following a plan.
Second, Assign a person to follow the development process, in order to report to shareholders and make decisions on whether to change requirements. To achieve information symmetry between developers and customers.
Third, make the effective PM. For example, good cost management, budget management. In the initial stage of IS design, all aspects should be considered, including function realizability, compliance and so on. To avoid subsequent frequent changes and waste of resources due to non-compliance.
Hello professor, here is my answer:
1.It is very important to start and plan the project life cycle during the IS project.
2.Project managers and stakeholders jointly manage the project. Establish comprehensive risk analysis to improve the success rate of the project.
3.Clarify the requirements of information system and build a good team division of labor.
Dear professor,
Here is my answer:
1、Set up control of risk countermeasures
First, adopt stronger legal constraints and include special protections for venture capital in agreements. Second, promote the standardization of internal governance structure of investment enterprises.
2、Set up five stages.
Planning、Analysis、Design、Implementation、Maintenance
The likelihood of project failure derives mostly from the Initiating and Planning stages. Risk analysis and accounting are key components of a project, By taking more attention during the Initiating and Planning stages, organizations can better be got risks throughout the lifecycle and mitigate them before they become a critical project risk.
1. When the organization is in the step of planning, they should consider more about the feasibility of the project.
2. During the project, there should be a supervisor to check the deliverables.
3. There should be a backup IS when the IS project fail.
Add something more.
4. Identify the critical path and pay more attention on it.
5. Find reliable vendors.
6. Take prevention measures for power failure.
4. Identify the critical path and pay more attention on it.
5. Find reliable vendors.
6. Take prevention measures for power failure.
7. Company should appoint a specific person be accountable to the project.
8. Company have to achieve an alignment between different components of the project.
Here is my answer:
1.Choose one of the approaches that best match to the project.
2.Dynamic feedback
3.Focus on adaptive rather than predictive methodologies,focus on people rather than roles, and focus on self-adaptive processes.
One way to avoid the IS project failure is to adopt a modern view of project assurance methodology.
project assurance methodology is based on the following principles or best practices:
1.Identify the real issues
2.Set realistic time frames.
3.Align the work streams
4.Look beyond the indicators.
5.Manage the expectations
6.Seek objectivity
Hello, professor
Here is my answer:
1.Choose the appropriate SDLC: For example, it is more appropriate to apply traditional methods that a project is considered to be high-risk and highly complex, and has a development team made up of hundreds of people, while less risky, smaller, and simpler development efforts lend themselves more to agile methods.
2.Hire a professional IS auditor: we could know from CISA that an IS auditor could control risk. Because throughout the project management process an IS auditor should analyze the associated risk and exposures inherent in each phase of the SDLC and ensure that the appropriate control mechanisms are in place to minimize risk in a cost-effective manner.
3.Using software development methods: As we all know, the higher the technology, the less risk. For example, benchmarking is about improving business processes.
Dear Professor, here is my answer:
1. The project risk analysis helps the organization to define business risk, project risk and technical risk.
2. The requirements definition addresses key system controls, such SoD and methods for granting and controlling privileges.
3. Strict change control should be applied.
4. Full, complete and open participation, coordination and communication among all stakeholders should be ensured.
5. The alignment of the three subsystems, including process, context and content, is critical in obtaining an optimal outcome.
Thank you
Applying the risk management process to the SDLC to ensure appropriate protection for the information that the system will transmit, process, and store.
Planning phase:
a. Identification of key security roles to be carried out in the development of the system
b. Make sure all stakeholders have a common understanding of the security considerations
c. Empower managers and supervisers. The Information System Security Officer (ISSO) should be identified as well.
Development phase:
a. Conducting a risk assessment and using the results to supplement the baseline security controls
b. Analyzing security requirements
c. Perform functional and security testing
d. Prepare initial documents for system certification and accreditation
e. Design the security architecture
Implementation Phase:
a. Perform design reviews and system tests before placing the system into operation
b. Additional acceptance tests of new controls
c. Document and update the results of the design reviews and system tests
Maintenance Phase:
a. Monitor performance of the system
b. Document information system changes and assessing the potential impact of these changes on the security of a system
Hi professor,
here is my answer:
1. Choose the right methods, techniques and tools to support system development. For example:
a. When using SDLC, use Agile Methodologies to alleviate the shortcomings of The traditional waterfall SDLC. Or take a more appropriate approach.
b. Use both Extreme programming and Scrum
2. Objective analysis to ensure that the project can achieve the goals and objectives.
3. Strictly implement the project planning work to ensure that the project is delivered on time and that resources and budgets are within the control range.
4. Have professional management personnel to supervise the software development process
5. At each stage of software development, a phased review and risk analysis is carried out.
6. Timely maintenance and update of software.
(1)Stakeholders’ needs and operational goals often contradict each other, so the organization should discuss and determine appropriate goals to avoid the difficulty of satisfying stakeholders.
(2)At the beginning of the project, it is important to understand the background, such as the environment, technology development, etc. Make sure the project is feasible with sufficient preparation and planning at the beginning, thus protecting the project from failure.
(3)The organization needs to have a clear determination of the objectives of the project and thus a clear plan of the project process. Every step should be strictly designed and every specific target should be set reasonably.
(4)The organization should determine which steps should be taken and who should be responsible for each possible problem, which facilitates timely feedback and modification.
(5)Constant updates, iterations, and constant testing are also factors that help projects survive for a long time.
(6)How to operate to achieve a given goal also needs to be rigorously planned, and many details need to be carefully considered.
First, the project manager should do better to review schedules and communicate with clients about the scope and terminology of project and have a clear understanding of what have to complete.
Secondly, to solve the problem on low-effective or low-frequency communication, the team should make a meeting weekly. Seniors understand his/her staff productivity. The manager tracks real-time project schedule.
1. Controlling: Understand the risk, allow the potential for it to come up, and control the direction of the risk.
2. Usually reserved for the lowest impact risks, acknowledgement strategies focus on understanding the risk and not deploying any unique strategies to account for the risk.
3. Understand the risk and deploy strategies to eliminate its occurrence.
4. Account for and control some of this risk by implementing stronger project management processes.