Exam 220-1002 topic 1 question 51 discussion

just in case - SOW means statement of work.

OK, I guess it's back out plan because "The team has already done the network diagrams and knows the locations that will need to be addressed in the project." so it's implied they have already made a plan and the risk analysis should come before the plan. the change board approval is not vital to add so back up plan it is. Otherwise I don't know how to make sense of it.

The project team would most likely add a risk analysis to the SOW. This is because a risk analysis helps identify potential risks or challenges that may arise during the project and allows the team to develop a plan to mitigate them. It is important to include a risk analysis in the SOW to ensure that the project team is aware of the risks involved and has a plan to address them. Plan to change, backout plan, and change board approvals may also be important components of the SOW, but they are not as critical as a risk analysis, which helps ensure the success of the project. While a backout plan is important, it is usually included as part of the implementation plan rather than the SOW.

Documented business processes • Purpose of the change • Scope the change • Risk analysis • Plan for change • End-user acceptance • Change board - Approvals • Backout plan • Document changes This is the order....so why the answer is not change board approvals?

The irony here is that the official comptia texts don't actually define the Statement of Work directly. but the section regarding change management documentation lists all four of the provided choices as items that should be on it. So what does CompTIA want us to answer here? The CompTIA text lists the "backout plan" last, but it is in BOLD lettering, so that has to be the answer. Be smarter than the test.

Searched up what is listed in a SOW. Purpose of the project Scope of work being performed Location of the project, project length, and any work requirements Expected deadlines and deliverables Acceptance criteria Any hardware and software required Performance-based standards to be met Benefits can include: Increased cost savings opportunities Supplier performance and risk mitigation Greater process efficiencies Detailed reporting Project performance management Visibility into all outsourced projects within a single purview Improved workforce management Organisational compliance and risk mitigation https://www.guidantglobal.com/what-is-outsourcing/what-is-statement-of-work-sow#:~:text=A%20statement%20of%20work%20(SOW,and%20payment%20terms%20and%20conditions.

The answer is Backout Plan because a SOW (Statement of Work) is done once majority of the other change management steps have been implemented. It's done towards the end.

Risk Analysis should be the next step after determining the scope

A backout plan is an IT governance integration approach that specifies the processes required to restore a system to its original or earlier state, in the event of failed or aborted implementation.

As safety comes always first i believe that making a Risk Analysis is a must. It is a bigger problem if a WAP gets installed close to a vibrating HVAC duct where it could fall on somebody's head than roll back the change incase someone's phone does not support the 5GHz range.

Back out plan is the most important answer here, IT IS A MUST, in order to move to the next stage. Because if you have a backout plan, you'll probably have the rest done as well.

Documented business processes • Purpose of the change • Scope the change • Risk analysis • Plan for change • End-user acceptance • Change board - Approvals • Backout plan • Document changes Why not go risk analysis first? Backup plan should be the last step, right?

@ Ziberteck, SOW concept falls more under Project Management lingo.

Does anyone know what section this falls under? I never read anything about SOW's in the book I was reading. And it doesn't seem to be listed in the exam topics.

Without the backout plan, if something goes wrong during the change, you have no plan to roll it back to its previous state. At that point, either you take a lot of unaccounted for time to figure out the backout steps (also make the company/client rather angry for not being prepared as well as wasting valuable time) or have to cough up the losses that the company incurred while the system is down...or maybe even both depending on the terms agreed upon for the project. If its an internal job, this could result in termination. Either way, it will definitely be a resume generating event that will haunt your career for a long time.

The Testout program uses purpose of change, plan of change, scope of change, risk analysis, and a backout plan. Wouldnt these all be correct answers? Or why would the backout plan be most needed?