Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
45 Cards in this Set
- Front
- Back
5 Stages of Group Development or Formation
|
Forming
Storming Norming Performing Adjouring |
|
Selection Process
|
What are the internal and external sources?
How do we select? How do we provide career development in PM? How can we develop PM skills? Prioritize Projects |
|
How do you create a project to present to the board?
|
Have an idea
Go to an executive Write a business case Get it Approved Assign the PM PM and the executive need to sign the Charter Create exact PM plan RTM - Requirements Traceability Matrix |
|
Charter
|
Create the plan
-Risks -Contingency plan -Recourses |
|
ROM
|
Rough order of Magnitude
|
|
Requirements Traceability Matrix
|
ROM
Testing designs to make sure all the requirements are met |
|
Forecast vs Actuals
|
Forecast
-What you think is gonna happen Actuals -What actually went down |
|
Expectancy Theory
|
VROOM
Mazda Can I do it? If I do it, will it equal a reward? Is the reward worth it? |
|
5 Imperitives
|
-The time span b/w project initiation and completion appears to be increasing.
-The capital committed to the project prior to the use of the end item appears to be increasing -As tech increases, the commitment of time and money appears to become inflexible. -Tech requires more and more specialized manpower -The inevitable counterpart of specialization is organization ***These identify the necessity for more effective planning, scheduling, and control. |
|
The Project Mgmt Stool Legs
|
Schedule
Functionality Cost Quality *Must be optimal length (a cutdown in the cost will prolong the schedule) |
|
Isolated and Operational Islands
|
Line Managers are vertical
PMg are horizontal *Triangle |
|
PMg Responsibities
|
-"Negotiate" with all functional disciplines for accomplishment of the necessary work packages within the constraints of the Stool
-Resolve conflicts -Produce the end-item with the available resources and within the constraints the Stool -Meet contractual profit objectives -Make all required decisions whether they be for alternatives or termination -Be the comms focal point for customers and mgmt |
|
Most Likely Cause of Project Failure
|
Risk Mgmt
|
|
Concept through Project Initiation
|
Conceptual
Planning Testing Implementation Closure |
|
Project Mgmt Maturity
|
The implementation of a standard methodology and accompanying processes such that there exists a high likelihood of repeated success
|
|
Hierarchical Mgmt
|
Layers
Priority Inheritance Cons: Communication is difficult Slow Only addresses symptoms, not root problem Pros: Well known Chain of Command Expectations are known Strategic Objectives are defined Responsibility is known (control) |
|
Matrixed Mgmt
|
Small, independent groups work on separate projects
Agile development Flexible Smaller companies Each project is its own entity Opposite of Hierarchical Mgmt |
|
Hybrid Mgmt
|
Traditional Hierarchical Org with "pop out" project teams as needed
|
|
Emerged vs Appointed Leaders
|
Appointed
-PM, Manager, Executive (usually wins) Emerged -Knowledge about the project and people go to them |
|
Define a Project
|
-Have a specific objective to be completed within certain specifications
-Have defined start and end dates -Have funding limits (if applicable) -Consume human and nonhuman resources (i.e., money, people, equipment) -Are multifunctional (i.e., cut across several functional lines) |
|
Strategy Development and Alignment
|
Too many people involved in Decision Making
|
|
Resolving Conflicts Modes
|
Withdrawal
Smoothing Compromising Forcing Confrontation |
|
Authority vs Accountability vs Responsibility
|
Authority
-the right of an individual to make the necessary decisions required to achieve his objectives or responsibilities Responsibility -The assignment for completion of a specific event or activity Accountability -The acceptance of success or failure |
|
Types of Power
|
Penalty
Expert Referent Legitimate Reward |
|
Expert Power
|
The ability to gain support because personnel perceive the pm as possessing special knowledge or expertise (that functional personnel consider as important).
|
|
Penalty Power
|
The ability to gain support because the project personnel perceive the pm as capable of directly or indirectly dispensing penalties that they wish to avoid. Penalty power usually derives from the same source as reward power, with one being a necessary condition for the other.
|
|
Legitimate Power
|
The ability to gain support because project personnel perceive the pm as being officially empowered to issue orders.
|
|
Reward power
|
The ability to gain support because project personnel perceive the pm as capable of directly or indirectly dispensing valued organizational rewards (like salary, promotion, bonus, future work assignments…)
|
|
Past View of PM
|
Requires more people and add to the overhead costs
Profitability may decrease Increase amount of scope changes Organizational instability and increases conflict "Eye wash" for the customer's benefit Creates problems Only good for Large projects Increase in quality problems Creates power and authority problems Suboptimization by looking at only the project Delivers products to customers Cost of product drives down competitiveness |
|
Current View of PM
|
Requires less people and does not add to overhead costs
Profitability will increase |
|
Engineering and requirements
|
The work done and the standards that work is held too
|
|
Negative/Destructive Roles on a Project
|
Aggressor
Dominator Devil's Advocate Topic Jumper Recognition Seeker Withdrawer Blocker |
|
Aggressor
|
Criticizes everybody and everything on a PM
Deflates status and ego of others Always aggressive |
|
Dominator
|
Always tries to take over
Professes to know everything about PM Tries to manipulate people Will challenge your leadership |
|
Devil's Advocate
|
Finds fault in all areas of PM
Refuses to become a believer unless threatened More Devil than Advocate*** |
|
Topic Jumper
|
Must be the first with a new idea/approach for PM
Continuously changes topic Cannot focus on issues for a long time unless its theirs PM Implementation remains in "Action Item" forever |
|
Recognition Seeker
|
Always argues in favor of their own ideas
Very status conscious Volunteers to become PM if status is recognized Continuously talks (Likes to hear themselves talk) Often boasts rather than providing meaningful info |
|
Withdrawer
|
Afraid of criticism
Will not participate openly Withholds info May become a backstabber Or may just be shy... you'll never know until its too late |
|
Blocker
|
Likes to criticize
Rejects the views of others Cites unrelated examples and personal experiences Has multiple reasons why PM will not work |
|
Out of Control Matrix
|
-Tends to makes exects want to revert to Classical Mgmt
-Reduced Authority for PM -All project decision making is taken to the executive level -Increase in executive meddling in projects -Creation of endless job description manuals |
|
Leadership Factors
|
???
|
|
Definition of Success
|
Within Time
Within Cost Within Quality Accepted by the Customer |
|
Communication Channels
|
Lateral Comms to friends, social groups, and both formal and informal orgs
Lateral Comms to associates and the Project office Lateral Comms to functional group and customers??? |
|
Communication Encoding Barriers
|
Comms goals
Comms skills Frame of reference Sender credibility Needs Personality and interests Interpersonal sensitivity Attitude, emotion, and self-interest |
|
Communication Decoding Barriers
|
Evaluative tendency
Preconceived ideas Comm skills Needs Personality and interests Attitudes, emotion, and self interest Position and status |