Config Management and Conflict Management

Hi, I have read the above two topics in pmbook, andy, and looked online. Still my fundamentals are not clear. Can you suggest any place where i can read more.

I understand each conflict resolution technique but still when i am applying my knowledge to questions, i am getting wrong answers. I get confused between compromising and smoothing and collaborating :(

I know config management is to manage product related changes and baseline changes, right ? and change control is more related to changes other than baselines and product, its more aboutchanges to project activities, right ?

Please explain or provide links to more reference.

 

Thanks,

Shweta 

 Compromising - it is lose lose for both as both has to compromised and give up something.

Smoothing  means downplaying the issue or focusing only on the positive. It's really hiding from the problem, and it doesn't address the problem or even acknowledge that the problem exists. Smoothing can be used to buy time or when one party believes the stakes are low and giving a "win" on this issue may be used to create an obligation later. Smoothing can often be seen when one party gives in by saying something like “Well, it’s not important anyway, so you choose.” 

Collaborating means working with other people to make sure that their viewpoints and perspectives are taken into acount. It’s a great way to get a real commitment from everyone. So when solving a problem required suggestions or feedbacks from multiple people of group, collabarating is used.

Your config management cocept is correct..

-Abhishek, PMP

admin's picture

For configuration management, search on PMZilla you will find some good material and explaination.

 Thanks, search on pmzilla pointed me to deepfiredbrain, where i found many more interesting articles.

 

Shweta

The alternatives chosen should be those in the popular places , for example in Quality Control, Venture Control, or Fund.nvq level 3 in management