Available:*
Library | Call Number | Status |
---|---|---|
Searching... Hardwood Creek Library (Forest Lake) | 658.404 MOR | Searching... Unknown |
Bound With These Titles
On Order
Summary
Summary
Project management is one of the fastest-growing occupations in the world. The Project Management Institute has seen membership growth of more than 1000% in the last 10 years. But while many of these managers know how to plan a successful project in theory, very few have the practical tools needed to navigate the politics of today's corporate world. Project managers need more than just technical skills; they need the right communication skills to succeed. Filled with real-world examples, Project Management That Works gives readers the tools they need to: communicate with their team as well as stakeholders - get their teams to function well - run fewer and more productive meetings - turn around failing projects - utilize data properly to make emotional conversations unemotional - know when a project is really done The only book that addresses thereal challenges project managers face today, this is an accessible and invaluable tool that will show every reader how to accomplish his mission-no matter the obstacles.
Author Notes
Rick A. Morris (Hoover, AL) is a project manager for several Fortune 500 companies and is a sought-after public speaker on project management.
Brette McWhorter Sember (Clarence, NY) is an attorney who has written more than 30 books including The Essential Supervisor's Handbook .
Excerpts
Excerpts
CHAPTER 1 UNDERSTANDING YOURSELF There are a tremendous amount of business and leadership books on the market. Some of them will have a profound impact on the reader's life, but some can be dangerous as well. For example, a new manager, Keith, brought in a star employee (and current friend) for an impromptu coaching session. Keith had been watching his friend and noting several things in his life. In Keith's observations, he saw the employee start tasks (even personal goals) with great vigor and excitement, but noted he never seemed to follow through. Keith had just finished reading a book on how to motivate employees and was excited to apply what he had just read. He thought that all his staff needed was a conversation to light a fire under him so that he could follow through on the activities he had started. He wanted to discuss the employee's failure to finish projects at home as well as on the job. Keith launched into a monologue about how he had watched the employee start a weight-loss program, brag about how much weight he was losing, yet it looked like he had quit the program. He had also heard the star employee talk about working with a charity, but hadn't heard any updates. Keith announced that he was concerned about the employee and felt he needed to learn how to finish what he had started. The conversation focused only on outside activities, not work-related items. Later, after thinking about their discussion, the employee marched back into the office and angrily said that Keith didn't know what he was talking about. Yes, the employee had started a weight-loss program, but it required weekly office visits, which the travel requirements for his current position prevented him from attending. He had also started working with a charity, but due to work demands had to leave, but none of that had anything to do with his work. In fact, the new manager didn't mention it at all and just seemed to be complaining about a general failure to finish things. The employee said he was upset at the approach the manager had taken to discuss this, especially because they were also friends. Keith was stunned, but after he thought about the situation, he replied, "I'm sorry. I've been reading a new book on employee motivation, and I guess I didn't apply the concepts very well." Keith was so eager to apply the points in the book that he failed to take several points into consideration. These issues included understanding why the employee had stopped some of the outside activities, what the current relationship was between the employee and manager, and the fact that his friend had never had a conversation like this with him before. Keith also failed to consider that as a supervisor, it was not appropriate for him to criticize choices in his employee's personal life, even if he thought he was being helpful. He failed to bring the conversation around to any work-related issues. Another manager, Juanita, went to visit a profound and world-renowned speaker. The advice offered was very straightforward and tough. It was a great approach, however, it was not one that Juanita could see herself using. For instance, when seminar attendees asked how to motivate someone, the speaker would state, "You just tell them to do it. If they don't, you take disciplinary actions." When asked how to deal with unrealistic project completion dates, the speaker said that you just reset them. It was an almost arbitrary or matter-of-fact statement. When Juanita dug into the speaker's theories and background, she realized that he had been a high-level manager at his former company. He had instant authority in his position. Juanita was in an environment where she did not have the same authority. She could not apply his principles because she did not share the same authority level or personality type. She could not employ the "do-it-because-I-said-so" communication type. She had almost no authority at all. She was hoping to learn how to influence teams to perform, not order them around arbitrarily. These scenarios demonstrate that until you know who you are and how you react to a situation or event, you cannot possibly coach someone else in any effective manner. You are also less likely to craft a proper message that will be meaningful for them. Could the new manager have been more effective had he approached the coaching session with concern versus straight motivation? Can the seminar attendee find the core of the speaker's message and apply it to her environment? Communications are based on senders and receivers. Each shares responsibility for the communication. Understanding yourself (and your weaknesses) allows you to compose a more complete message by knowing your communication strengths and utilizing them properly. It has been said many times that people's strengths are also their greatest weaknesses. One manager's strength might be that he can process information quickly in his head. The weakness is that sometimes his mind is processing information before the conversation or event is over, causing him to lose the intensity with which he usually listens, or causing him to miss some key information. Another manager's strengths might be a passion for project management and for life. The resulting weakness might be that he or she can be overexuberant or even quick-tempered. It is important to be able to identify these traits in ourselves so that we can learn to manage them and optimize our skills, while downplaying or compensating for our weaknesses. It is only once we are able to manage ourselves, that we have any hope of effectively managing others. Great managers take the time to understand how they will react in a situation and are honest in their evaluations so they can then learn to control and mitigate their weaknesses. When something bad happens and a manager with a quick temper can feel and recognize that inner fire in his chest, he can learn to take a deep breath and control his tone of speech. When a manager hears an update and someone is talking, he or she can wait to take notes until after the speaker is finished. Waiting to do this creates a fear that they might forget a point, and makes him or her concentrate harder and listen more intently than if he or she was taking notes throughout the entire discussion. ■ DISC Profile The DISC profile was created by William Moulton Marston (Mr. Marston also created the first functional lie detector and the Wonder Woman comics). As the DISC profile has evolved, it has taken on many meanings, but for purposes of this book, we will use Dominant, Influencing, Steadiness, and Conscientious. The profile tests your personality characteristics and places you into one of the categories. Understanding which category you and your employees are in can help you become a better manager (Chapter 2 discusses how to use this profile with your team). Here is a much scaled-down version of this test. For one that's more detailed, you can take a variety online. Whatever you do, take it (Table 1-1). Please circle the description in each line that best describes you. Now count the number of answers in each column. Column 1 is D. Column 2 is I. Column 3 is S, and column 4 is C. Whichever column has the highest score is your dominant personality type. There is a brief description of personality types in Table 1-2. Excerpted from Project Management That Works: Real-World Advice on Communicating, Problem-Solving, and Everything Else You Need to Know to Get the Job Done by Rick A. Morris, Brette McWhorter Sember All rights reserved by the original copyright owners. Excerpts are provided for display purposes only and may not be reproduced, reprinted or distributed without the written permission of the publisher.
Table of Contents
List of Tables and Figures | p. xi |
Acknowledgments | p. xiii |
Introduction | p. xvii |
Chapter 1 Understanding Yourself | p. 1 |
DISC Profile | p. 4 |
Fostering Communication | p. 7 |
Responding to Types | p. 7 |
Working Through Weakness | p. 9 |
Chapter 2 Communicating on All Levels | p. 11 |
Determining Sponsor Styles | p. 12 |
Delivering Information | p. 13 |
Crafting the Message | p. 14 |
Team DISC Profiles | p. 16 |
Adjusting the Message | p. 17 |
Proper Communications Management | p. 20 |
Communications Documents | p. 21 |
Chapter 3 Be Trustworthy | p. 27 |
Coping with Questions | p. 28 |
Qualifying the Question | p. 29 |
Don't Lie! | p. 30 |
Dealing with Fear | p. 31 |
Admitting You Are Wrong | p. 32 |
How to Fix Things If you Haven't Told the Truth | p. 36 |
Sometimes It Can't Be Fixed | p. 37 |
Chapter 4 Turning Around Failing Projects | p. 41 |
How to Spot a Project That Is on Its Way Down | p. 42 |
Someone Isn't Being Heard | p. 43 |
Watch the Ego | p. 46 |
When It's Wrong, It's Wrong | p. 47 |
Stopping a Project Before It Starts | p. 48 |
"It Is What It Is" | p. 51 |
How to Assess the Current Situation and Create an Action Plan That Works | p. 54 |
Chapter 5 Defining the Word Done | p. 57 |
Definition of Done in Project Management | p. 57 |
Team Building with the Word Done | p. 59 |
How Done Can Set Proper Expectations | p. 60 |
Lack of Historical Information | p. 61 |
Creating Lessons Learned | p. 62 |
Chapter 6 Application of the Iron Triangle (Triple Constraint) | p. 65 |
What Is the Iron Triangle? | p. 65 |
Why the Triangle Works | p. 66 |
How to Implement the Triangle | p. 69 |
Use the Triangle for Discovery and Scoping | p. 70 |
Why the Triangle Shouldn't Be Used for Project Success | p. 72 |
Chapter 7 PERT Methodology in Project Planning | p. 75 |
What Is PERT? | p. 76 |
PERT for Time Estimation | p. 78 |
How to Factor Risk into the Equation | p. 79 |
Create a Work Breakdown Structure for PERT | p. 80 |
Examples of PERT in Action | p. 82 |
Chapter 8 Customer Focus Starts with Great Requirements | p. 87 |
Characteristics of Good Requirements | p. 88 |
Functional Requirements Versus Technical Requirements | p. 90 |
Who Is the Real Customer? | p. 92 |
Work Breakdown Structure Dictionary | p. 93 |
Chapter 9 Do Not Sacrifice Your Team at Any Cost! | p. 95 |
The Importance of the Team Relationship | p. 96 |
How to Build an Effective Team Relationship | p. 96 |
Internal Team Satisfaction | p. 99 |
Team Building and Conflict Resolution | p. 100 |
100 Percent/10 Percent Rule | p. 101 |
How a Team Can Become Overburdened | p. 103 |
Interacting with Requestors to Avoid Overburdening | p. 105 |
Dealing with Mandated Dates | p. 106 |
Chapter 10 Myths About Status Meetings | p. 111 |
Understanding the Purpose of Meetings | p. 112 |
Should There Be a Meeting? | p. 113 |
Are Your Meetings Effective? | p. 114 |
Setting Up a Successful Meeting | p. 116 |
Important Rules for Meetings | p. 118 |
How to Get a Meeting Back on Track | p. 119 |
A Big Meeting Faux Pas and Myth | p. 120 |
The Team Morale Killer | p. 121 |
How to Close a Meeting Successfully | p. 121 |
Chapter 11 Patriots and Scuds | p. 125 |
Dealing with Patriots and Scuds | p. 125 |
Understand Your Own Missiles | p. 127 |
Understanding Missiles | p. 128 |
Using Patriots | p. 128 |
Using Scuds | p. 128 |
Missiles in Public | p. 129 |
Missiles in Corporate Culture | p. 130 |
Always Have an Escape Strategy | p. 130 |
Chapter 12 A Real Risk Assessment | p. 133 |
Why Risk Is Important | p. 133 |
The Risk Process | p. 134 |
Why People Are Opposed to Risk Management | p. 137 |
Dynamic Risk Assessment | p. 138 |
The Beginning of the Transformation | p. 141 |
The Evolution of the Risk Assessment | p. 142 |
The Final Product | p. 145 |
Involving the Team | p. 148 |
Chapter 13 How to Put Risk in a Project Plan | p. 151 |
Thirteenth Floor Principle | p. 152 |
Parkinson's Law | p. 153 |
Murphy's Law | p. 154 |
Putting Risk in a Project Plan | p. 155 |
Presenting Risk to the Sponsor | p. 160 |
Presenting Risk to the Team | p. 161 |
Using Risk | p. 161 |
Chapter 14 Data Rules All! | p. 165 |
Collecting Data | p. 166 |
Mining Data from Lessons Learned | p. 170 |
Making Emotional Conversations Unemotional | p. 171 |
"Drop Everything" Does Not Mean Drop Everything! | p. 174 |
Using Data in Conflict Situations | p. 175 |
Countering Data That Is Harmful to the Project | p. 181 |
Chapter 15 Project Manager: The Strategic Resource | p. 183 |
Needing the Data | p. 184 |
Strategic Positioning of Project Management | p. 185 |
What CIOs Need to Know | p. 186 |
What PMs Need to Provide | p. 187 |
Software Assistance with Governance | p. 188 |
The Proactive Approach | p. 189 |
Chapter 16 Making Positive Change to Your Corporate Culture | p. 193 |
How Corporate Culture Affects Project Management | p. 193 |
Understanding and Analyzing Corporate Culture | p. 198 |
What to Do When You Can't Change or Affect Corporate Culture | p. 200 |
How to Obtain Executive Sponsorship | p. 202 |
What to Do When Executive Sponsorship Is Not as You Hoped | p. 204 |
How to Get Your Sponsor Motivated and Interested in Your Project | p. 207 |
Chapter 17 Conclusion | p. 209 |
Glossary | p. 211 |
Index | p. 213 |
About the Authors | p. 219 |