Easy concepts made hard in questions - Tuckman's Model & Maslow's Hierarchy

Don't underestimate easy concepts. They can turn sour and bitter at the exam and unnecessarily take points off your final result. Let's have a look at typical two: Tuckman's Model and Maslow's Theory. They might sound easy but don't take them for granted.

"Stakeholders" tend to associate with certain words

Say you have a rather difficult question about stakeholders. None of the answers doesn't make any sense. Chances are high that it will be the one mentioning "requirements". 

Stakeholders are critical in defining requirements and the 2 terms naturally attract each other.

Stakeholders are also crucial in defining constraints and when you manage them they need to be happy / satisfied.

Just like Birds of a feather flock together so some of the PMI terms tend to be flocked more near one another.

When you Start noticing those, it will help you pass.

Difference between Stakaholder Management Plan and Communications Management Plan

Stakeholder and Communications Management Plans store similar information and telling them from each other can sometimes be confusing.

There is however one clear distinction. Communications Management Plan is more about means of communications and communication models while the Stakeholder Management Plan stresses more about where or why of communication. For instance when you have an issue or problem and you don't know who you should escalate it to and under what circumstances that should happen.

Changing back from Chatter Free Role to Salesforce Role

This article is from the standpoint of Salesforce Administrator.

Once your user is given Salesforce user role, it is harder to change back to Chatter free role. 
(Salesforce role is the one that is given to you as part of your license. 
If you're a large company that has hundreds of Salesforce licenses than this might not be much of a problem.

Think of a "stakeholder" as a "placeholder"

Sometimes questions asking about stakeholders really mean something more specific, they just do't want to give it away thinking they would make things too easy for you.

It's a good idea sometimes to swap stakeholders with something else, like for instance decision-makers. Then all of a sudden the answer becomes a whole lot clearer.

And when you manage stakeholders, you strive for their satisfaction

Example of Agile Requirements Capturing

In software development it is often not until the users have something in their hands, have been shown or given something, some kind of tangible outcome, software, screen with links to a dummy content, etc, before they only begin to realise what they actually need. The requirements are painstakingly being elicited from them and gradually narrowed down to a form that would be satisfactory for their purposes. It might be rather a long process and end users need to be fully involved right from the start of the project.

Selecting Seller by Source Sellection Criteria using DAME

In procurement management it is often necessary to evaluate sellers based on proposals they have sent. Evaluation is crucial for the award decision.
Proposal evaluation is an assessment of the proposal and the offeror's ability to perform the prospective contract successfully. Here is a simplified example how this process can be done with a little known tool called DAME.