http://www.oraerp.com/ Sun, 19 May 2013 16:26:34 +0000 MyBB http://www.oraerp.com/Thread-ICT-Change-Management-Forms-Issue-Logs Wed, 02 Jan 2013 23:39:28 -0600 http://www.oraerp.com/Thread-ICT-Change-Management-Forms-Issue-Logs 1. Change Request Form Template
2. Change Request Log Template
3. Issue Document Template
4. Issue Log Template

5. Monthly Status Report Template

  Change_Request_Form_Template.doc (Size: 50.5 KB / Downloads: 23)

  Change_Request_Log_Template.xls (Size: 137.5 KB / Downloads: 13)

  Issue_Document_Template.doc (Size: 51.5 KB / Downloads: 20)

  Issue_Log_Template.xls (Size: 100 KB / Downloads: 24)

  Monthly_Status_Report_Template.doc (Size: 70.5 KB / Downloads: 18) ]]> 1. Change Request Form Template
2. Change Request Log Template
3. Issue Document Template
4. Issue Log Template

5. Monthly Status Report Template

  Change_Request_Form_Template.doc (Size: 50.5 KB / Downloads: 23)

  Change_Request_Log_Template.xls (Size: 137.5 KB / Downloads: 13)

  Issue_Document_Template.doc (Size: 51.5 KB / Downloads: 20)

  Issue_Log_Template.xls (Size: 100 KB / Downloads: 24)

  Monthly_Status_Report_Template.doc (Size: 70.5 KB / Downloads: 18) ]]> http://www.oraerp.com/Thread-Oracle-Implementation-Project-Plan Wed, 08 Jun 2011 11:11:47 -0500 http://www.oraerp.com/Thread-Oracle-Implementation-Project-Plan Attached is the MS Project Plan for implementing Oracle Applications with a framework. It contains the detailed tasks involved and lists the associated resources that may be needed.

The Work Breakdown Structure (WBS) codes tie back in to the Oracle AIM documents that should be prepared for each task and phase.

  ABF_WM020_PROJECT_WORKPLAN_W_PJM41.zip (Size: 49.08 KB / Downloads: 652)

  Oracle_implementation_plan.zip (Size: 89.89 KB / Downloads: 825) ]]> Attached is the MS Project Plan for implementing Oracle Applications with a framework. It contains the detailed tasks involved and lists the associated resources that may be needed.

The Work Breakdown Structure (WBS) codes tie back in to the Oracle AIM documents that should be prepared for each task and phase.

  ABF_WM020_PROJECT_WORKPLAN_W_PJM41.zip (Size: 49.08 KB / Downloads: 652)

  Oracle_implementation_plan.zip (Size: 89.89 KB / Downloads: 825) ]]> http://www.oraerp.com/Thread-Project-Risk-Management-Plan Wed, 08 Jun 2011 10:45:03 -0500 http://www.oraerp.com/Thread-Project-Risk-Management-Plan 1. Define the risk management methodology to be used. Section 1 of this table defines your risk management process. The risk management process is scalable to ensure that the level, type, and visibility of risk management are commensurate with both the risk and the importance of the project. Modify the text in this section to fit your process.


Risk Identification – Identify risks through discussion with all major stakeholders. Also use the Risk Assessment Questionnaire and Project Planning Risk Assessment Checklist, augmented to include other project specific risks, as appropriate.


Risk Categorization – Group the risks into categories by using the Risk Assessment Questionnaire. The project manager can create additional categories, as required.


Risk Probability and Impact Assessment – Enter all risks into the Risk Response Plan document. For each risk identified, assess the risk event in terms of likelihood of occurrence (Risk Probability) and its effect on project objectives if the risk event occurs (Risk Severity = Impact Score). This information will be used to prioritize the risk using established threshold criteria.


Risk Prioritization - Risks that meet the threshold criteria will be so noted in the Risk Register. These Risks will be prioritized.


Risk Response Planning – For each risk in the Risk Register that is above the Risk Threshold:

• Determine the options and actions to reduce the likelihood or consequences of impact to the project’s objectives
• Determine the response based on a cost/benefit analysis (cost vs. expected effectiveness)
• Describe the actions to be taken to mitigate the risk
• Describe the Signs and Symptoms that may be indicators of Risk Event occurrence
• Describe the actions to be taken when the risk event occurs (contingency plan)
• Assign responsibilities for each agreed-upon response
• Assign a “due date” where risk responses are time-sensitive
• Determine impact on project budget and schedule and make appropriate changes or additions to the project plan.
• Incorporate this information into the Risk Register
  

Risk Response Tracking
Risk Monitoring
Risk Control

  Risk_Assessment_Questionnaire_Template.doc (Size: 146.5 KB / Downloads: 130)

  Risk_Assessment_SOW_Template.doc (Size: 64 KB / Downloads: 122)

  Risk_Management_Plan_Template.doc (Size: 83.6 KB / Downloads: 119)

  Risk_Response_Plan_Template.zip (Size: 374.63 KB / Downloads: 121) ]]> 1. Define the risk management methodology to be used. Section 1 of this table defines your risk management process. The risk management process is scalable to ensure that the level, type, and visibility of risk management are commensurate with both the risk and the importance of the project. Modify the text in this section to fit your process.


Risk Identification – Identify risks through discussion with all major stakeholders. Also use the Risk Assessment Questionnaire and Project Planning Risk Assessment Checklist, augmented to include other project specific risks, as appropriate.


Risk Categorization – Group the risks into categories by using the Risk Assessment Questionnaire. The project manager can create additional categories, as required.


Risk Probability and Impact Assessment – Enter all risks into the Risk Response Plan document. For each risk identified, assess the risk event in terms of likelihood of occurrence (Risk Probability) and its effect on project objectives if the risk event occurs (Risk Severity = Impact Score). This information will be used to prioritize the risk using established threshold criteria.


Risk Prioritization - Risks that meet the threshold criteria will be so noted in the Risk Register. These Risks will be prioritized.


Risk Response Planning – For each risk in the Risk Register that is above the Risk Threshold:

• Determine the options and actions to reduce the likelihood or consequences of impact to the project’s objectives
• Determine the response based on a cost/benefit analysis (cost vs. expected effectiveness)
• Describe the actions to be taken to mitigate the risk
• Describe the Signs and Symptoms that may be indicators of Risk Event occurrence
• Describe the actions to be taken when the risk event occurs (contingency plan)
• Assign responsibilities for each agreed-upon response
• Assign a “due date” where risk responses are time-sensitive
• Determine impact on project budget and schedule and make appropriate changes or additions to the project plan.
• Incorporate this information into the Risk Register
  

Risk Response Tracking
Risk Monitoring
Risk Control

  Risk_Assessment_Questionnaire_Template.doc (Size: 146.5 KB / Downloads: 130)

  Risk_Assessment_SOW_Template.doc (Size: 64 KB / Downloads: 122)

  Risk_Management_Plan_Template.doc (Size: 83.6 KB / Downloads: 119)

  Risk_Response_Plan_Template.zip (Size: 374.63 KB / Downloads: 121) ]]> http://www.oraerp.com/Thread-Project-Change-Management-Plan Wed, 08 Jun 2011 10:34:38 -0500 http://www.oraerp.com/Thread-Project-Change-Management-Plan The goals of this Change Management Plan are to:
· Give due consideration to all requests for change
· Identify define, evaluate, approve, and track changes through to completion
· Modify Project Plans to reflect the impact of the changes requested
· Bring the appropriate parties (depending on the nature of the requested change) into the discussion
· Negotiate changes and communicate them to all affected parties.


You can download sample Template from here

  Change_Management_Plan_Template.doc (Size: 60 KB / Downloads: 132) ]]> The goals of this Change Management Plan are to:
· Give due consideration to all requests for change
· Identify define, evaluate, approve, and track changes through to completion
· Modify Project Plans to reflect the impact of the changes requested
· Bring the appropriate parties (depending on the nature of the requested change) into the discussion
· Negotiate changes and communicate them to all affected parties.


You can download sample Template from here

  Change_Management_Plan_Template.doc (Size: 60 KB / Downloads: 132) ]]>