What Is A Project?

Project_Management_Knowledge_Areas
Project_Management_Knowledge_Areas

Many in the working world, who are not Project Managers by trade, manage projects. In many cases, they do not recognize they are managing a project and treat it as just another task assignment without applying project management disciplines. This can be very stressful as projects can descend into chaos without proper management.

If you are given a goal and it has a due date you now have a project. It can range from the trivial (“let’s go out to lunch Friday”) to the very complex (“we need a new payroll system”). There is a tipping point where you need to start applying project management discipline, with the depth varying with the complexity.

If you are the person responsible for meeting the goal and the date, then congratulations, you’re the Project Manager, whether that is your formal title or not. Recognizing your role is the first step to improving your chances of success. There are many more ways to fail than to succeed. By applying fundamentals, you eliminate ways to fail.

In the upcoming blog posts I will introduce you to fundamentals that will help you succeed in your job and your life.

My book, “Project Management For The Real World”, is available in paperback and Kindle formats at

http://www.amazon.com/dp/b089krddvn

Building Blocks Of A Successful Project Part 4 – Human Resources

#projectmanagement

Initiation

The first step in obtaining your project’s human resource needs is to create a “Roles/Responsibilities” matrix. In the first column, you define the project roles required. For example “Project Manager”, “Business Analyst”, “Subject Matter Experts”. These are not job titles but roles defined for the needs of the project. The second column describes the scope of responsibilities for that role. The third column is the name or names of those people assigned to that role. The rest of the columns contain contact information, and the assignee’s department and manager.

The next step is obtaining the commitments for these resources to work on the project. I have seen many projects given the approval to begin without the commitment (or even awareness) of key stakeholders (business units that will have project task assignments). This leaves the Project Manager in the position of negotiating with the business units for resource time and priority. This is typically the result of lack of Project Portfolio Management and control of the project intake process, especially in regard to resource capacity.

A best practice in Project Management is to secure the resource commitments prior to the approval of the Business Case. This means doing a thorough stakeholder analysis of all of the roles and responsibilities needed for the project. A brainstorming session with those having a broad knowledge of the business functions can help identify key stakeholders.

The Executive Sponsor (with support from the Project Manager) is responsible for communicating with the affected business units and securing the commitments. If these commitments have not been made and the project is directed to proceed, then this must be handled using formal Risk Management (which will be addressed in a future post).

In addition to having committed resources, they must also be the right resources. They must have skills that match the assigned roles. If they don’t and you have no resource alternatives then your project must include a plan for skills development and your task estimates must take into account the skill levels of the task assignee. These are also risks which must be managed.

For your “core” team (the small group that attends almost all meetings and contribute to planning) you must make sure they are empowered as decision makers. If your team is constantly saying “I have to get my manager’s approval”, your schedule may be significantly impacted.

Building Blocks Of A Successful Project Part 3 – Executive Commitment

#projectmanagement

Initiation

If your company actively manages its Project Portfolio, then this building block should already be in place. However, many companies begin new projects without any consideration of the impacts to projects already in progress or in the “pending” queue. This is the single biggest root cause of the Project Manager’s #1 headache: resource contention.

Before projects can begin, you should have satisfactory answers to the following questions:

  1. Are any existing projects competing for the same resources?
  2. If so, do these resources have the availability required for the new project?
  3. Where does this new project rank in the corporate priority?
  4. Is there a process in place to prevent the next new project from interfering with this one?

The answers to the above will tell you if you have Executive commitment for your project. Without it you will every day be at risk of losing key resources and jeopardizing your schedule.

My book, “Project Management For The Real World”, is available in paperback and Kindle formats at

http://www.amazon.com/dp/b089krddvn

Building Blocks Of A Successful Project Part 2 – Business Objectives

#projectmanagement

Initiation

There are  certain fundamentals that need to be in place to increase the probability of project success. The second of these is to have well-defined Business Objectives. These should be established as part of the original Business Case for the project. It is surprising how many times I have seen these absent from an initiative.

Business Objectives are the “CEO’s view” of the project. For example, they should make or save money, take advantage of opportunity, respond to new law and regulations, or increase competitive advantage. They should be specific and measurable (including when, how, and by whom the objectives will be measured) to avoid what I call “Mom and apple pie” objectives like “We will be more efficient”. Really? Exactly how efficient? Will we be able to cut costs or deploy those efficiency savings to revenue opportunities?

I will go into more detail on this topic when I address the Project Charter. Suffice to say for now that the main reason for having solid Business Objectives as a building block for project success is that it guides all decision making on a project. Whether you realize it or not, all of the project team members are decision makers, typically making many micro-decisions every day. The Business Objectives act as the beacon of light for these decisions. Any decision that will reduce or modify the impact of the Business Objectives must be escalated to the Project Sponsor.

My book, “Project Management For The Real World” is available in paperback and Kindle formats at

http://www.amazon.com/dp/b089krddvn

Building Blocks Of A Successful Project Part 1 – Business Sponsorship

#projectmanagemet

Initiation

The “Building Blocks” series of posts will help you identify key prerequisites that must be in place before you begin your project. Whether you are the Project Manager from the start of the project, or taking over someone else’s already started project, make sure these Critical Success Factors are in place.

There are certain fundamentals that need to be in place to increase the probability of project success. The first of these is to have an active and committed Business Sponsor. The Business Sponsor is the person (or persons) who initiated the project and authored the Business Case. The primary roles of the Business Sponsor are to provide funding, help clear obstacles to success, provide resources and make key decisions.

It is surprising how many projects (IT projects especially) proceed without this key building block. The thinking is that the merit of the project itself will drive it to successful conclusion. This is a huge mistake. Projects like this will typically encounter a lack of cooperation from the business units as their priorities do not match the priorities of those driving the project. It is OK for IT to get the ball rolling, but before the project is officially approved, the Business Sponsor must be identified and take ownership.

The Business Sponsor will play a key role in your Organizational Change Management Plan. Their responsibilities will include:

  • Being the “Face” of the project communicating directly with employees and management
  • Participating actively and visibly throughout the project
  • Building a coalition of sponsorship and manage resistance – identify other Executives who will Champion the change

My book, “Project Management For The Real World” is available in paperback and Kindle formats at

http://www.amazon.com/dp/b089krddvn

The Five Steps To Successful Project Management

There are no secrets to project management success. It’s a combination of education in PM best practices (the Project Management Body of Knowledge, or PMBOK), communication skills, and staying confident, focused and cool under fire. Most successful Project Managers follow these five steps:

Step 1: Know Your Outcomes

In the Project Charter topic, I mentioned the first and most important step in your project is to properly define the business and project outcomes. If you don’t know where you are going, how will you know you have arrived? This is as true for personal projects and goals as it is for business projects.

Step 2: Have a Plan and Take Action

You can speak passionately about your desired outcomes but unless you do something about it they are as worthless as having no outcomes at all. Taking action starts with good planning and the topics on the “Project Management Plan” and the “Project Plan” are excellent places to start. Once you have a plan, you can begin execution.

Step 3: Collect Relevant Information Regarding Progress

It is a rare project that goes exactly according to plan. You need to regularly evaluate whether your outcomes are still achievable and the level of progress towards achieving those outcomes. Having this information leads to the next step …

Step 4: Be Flexible and Change Plans as needed

If your project is not proceeding according to the plan, be prepared to change the plan and do whatever it takes to achieve your desired outcomes. This could mean some combination of the following: changing the order of activities, reassigning resources, changing the scope, crashing the schedule, etc.

The Marines have a motto: “Improvise, Adapt, Overcome”. This is also a good motto for Project Managers.

Step 5: Look and Feel Confident

Your project team will take its cue from you. If you are expressing doubts, look worried and anxious, or show uncertainty, your team will start to feel the same. Using PM best practices and following Steps 1 thru 4 in this post will allow you to proceed with confidence.

Note: Much more detail on successful Project Management can be found in my Kindle book “Project Management For The Real World”, available at

http://www.amazon.com/dp/b089krddvn

#projectmanagement

The Project Charter – Sign Off

Initiation

The Project Charter can be looked at as a contract between you and your project sponsor or you and your manager. It documents your understanding of the expectations of the sponsor and what you are expected to deliver and when. Like any contract, it should be concluded with a signature indicating agreement.

Why get a real signature? It is amazing how people will pay close attention to what is in a document when they have to sign their name to it! I have seen cases on my own projects as well as those I consulted on where misunderstandings are cleared up prior to charter sign off. This has and will save many hours of effort avoiding taking a project down the wrong path. For these reasons I highly recommend getting a real signature and posting a PDF image of the Project Charter in the project repository.

Once you have a signed-off charter, you now have one of the deliverables subject to formal Change Management. Any request that would change any component of the charter should have a formal change benefit/impact statement signed off and the Project Charter should be changed to a new version and signed off again.

In my next post we will move to the Planning Phase and begin a multi-part discussion on the Project Management Plan.

My Kindle book, “Project Management For The Real World”, is available at

http://www.amazon.com/dp/b089krddvn

Now available in paperback!

The Project Charter – Constraints

Initiation

Constraints are any limitations to solution options that have been imposed on a project. It is important to know these early on so time is not wasted pursuing these options. Here are some examples:

  • The solution must work with Microsoft Edge as that is the company standard
  • The solution must be an Oracle product for seamless integration with our other Enterprise systems
  • The new department we are adding as a result of this project must fit into this 30′ x 50′ area

When project constraints are uncovered, be sure to understand the reason why. It is possible some constraints could be removed. I was involved with a project where the service provider was already selected but without looking at the competition. I convinced my business partners to conduct formal “Request for Proposal’s” with the leading competition and the result was a different provider was selected.

Constraints are included in the Project Charter so that the Sponsor and Core Project Team understand and agree.

My Kindle Book, “Project Management For The Real World”, is available at

http://www.amazon.com/do/b089krddvn

Now available in paperback!

The Project Charter – Issues

Initiation

Issues are any event or known problem that will negatively impact your project’s schedule, scope, budget or quality. Issues differ from Risks in that Issues are 100% will or has happened whereas Risks may or may not happen with a probability less than 100% and greater than 0%. Risks that are not actively managed are more likely to become Issues.

At Project Charter time, you want to highlight the most severe impacting issues. Look specifically for the impacts in the following areas:

  • Schedule – issues that will delay your project start, or impact key milestones and the target completion date.
  • Scope – Issues that can prevent you from delivering the defined project scope
  • Budget – Issues that can cause the project to go over the allowed budget
  • Quality – Issues that will affect the quality of the delivered solution

In a future post I will address Issue Management in detail.

My Kindle book, “Project Management For The Real World”, is available at

http://www.amazon.com/dp/b089krddvn

Now available in paperback!

The Project Charter – Risks & Assumptions

Initiation

In upcoming posts I will discuss Risk Identification and Management in detail. For now, you just need to know that a risk is an uncertain future event that can have a negative impact on your project’s schedule, scope, budget or quality. The event has a probability of occurring less than 100% and greater than 0%. If the probability is 100%, then you have an issue, not a risk. Some risks can have a positive impact but we will not discuss that here.

You state the risk as follows:

  • If <risk event> occurs, then <state the outcome that affects your project> causing the project  to be impacted in the following specific ways <scope, schedule, budget, quality>.

At the Project Charter level, you are interested in identifying only the highest impact risks so that your risk management strategies can be accounted for in the scope and schedule.

Some Project Charters will list “Assumptions” in its own section. I have eliminated assumptions from my own charter template as I feel if you have assumptions that can impact your project, then that is just another form of risk. I now include any assumptions in my risk section.

My Kindle book, “Project Management For The Real World”, is available at

http://www.amazon.com/dp/b089krddvn

Now available in paperback!