Hello and welcome back to the company. A project plus B k +0004 This is your instructor, Roberto Hilario. Now that we have reached the end off the module, let's do a quick review with five short questions.
While the challenges to the communication when dealing with international collaboration in here, we have to choose all that apply less know through the choices
1st 1 is time zones. Definitely. Time zones do percent a challenge when he comes to international collaboration.
Cultural differences indeed. Different cultures, percent different ways of approaching and addressing and communicating with each other.
So let's look at the 3rd 1 language barriers.
not being able to communicate in a neutral, proficient, managed language is gonna be a challenge of will
technology. Yeah, technology could also be a challenge. What if the platform or the service we are using our counterparts in the other side of the world is nothing miller with Or maybe the service is not with the same quality that we experience here,
So that could be a barrier, a swell
and also enter organizational differences. This is our also true statement.
Different organizations different components of the organization deal with authority and with communications in different ways. So
it seems to me that all these choices could be valid.
well, the correct absolutely all of the above communications across regions can be obstructed by several reasons. And these five are the typical reasons. Let go on to our second question.
the team are arguing over two different approaches to complete the task.
You listen to the side and direct them to use a different option. What type of resolution was this?
Well, the fact that you provided a solution that was not one of the ones they suggested. It seems that it was forcing because avoiding will try to find out a median middle ground between the two choices.
Smoothing will try to diminish the problem, and compromising will also try to find some middle ground as well.
So the answer is a avoiding
because one viewpoint, your viewpoint in this case was pushed four. Despite the resistance from the rest,
let's look at the third question
when a change request is introduced. What is the first thing that should happen? Well analyzed for phys ability,
apt to the change request Logan assign a tracking i d.
Examine it To terminate the requester is a valid stakeholder folder project,
or notify the project sponsor
on a lesson for a feasibility might be valid. But it's too early because it's just a change request. It doesn't mean it has been approved or has Bean evaluated
to be considered. That doesn't sound the right one.
After the change request Long and assign a tracking I D. That sounds more appropriate because we're never request it's introduced issue be documented and identify
So they're adding into the request law. And assigning an I D. Sounds appropriate.
Examined to the terminal of the requester is a valid stakeholder for the project.
Anyone that has an investment in the project is a stakeholder that we know already,
and in this case, we cannot deny the opportunity to suggest toe somewhat that previously have not being identified. A stakeholder.
Maybe at that moment we were not in form or we don't did not have enough,
documentation to consider them as a stakeholder. But there's a possibility that someone that has a late investment may pop up and the request will can never be should never be turned out.
Last choice is notified. The project sponsor.
I don't think the project sponsor wants to be doing with this type of minutia, especially that he's not looking for the details on the house. He just wants to help us move through the project and achieve the goals we have established.
So out of the four choices, I will go with Choice B.
Well, correct change request should be assigned a number for tracking purposes when documenting.
Let's look at our next question.
What plans should a team have in place in case a change that's not go according to
Reverse change management or regression
Rollback Sounds logical. Kind of gives me
the idea that it could be possible. Roll back. We've seen this in Microsoft operating systems when you would only stole a driver, the or go back to a previous version of a driver is called a driver. Roll back
reverse doesn't sound like a term we've seen before. Change management.
Um, it's the overarching,
so it shouldn't be that regression. Okay, regression. He's also probable. What will be the difference between regression and roll back?
The rollback just resets where it's a regression
evaluates how the change back affects the world that has been done to that point.
So the answer is Russian because it gives the ability to reverse a change
at the same time looking into what other areas would be affected.
What kind of document would we use to solicit goods or service is from outside partners?
This one is easy. We just need to know what each off these initials mean.
Request for proposals
revolutions for a minute.
Requests for quotes, a request for information.
So definitely rpm doesn't seem to be something we've seen in project management, maybe in our cars, but not in project management.
When you are soliciting goods,
we have requests for proposals, requests for quote requests for information so information we don't solicit goods, so quotes and proposals would be the closest ones. What do we remember? The differences
Quotes is too about to see the cost, whereas proposal is to see the actual engagement.
Because in this this level, as we said, we are procuring the service, So request for proposal is the correct answer.
Well, that's it for now. Thank you so much. And I'll see you in the next module