BUS 4017 PROJECT MANAGEMENT – Class Data Base Instructor: Prof. Fred Pentney. Wk. 4 Suppl. P. 4 The purpose of this exercise is to identify the different types of stakeholders who influence a project. Each one has a different reason for being part of the project. Action for each SH shown by the indent. Our class has been divided into five types Stakeholders. You need to be know five types. There is an action step described for each type of S.H. Project Managers - who have an objective in getting this project completed, on time, on budget with all the information distributed to the: PM. Set a time for the Project and gets your teams working on ideas of how to gather and collate the data. Assign the people who will assemble and distribute. Customers - who happen to also be the end users in this case? Stakeholders can have more than one role on a project. Some of the customers are also Team Members. Try and get a confirmation on time you get the info. and any disruption to your schedules of learning today. Team members - who have to present ideas of how to complete this project to the Project Manager. Other team members will be asked to do the work of collecting the information and assembling and distributing it. A Sponsor in the class will try and diffuse any conflict that develops. He/she will work closely with the Project Manager. Go and make the peace. Functional managers in the Class represent Geo. Brown and are against this project being developed from a cost and risk perspective. The customers feel it is worthwhile. The Project Manager needs some of the Geo. Brown resources to achieve the objective and needs to get the support of management. Try and convince the Project Manager and customers this will cost them and there are risks as discussed in class last week. First name Last name Email Phone Strengths Skill Interests Causes

Review the Group Data base project.

Identify clearly the five types of Stakeholders. The Customer, Project managers, Functional managers, the Sponsor and the Team Member. Then make sure each Group knows its initial (hi level) tasks and responsibilities. Ensure clear lines of communication are established. Then set the rules for the project. Establish a Statement of Work - make it a contract if necessary.

Clearly read the Instructions. Management and Team Memeber's (Students) were quite justifiably concerned about providing their phone # and Email. The instructions clearly indicated the number would not be published. However, the issue served the purpose of generating opposing points of view which is typical on a project. How could this have been handled?

Here are few of the learnings. Remember project management is both process (science) and people (art).

Process (SCIENCE)	People (ART)
Carefully read instruction on all documents. This might be the R.F.P., the proposal or the S.O.W or all three.	Check if documents have been read and understood by all the Stakeholders. Get acknowledgment.
Post the Rules, time lines, budgets for all to see. Post a Responsibility Matrix.	PM's go and get management support for the project from TEAM Memebers and Management, contractors if any.
Establish the purpose and method of completing the project. Decide on functionality and specifications.	PM's ask for input and ideas from all the Stakeholder's. Team members usually have the best ideas because it is they who do the work.
Set the levels of quality and the tools and methods to get that quality. Again get input from all the Stakeholders.	PM's quickly establish communications methods, time frames and objectives.
Get some people working on Risk Management early in the process.	Team member get clarification on time lines and other responsibilities.
Remember the action plan for a successful project. Get management support, agreed upon goals, a plan, control the scope and good communication.	Management don't hold back resources or the project is jeopardized and the Customer gets upset. Contribute ideas of how to make the project a success.
Always do a lessons learned.	Sponsor keep in touch with management and PM. Only go to the Customer when really critical. Would you go to the TEAMS? Maybe to encourage but not get involved in the management aspects. TEAM members already have two sets of bosses, they don't need a third.