PMBOK Cafe is an innovative workshop that explores the best practices of
Displaying items by tag: Bottom Up
Sunday, 04 October 2009 00:00
2009 Summer The Marketing School of Project Management Presentations
Additional Info
- Year_Session_Workshop 2009S1W5
Published in
Marketing School of Proect Management
Sunday, 04 October 2009 00:00
2009 Summer The Marketing School of Project Management Presentation Bottom-Up Approach
Informal Bottom-up Approach to Managing Change
Scenario
As a Project Manager. You analyzed the Scope Requirements of your customer. Based on your previous projects your team concludes, The project cannot meet the requirements that the project will be in jeopardy. You are going to propose changes. How will you communicate/market to the Customer your Proposed Changes to the Scope of the project
Informal / Bottom-up Approach
Introduction
Informal / bottom-up aproach can be used to make your customer listen your opinion in a crucial moment.
Sometimes project members know better about requirement than customers. Occasionally, PM have to convince their needs for requirement changes.
Your project members noticed the project will be in trouble. You have to make your customer agrees to your proposal of requirement change.
Your customer always listen your opinions, and your need for a requirement change is always accepted.
Make your customer on your side! Use grassroots approach.
1) Bring more customer side people on your side. 2) Choose the right person and right way to communicate. 3) Prepare more data to emphasize and backup your opinion.
Body
1. Building up consensus
?Gather general working level opinion and organize them
ex) In North Korea abducion matter, family members of abducted people united together and apealed strongly the need for
political action by Japanese government on street so that the public opinion become sympathetic as politicians could not ignore.
?Make the project visible and open to customers.
2. Finding key person / technique
?Find the person having large influence on decision making.
?Adjust the perspective with the expertize of the key client.
3. Justifying with proof
?Bring the expert who knows deep about the same kind of problem with the one you are confronting now.
?Constantly collect data showing progress and achievement of the project.
Try to make atomospher that various stakeholders trust you and back you up.
Conclusion
Roadmap : 1) Bring more customer side people on your side. 2) Choose the right person and right way to communicate. 3) Prepare more data to emphasize and backup your opinion.
Sometimes project members know better about requirement than customers. Occasionally, PM have to convince their needs for requirement changes.
Your project members noticed the project will be in trouble. You have to make your customer agrees to your proposal of requirement change.
Your customer always listen your opinions, and your need for a requirement change is always accepted.
Make your customer on your side! Use grassroots approach.
Need for requirement change could happen to everybody. Don't afraid and face it!
Additional Info
- Year_Session_Workshop 2009S1W5
Published in
Marketing School of Proect Management
