Project Management 2.0


Home  >  gantthead blogs
about this blog RSS

recent posts
   Do You Need a Project Management Survival Plan?
   Do You Need a Delegation Document?
   T- shirts Seem to Be All the Rage
   Do You Need a Team Operating Agreement?
   Is Your Team Really a Team?

Project Management 2.0

  by - Dave Garrett

New technologies, concepts, and Web 2.0 tools are popping up everywhere. How can you use them to help your project team collaborate, communicate - or just give your project an extra boost? [Contact Dave]

View Dave Garrett's profile on LinkedIn Add to Technorati Favorites Add to NetvibesGet this widget from Widgetbox

Advice | Certification | Collaboration Tools | Decision Making | Estimating | Interviews | Learning | Management Approaches | New Templates | Personal Productivity | PM Software | PPM Software | Presentation Tools | Reporting Tools | Requirements | Research | Risk | Scheduling Software | Security | Team Building | Techie Tools | Time Killers | Time Tracking Software | Training | Virtual Team Tools | Web-based Tools

older posts

Do You Need a Project Management Survival Plan?
categories: Advice, Interviews, Management Approaches

Situation: You need a fresh perspective on Project Management in general.

 

Steve Starke, VP of Program Management at Thomson Reuters, has written a new PM book entitled, S.T.O.P. The Project Management Survival Plan which outlines a new framework for managing projects based on survival principles used by many of our armed forces divisions in the United States. The book offers an alternative to the classic triple constraint triangle.  Instead he suggests that we focus on managing value, team performance, and communication.  We asked him for a few specifics in the interview below…

 

Dave: How did you come up with the idea of applying survival principles to project management?  Surviving is about achieving a minimum threshold –presumably in a difficult environment.  Are you taking a project view that says, "achieve the stated goal and no more?" (I.e. - stay entirely within scope) 

Steve: A key to surviving many of life’s situations involves mental toughness. Essentially, knowing how to think through a problem and develop action plans. If you think about your project as a survival mission in which it’s your responsibility to save and lead members of your team to safety, you may change your approach to managing your projects. You may start to understand your team members better: their strengths, weaknesses, and the environment in which they perform best. You may also have a new sense of urgency considering what’s on the line. Many times on survival missions you only have one shot to get it right. You could say the same thing about planning and managing a project. If you don’t get it right up front, you may find yourself and the team in front of the CEO explaining the failure, missing customer expectations, and hurting your career. With the role of the project manager, there’s a lot at stake and no room to take chances. Corporations are counting on project managers more than ever.

Dave, the view I am taking is that project managers, especially those involved with developing new and innovative products, must be mentally tough! Project Managers must mentally train themselves to think through alternatives before tackling any of them. As critical situations develop during a project, the project manager needs to physically stop and think to consider all their options. Next, they need to observe their environment and consult with their team members to determine the best plan of action - thinking through how the plan is going to be accomplished.

A project manager must also know when to recommend stopping the project. Stopping isn’t something a lot of organizations do well. In a recent study, the Accept Corporation and the Association for International Product Marketing and Management (AIPMM) found that more than 60 percent of executives say they struggle making kill/ go decisions. There is a tendency to continue projects and activities even when most people involved realize it’s not an optimal use of their time.

The S.T.O.P. principles were designed to ensure that critical thinking occurs in high pressure situations (sound familiar?). I have taken those same principles and constructed a framework for project management. Giving the project manager guidance and direction on what that minimum threshold should be for being successful if their project is viable – and if it’s not viable, then what it takes to stop it!   

 

Dave:  When we thing of managing scope, schedule, and cost we are really balancing those things against on another in many ways. In your version of the triangle, do you see project managers needing to balance value, team performance, and communication?  How does that work?

Steve: If project management is to survive as a profession, then we as project managers need to realize that our job is more than just managing scope, schedule, and cost – it’s about delivering value. The iron triangle still exists; don’t get me wrong. But to truly be effective as a project manager I believe a new triangle must emerge. A triangle based on managing value, team performance, and communication. I developed equations in the book to help identify and quantify the variables where more focus and management need to be applied on our projects.

Let me give an example on how this works in regards to determining and managing project value:

You’re raised as a project manager with a visual implanted in your head of a triangle that flexes and constrains as you move through your project. You force your sponsors to make decisions and tradeoffs against the three (scope, schedule, and cost), but based on what? The answer should be value. When creating, developing, and delivering a product to the market, you seek to maximize its value. You want to maximize the customer benefit and experience while maximizing the return on investment. When you adjust your perspective around the triangle like this, you realize it’s more of an equation based on deriving value. I call this the project management value equation. It’s designed to give context to “scope, schedule, and cost,” ensuring that you’re weighing all that you do against the overall value of the project and keeping your sponsor and team focused on the prize. Said another way, it’s an equation meant to quantify and assess the value of a project and identify — if value has been decreased — whether the project should be stopped. The equation is the following:

Value = Scope ÷ (Schedule + Cost)

By understanding this concept, you bring more depth and meaning to what you really need your sponsors to trade off against. By assigning a value to each of your success criterion, you in essence are quantifying the value of the project. Increases to schedule and cost will decrease the value of the project if more scope is not being delivered to offset it. Ensure that your scale for scope, schedule, and cost are the same. Assigning either a percentage value or using a 1–10 scale can work if each variable is quantified consistently. The idea is that, at the start of the project, as you determine its overall value, it should equal 100 percent. As tradeoffs are made between each of the three variables, the project value will change. Together with your sponsor, determine what the threshold value is for stopping your project.

 

Dave:  Can you give us your top 3 tips for understanding and creating value on projects? Which tools do you apply and why are they important?

Steve: You bet, they are the following:

  1. Stop before you rush into any project. Take the time to understand the project’s success criteria.
     
  2. Think about each success criterion and ensure that it’s understandable, measurable, and achievable by the project team, stakeholders, and sponsor. Understand who is going to benefit from what aspects of the project and how they’re going to measure them. Tools exist in the book to help create and assess completion of project success criteria.
     
  3. Create a project tradeoff matrix. The project tradeoff matrix documents the options available when critical tradeoffs must be made between scope, schedule, and cost when weighed against overall value. This matrix captures stakeholder guidance as you control the project through execution. It will serve as your compass, directing you as you balance and manage your project.

 

Dave: Can you give us your top 3 tips for managing team performance on projects? Which tools do you apply and why are they important?

Steve:

  1. Creative disruption is a method to stop or disrupt the monotony of the everyday and introduce small, incremental changes that keep the team challenged and fresh. Just because something worked for a team on a prior project doesn’t mean it will work on the next project. Keep the team on their toes and in a mode of constant, critical thinking. Your project results and team dynamics will dramatically improve as this technique prevents stagnation and complacency.
     
  2. Observe the differences in backgrounds, perspectives, and functional priorities that exist amongst your team. Managing team construction and dynamics are a part of your job. They’re counting on you to guide them through the project by reducing the risk of interpersonal conflict. Social bonding, Team identification, Team orientation, and formal Planning are the ingredients to team integration and performance.
     
  3. Plan to capitalize on team dynamics and integration by understanding the three C’s of your product development lifecycle (conceive, construct, and commercialize) and knowing when to increase communication based on time and team function.

 

Dave: Can you give us your top 3 tips for ensuring effective communication on projects? Which tools do you apply and why are they important?

Steve:

  1. Plan your project. A project schedule isn’t a project plan! A project schedule is a tool used to manage a plan. Create an integrated project plan designed around market/product needs and project outcomes. Do this and you’ll turn your plan from one that is inwardly focused to one that ultimately meets customer needs and ensures that all the project work yields the outcomes your organization expects.
     
  2. To truly do that full robust planning, you need to establish a responsibility assignment matrix, commonly called a RACI (Responsible, Accountable, Consulted, and Informed) matrix before you start to build your project schedules. The RACI matrix describes the roles and responsibilities of various teams or people involved in developing and delivering a product. It should also include your stakeholders and any extended team members needed to deliver your project. Like the project tradeoff matrix, the RACI matrix can be used as a stop sign for your project. If you don’t have the right accountability and responsibility mix within your project — Stop! Talk with your sponsor; show them the results, and work with them to get the right team in place. The RACI matrix can also be used to help explain to your executive sponsor and senior leadership just how complex your project is. I’m not saying it’s the silver bullet in getting that message across, but it can help.
     
  3. Develop your communication plan to reduce the risks and decide how to best implement the plan safely and with transparency. Ensure proper feedback mechanisms are put in place so you can monitor how the communication was received and whether you should alter the communication in the future.



| Posted: January 10, 2012 10:49 AM | Permalink | Comments (0) |

Do You Need a Delegation Document?
categories: Advice, Management Approaches, New Templates

Situation: It's unclear which decisions you can take and which ones must be escalated.

Often we begin with a general understanding that the PM can approve expenses within budget and at times there is an approval threshold, but not much more is said about decision-making.  Action-oriented PMs often take a "decide first", ask for forgiveness later approach.  This can work well in the moment, but strain relationships long-term. 

At their best, a good delegation document will:

  • Allow for the best decisions to be made
  • Make management processes more efficient
  • Contain the level of risk associated with each decision

Our version helps you record decision-making authority for the following types of decisions:

  • Matrixed Staff
  • Project-specific staff
  • Contractors
  • Vendors
  • Budgeted Expenses
  • Unbudgeted Expenses
  • Scope Changes
  • Schedule Changes
  • Quality Changes

 

We've seen various types of delegation documents and developed our version of a template this past week (a premium template, available to all gantthead members through 1/15/2012).

If you think you might find it useful, take a look at the template and tell us what you think.

 



| Posted: January 08, 2012 10:02 PM | Permalink | Comments (2) |

T- shirts Seem to Be All the Rage

Situation: Ya need something casual to wear that makes a PM statement.

I just noticed on facebook that PMI is promoting a new set of T's.  Here's the announcement and link -

Show off your project management pride! Reward your favorite project team members with new T-shirts from PMI! 

“Project Management” t-shirt: A colorful globe design sets off the words “Project Management” in several different languages.

‘Project Managers Do It With Standards” t-shirt: Give your fellow project managers a good chuckle when you wear this trendy t-shirt, which features a silhouette holding A Guide to the Project Management Body of Knowledge (PMBOK® Guide). Select from a male or a female silhouette.

‘Rome Wasn’t Built in a Day. They Should’ve Hired a PMP” t-shirt: For team members with a PMP® credential.

 

Of course, I tend to favor our gantthead T's - but I think it's great that you now have more PM fashion options.

If you're interested, the PMI shirts can be found here.

Our t-shirts are of course, in the gantthead shop.  You also get a free one if you sign up for a Premium Plus Membership.

Here's a few of them...



| Posted: January 06, 2012 03:52 PM | Permalink | Comments (1) |

Do You Need a Team Operating Agreement?
categories: Advice, Collaboration Tools, Management Approaches, New Templates

Situation: Team members keep stumbling over simple, common sense, standard practices.

A Team Operating Agreement seems like overkill for a lot of us. I've personally seen dozens of these over the last several years and many are just a fluffy box-checking exercise.  The whole this seems a bit much until you've been through the painful process of constantly reminding people how they should be working together. At some point you have to ask yourself - what's the least ridiculous option?  Do you keep telling people what you think is just common sense or do you work with them to spell out a set of rules that make sense to everyone?

Yesterday we went through the process of updating the TOA template we have here on gantthead (usually available only to premium plus members, but freely available to all registered members through 1/15/2012) and we added a few items that you see listed in bold below.

  • Ownership of project outcomes
  • Ownership of specific outcomes
  • What we value
  • How we make decisions
  • How we communicate
  • How we work through problems
  • How we express our commitments

In my opinion all of these things are important, but as it is with so many other things, the more important part is not the document - but the process of having built it collaboratively.  It's that collaborative process that gets you real buy-in to the principles you lay out in the agreement.  The signature is just a formality.

If you have a moment, come take a look at the new version of our template and let us know what you think.  

What do you think should be in a Team Operating Agreement?  What's a waste of time? How do you make the collaborative process of building the document work?



| Posted: January 04, 2012 10:47 AM | Permalink | Comments (18) |

Is Your Team Really a Team?
categories: Advice, Interviews, Management Approaches

Situation: You need to get people more in sync.

Recently, I interviewed Harlan Bridges on one of his chapter in Project Pain Reliever entitled, "My team isn't really a team". I asked him a few questions about how you get people to recognize the problem.  Then we dropped in a condensed version of the solution from the book

 

Dave:  In your experience, how do project managers find themselves in this situation?  What triggers the realization that they need help?

Harlan:  Project managers can find themselves in this position for many reasons. Some of these happen when:

  • the team's purpose, it's reason for existence, is not clearly defined
  • there is no team identity
  • the team members do not agree on the goals and objectives
  • the team members are not used to working as a team or with each other
  • there is a lack of clear communication
  • there is a lack of clear expectations 

Some obvious ways that people figure out that they are not on a cohesive team are:

  • everyone working more as a group of individuals doing individual activities than as a coordinated team
  • a lack of cohesion
  • conflicts between team members
  • unclear roles
  • a lack of respect for each other or the Project Manager

 

Dave:  How do you help them connect what they perceive as their problem to the solution you outline in your Project Pain Reliever chapter?

Harlan:  I work with the PM to look for the warning signs of a lack of teamwork. If they are present and pervasive, there are ways to find root causes and solutions. 

I will ask questions such as these in an attempt to find out the root causes a lack of teamwork.

  • Are the people on the team the "right" people?
  • Do the team members have a clear and complete understanding of the goals and objectives of the team?
  • How is communication being handled within the team?
  • Is there an established team identity?
  • Are conflicts work related or personal in nature?

 

Dave:  What skills will the Project Manager need to resolve this project problem?

Harlan:  The most important skills are those of observation, communication, and leadership. Practice observing the interactions of the team members. Look for signs of disrespect towards team members as well as tendencies to marginalize people or their contributions. Communication is key. The most important skill in communication is the ability to listen. The project manager most learn to deal with conflict effectively. Do not avoid conflict, but rather work to determine the cause of the conflict. Seeking advice of others who have a track record of successful team building is a good method for overcoming a skill gap. Course in leadership as well as self-learning activities can also be of help.

In some cases, the teams may be beyond help. It is possible that the team is so miss-matched that it will not function well. That is why getting the right people on the team is critical to success. I have had the misfortune of working with such a team. In spite of my best efforts, I had to replace one of the members of the team to end the turmoil. Though not my desired solution, it did solve the problem and my team became a successful team afterwards.

 

Dave:  How do you motivate them to action?

Harlan:  In these situations, projects are usually not meeting milestones or other expectations. It's a self-motivating situation. There is often a great deal of stress for all involved and the trick is painting a clear picture of the cost of failure.

This stress of belonging to a low-performing team by itself is usually a strong motivator to take action. The alternative is a vicious downward cycle which is untenable for all involved. 

 

 

So how do you build a strong team?

(excerpt from Project Pain Reliever)

 

 

As the project manager, you have the responsibility for developing and leading cohesive teams. Remember that you are not so much managing a project as leading a team of people who must come together to achieve the goals of the project. Often, people are part of a functional unit within the business and do not directly report to you. You will have to establish yourself as a leader and mold the individuals into a team. What can you do to create cohesive, successful teams?

First, you need to understand the characteristics of a successful team. Then you can create an environment that helps the team take on those characteristics. These characteristics include:

  • The right people on the team
  • Respect for every member of the team
  • Well-defined roles and responsibilities
  • Clear and honest communication
  • Understood and agreed upon project goals
  • Team ownership of project goals
  • Team responsibility for the success of the project

 

What should I do?

As project manager, you need to start laying the foundation for effective teamwork by creating an environment where people can work together effectively.

Get the right people

In order to get the right people, you need to develop a resource plan. A resource plan requires that you identify and understand the work to be done, at least at a high level. This will identify the type of personnel required and will help you to recognize skills and abilities required to complete the work. Use the resource plan to begin identifying the resources for your team.

Effective teams require the right people. There are many factors to be considered when choosing team members, such as:

  • Do they have the skills required to complete the work?
  • Do they have the capacity to work on the project, and do they have the time?
  • Do they have the ability to effectively work with others?
  • What is their position within the organization, and do they have the right level of influence?
  • Are they results oriented?

In most organizations, project team members are part-time teams. They usually have to split time between their regular job and project work. In order to reduce conflicts between their different responsibilities, work closely with the team member’s functional manager. Come to an agreement with the functional manager on terms such as availability, dealing with emergencies, and time away from their usual duties.

Create a team identity

Project team members are often from different functional areas or departments within the organization. They identify themselves as members of that organization and that team. A project requires them to leave their “home” team and play for someone else’s team. Who is that new team? If they do not know, it is difficult to feel loyal to, or a part of, a new team.

Once you have identified your team members and brought them together, begin creating a team identity. Involve the members in this. Here are some activities that can help:

  • Choose a team name, perhaps the project name or a nickname.
  • Develop a team logo.
  • If budget allows, order team shirts or coffee mugs, etc.
  • Announce the new team to the organization; be sure to list the team members.
  • Create a project web site on the company intranet.

Once you have established the team identity, use it often. Refer to the team by the team’s new identity.

Develop a team operating agreement (TOA), aka team charter

Once you have determined your team identity, it’s time to create the team operating agreement (TOA) or team charter. Include the entire team in the development of the TOA to ensure that everyone buys into it and has ownership. The TOA provides the ground rules and guidelines the team will use to work together in an effective manner during the project. It can include anything the team believes must be addressed in order to work together. Some typical items included are:

  • Team communication rules and expectations
  • Decision making procedures
  • What meetings will be held and ground rules for conducting meetings
  • Roles and responsibilities
  • Personal courtesies and how the team interacts with each other

Upon completion of the team operating agreement, every team member as well as the project manager should sign it indicating their agreement. The TOA is a living document and should be revised as needs arise.

Define project goals and objectives

The project goals and objectives are defined in the project charter. You have one, right? The project sponsor and the project manager usually jointly develop the project charter. They will work together to define the goals and objectives of the project, as well as the project success criteria. This document drives the scope of the project.

Use the project charter to help the team understand what is expected of them and of the project. As project manager, it is your responsibility to ensure the team has a clear understanding of project goals, objectives, and scope. Your team must know what success looks like in the eyes of the project sponsor. The project charter should also clarify how the project fits into the strategy of the organization. This will help the team understand the importance and relativity of the work they are doing.

Use leadership strategies

The most important aspect of team building is effective leadership from the project manager. The project manager is ultimately responsible for creating effective and successful teams. Some project managers are naturally charismatic, and people seem to want to do their best for them. Most of us do not have that gift. So how can the rest of us be effective leaders? Fortunately, although leadership entails many skills, these skills can be learned.

Practice effective communication

Become an effective communicator and always be honest in your dealings with the team. Learn to listen. Communication is your most effective tool in dealing with people. A simple rule is to tell your team everything about the project unless there is a valid reason for not doing so. Don’t manage with a “need to know” attitude but rather a “why shouldn’t they know” attitude.

Organize the team’s work in such a way that team members are mutually depen- dent and recognize it. This will produce a strong impetus for the group to become a team. Encourage a problem solving orientation in the team. Associate project suc- cess with teamwork and lack of teamwork with project failure.

Create rewards and recognition

Set up a system of rewards and recognition for your team. A good technique is to create a way that team members can nominate other members for rewards or rec- ognition. This fosters camaraderie and avoids the perception of favoritism. Present rewards and recognition at team meetings and consider inviting the team member’s functional manager to present the award. Post it on the project’s web site.

Manage conflict effectively

It is not possible to eliminate conflict from projects. How the project manager deals with conflict will determine whether conflict is harmful to the team and the proj- ect. In fact, controlled conflict can result in beneficial effects, such as thinking in a new way, coming up with novel solutions, and encouraging creative thinking. But unmanaged or unresolved conflict usually leads to problems.

Often you will have to become a negotiator between the team members in con- flict. This requires good listening skills and a bit of detection on your part. You must find the root cause of the conflict before you can address it. Work with all parties to the conflict to create a solution. In other words, help your team members find a solution. Don’t solve their problem, but support them in finding a resolution.

Empower your teams

Empowering others requires a level of trust on your part. Encourage the team to make decisions and find solutions to problems. It is your job to support the team in its work. Project managers with strong leadership skills trust their teams to do what’s right. Micromanagement is a team killer. You have selected a team for their expertise and ability to do the work. Trust them to do so. Your job is to clear their path of obstacles to project success and to provide them with all they need to do their jobs.



| Posted: December 27, 2011 05:09 PM | Permalink | Comments (1) |

older posts



sponsored announcements and special offers
Position yourself for success with Florida Tech's MBA in Project Management, accredited by PMI® GAC. There's no GMAT or GRE required, and you'll also qualify for 1,500 experience hours that can be used toward earning a prestigious PMP® credential.
The Enterprise PPM and PMO Blue Print. Learn strategies and best practices for taking a top-down, enterprise-wide approach to PPM processes and system deployment. To learn more and register now, click here!



The truth is more important than the facts.
- Frank Lloyd Wright