Search This Blog

Monday, April 30, 2012

Does Your Project Have Value?

Are you working on a project that has diminished in value? Does your project seem like it would have been a good idea if it was implemented two years ago, two years from now? If you are questioning the value of your project think about these things.

What would happen in your company if the project were cancelled?

Does the project link to your organizations strategic goals and/or objectives?

Does the project have visible support from senior management?

Does the project generate excitement?

Is your organization going to gain efficiencies or be more competitive as a result of successfully completing the project?

Is there lots of negative "buzz" about the project?

I'm sure there are lots of other questions that could be asked when it comes to questioning the value of projects. We need to keep in mind that all projects eventually end. Some end when they are completed successfully, and others are terminated early for a variety of reasons.

The important thing to keep in mind is that you must continually communicate across, up, and down the organization to find out what others are thinking about your project.

If the project manager is the only person in the organization that thinks his or her project has value, then the project manager isn't really thinking.

Does your project still have value? A tough question for certain projects, but one that must be answered on a regular basis.

Monday, April 23, 2012

Project Management - Communicating Change

Think about these questions prior to communicating change to your organization, project team, or stakeholders.


1. Why are we changing things?


Be prepared to address the value of the change to the people impacted by the change


2. What is required for those impacted by the change to do? What needs to be done first, second, etc.?


Outline the steps required to implement the change


3. How will we measure the results of the change? What are the potential impacts?


Prepare ahead of time to address how the team will know if they are successful.


4. Once change is implemented what tools or processes will need to be changed, added, deleted?


What will be impacted and how might these changes be received?


5. What is the benefit of the change (What's in it for me?)


What is the benefit, what is the downside (if any)?  Be honest and let the team know if behavior change is expected

Tuesday, April 17, 2012

Assumptions vs. Facts

Dr. Lewis Ireland wrote the excellent article below in 2003 talking about the differences between Assumptions and Facts.

Introduction

The difference between an assumption and a fact is often subtle and confusing. Some organizations, and individuals, view assumptions and facts in the same light. This approach causes confusion in managing both the assumptions and facts as well as communicating accurately the situation during planning and execution of projects.

The American Heritage Dictionary defines both words in the context of planning as:

• Assumption – a statement accepted or supposed as true without proof or demonstration.

• Fact – something presented as objectively real or something that has been objectively verified.

Planning a project using the wrong term can convey a different meaning to fact or assumption with catastrophic results. Facts do not change whereas assumptions are typically about a future state that may or may not come true. Listing both facts and assumptions as assumptions can also cause confusion because the project manager does not know which assumptions to track to ensure they are converted to facts.

read the rest of the article by clicking here

Thursday, April 12, 2012

Quote for the Day

You've got to have an atmosphere where people can make mistakes.  If we're not making mistakes, we're not going anywhere.  - Gordon Forward

Monday, April 09, 2012

Where are your Process Maps?


Well crafted business process maps should be designed to make work flow visible, understandable, and measurable. An important consideration when mapping your business processes is to view them through the eyes of your customers.

Here are some areas to consider when you are mapping business processes:

Identify Your Organization's/Project's Business Processes

What are the processes in your organization that your project will impact?

What new processes will be created once your project is implemented?

What are your customers understanding of your processes?

What are the key trigger points of your processes?

Gather required information

Who are the process owners?

What are the processes you've identified trying to accomplish?

What is the level of quality required? Risk?

What are the control points?

Documenting the Processes

What are all the steps of the processes?

What are the objectives of the processes?

What are the inputs and outputs?

What tools or techniques are applied in each process step?

Where does the process begin and end?

Who owns the process?

Who monitors the process?

How we will know it is working?

Analysis (post mapping)

Is the process efficient?

Does it make sense?

What steps are unnecessary?

Is the process in line with departmental or enterprise objectives?

Are there too many approvals or too much rework?

Are there too many delays or bottlenecks?

Is the process efficient? How do you know?

What measures will be put in place to ensure the process is as efficient as possible?

There are many opportunities for problems to occur when mapping processes, but getting started will help your organization become more effective. Once you become good at mapping your business processes everyone in your organization will begin to understand their role in the organization, what the organization it trying to accomplish, and feel like they are part of the effort to help drive improvements and efficiencies.

There are plenty of books on the subject to help your get started. Click the link below for books that can help - Process Mapping Books

Saturday, April 07, 2012

Monday, April 02, 2012

The Project Sponsor

A project sponsor's role is to help make project decisions (formal authority), and additionally, he or she is ultimately responsible for the project's success. The sponsor comes from the executive or senior management ranks (depending on the size of the project) and should be influential, a respected politician, and have a track record for getting things done.

The sponsors authority and stature should be such that they are independent as much as possible of the project's goals and objectives so they can cut through the political landscape to get critical project decisions made.

Sponsors don't just support projects; they support the project manager and project team. They are the project champion and won't allow others to sabotage the project manager, the project team, or the project's goals. They have authority that comes from their title and position within the organization. In order for sponsors to be effective they must have organizational respect, proven leadership qualities, and be honest in their dealings.  They aren't political sharks and they are adept at rallying the troops (project team and stakeholders), presenting a clear message, and are supportive of the project manager.

Ideal Sponsor Responsibilities

Writes the Project Charter

Help to define project team roles and responsibilities

Acts as an advisor to the project manager

Removes obstacles

Has control of project funding

Reviews and Approves any Statements of Work/Contracts and Planning Documents

Bad Sponsor Characteristics

Always too busy to meet with the project manager and project team

Doesn't have time to write a project charter

Won't get involved in assigning project roles and responsibilities

Doesn't have time to approve documents, or delegates all sponsor responsibility to others.

Blames others when things go wrong, and/or won't work to resolve project issues

Always takes credit for any project success

Is surprised when the project's deliverables aren't what they expected

A bad sponsor is a project manager's worst nightmare. Avoid them at all costs if possible.

Monday, March 26, 2012

Project Role Definition and Responsibilities

What are your thoughts?  Do these roles exist in your organization?  Do you agree with the definitions? 

Executive Steering Committee - Sets the strategic vision and objectives for a given program or project. The team leads efforts to build consensus through the organization to support the project or program’s objectives.

Governance Board - Formal team of executives from across the organization that ensure projects will meet/are meeting enterprise goals.

Project Sponsor - Provides clarity of the project vision, and directs the activities of the project team. Allocates funding and resources to the project. Provides executive authority necessary to overcome organizational obstacles and barriers. The guardian of the business case, and ultimately responsible for project success.

Performing Organization - The organization whose personnel are most directly involved in doing the work of the project. This organization usually provides sponsorship for the project.

Project Management Office - An organizational body or entity assigned various responsibilities related to the centralized and coordinated management of those programs/projects under its domain.

Project Stakeholders - Persons or organizations (customers, sponsors, performers, public) that are actively involved in the project or whose interests may be positively or negatively impacted by executing or implementation of the project.

Program Manager - Person responsible for the centralized, coordinated management of a program (group of related projects) to achieve the program’s strategic objectives and benefits.

Project Manager - The person assigned by the performing organization to achieve the project objectives. The project manager is responsible for coordinating and integrating activities across multiple functional lines, and managing stakeholder communications. The project manager accomplishes the above by managing project scope, time, cost, and quality. Finally, the project manager applies project management, general management and technical skills, as well as team management, negotiation, financial and business acumen, combined with an understanding of organizational politics to meet project objectives and to meet or exceed stakeholder expectations.

Project Team - All the project team members, including the project management team, the project manager, and for some projects, the project sponsor.

Functional Manager -  In regards to projects, the person responsible for ensuring agreed-upon project tasks are completed using pre-defined resources under the functional manager’s control within scope, time, budget and quality constraints.

Project Team Leader - Responsible for ensuring that agreed-upon project tasks and assignments are completed on time, on budget, and within quality standards for personnel under their realm of control or influence. The team leader should be knowledgeable of the principles and practices of project management and understand the business unit’s strategic and operational issues.

Technical Manager/Liaison - Responsible for the technical implementation of the project as measured against the project requirements, quality targets, and budgetary constraints, and timelines. Ensures technical deliverables are consistent with the overall technical strategy of the enterprise.

Business Analyst - Primary interface between projects and business partners. Responsible for understanding current and future processes, including processes for the entire enterprise. Documents business requirements, generate business cases, assists in defining project benefits/ costs, and participates in project reviews


Thursday, March 22, 2012

Mastering Your Work

David Allen is known for great training and tools to help people and organizations efficiently manage work.  Check out David Allen's website for some great information!


David Allen wrote an article for the NYT this past weekend. Check it out here!


Click the image below to enlarge.

Monday, March 19, 2012

Estimating Project Management Tasks


As stated so eloquently by Bob Lewis in his book "IS Survival Guide", There is no way for you to successfully estimate projects. Take that as a given. It can't be done, and for a very simple reason: Every one of your projects is one-of-a-kind. Mr. Lewis makes a very good point, however in my experience, I have yet to have met a manager that will let me get away with saying "I can't estimate this project".

SO WHAT IS A PROJECT MANAGER TO DO?

I like to call the solution to this problem rolling-wave estimating. By that I mean when the project is in the initiation phase and you have very little information your estimate should reflect that fact. This means very early in the project your estimate(s) could be off by as much as +200/-75% (or more). As you progress through the project planning phase you will breakdown the project into smaller, more manageable pieces of work (decomposition). This process helps to narrow the range of your estimates.

Do not be fooled into thinking that because you have broken down your project into phases and/or small manageable pieces of work that you can just add up the estimates and have a total overall project estimate. Many times, especially on IT projects, there are integration issues that are difficult to estimate and are usually ignored in the planning phase. Do not forget to add time for these critical integration activities. Also, while padding of estimates is a no-no, don't forget to account for risk in your project estimates. PMI advocates for contingency and management reserves to account for risk events, but I have not worked in an environment where these exist so I have to plan for risk in my estimates.

Be smart when estimating and realize that in the IT world estimates are always wrong and tasks are always underestimated.

Monday, March 12, 2012

What is Project Management Value?

Project value can’t be dictated; it must be planned, agreed upon, and easily recognizable.  We can't be told something has value.  We must be shown its value and left to form our own opinions.  In all cases the value of a project must be measurable.

IT IS EASY TO BE SUCCESSFUL WHEN SUCCESS HAS NO MEASURE!

Projects that produce little to no value aren't unique to any one industry or business segment.  They are often a result of a project manager or project team with the mentality that says we know best, and we believe we are smarter than everybody else.

We can sum up this type of behavior in one word...Arrogance.

As taken from the website the Inner Frontier:

ARROGANCE - "Those to whom much has been given sometimes suffer from arrogance; or rather the people around them suffer. Arrogance is doubly a pity, because the talents of the arrogant serve primarily themselves. The arrogant assumes his views and opinions are The Truth. In arrogance, natural confidence goes sadly awry. Rather than the self-assurance born of knowing his own strengths and limitations, arrogance admits no limits. The arrogant brooks no weakness in himself and may even secretly rejoice to find flaws in others."

Don't be arrogant and don't manage a project that doesn't have value.

Monday, March 05, 2012

Organizational Strategy and Project Plans

We have a strategic plan where I work, however we don't have a portfolio planning office to manage the output of the strategic plan (the projects). A strategic plan is basically an outline for a list of strategic projects. Strategic projects are focused on mid and long term goals and are authorized by senior management. Without a strategic planning office there is not an effective strategic plan, and a strategic plan that isn't effective isn't worth the paper it is printed on.

According to some research, 50-80% of strategic plans never come to fruition. I would bet that most of these failed strategic plans were due to organizations not having a strategic planning office. As I mentioned, my organization has a strategic plan, and while well thought out, it doesn't appear to be very effective at consistently delivering measurable results. I say this because I don't see a project portfolio or list of strategic projects, and there is no organization to oversee these projects at the enterprise level. Also, the projects that do come out of our strategic plan aren't usually very S.M.A.R.T. - Specific, Measurable, Achievable, Resource Constrained/Relevant, Time-bound.

If your projects aren't S.M.A.R.T they aren't worth planning and executing.
Organizations, especially local governments, can tweak and refine their strategy over time. This can be due to the ever changing political winds, environmental factors, customer demands, changing priorities, resource constraints, a lack of political will, or executive apathy, but more often it is because of a lack of an enterprise project management focus. Whatever the case, a strategic planning office can help an organizations focus on what is important in regards to the management of strategic projects.

When thinking about strategic projects think about the following:
  • How the projects will be selected?
  • How the projects will be funded?
  • How the projects will be monitored and reported against?
  • How will project audits be conducted?
  • Who sponsors the projects?
One final thing, review PMI's OPM3 (Organizational Project Management Maturity Model) to help you transform your organization's strategy into action, and remember the Strategic Planning Circle - Strategy ---> Ideas ---> Projects ---> Change

Wednesday, February 29, 2012

Can You See Me Now?



Do you manage your projects mostly from your desk? Are you falling into the trap of managing projects via e-mail, voice mail, fax, letter, and failing to communicate with your customers and stakeholders face-to-face?

People value one-on-one conversations. A project manager that doesn't spend significant time on his or her project speaking directly to their customers will not be as effective as the one the takes the time to conduct meetings in person.

As project managers we are selling "experiences" and "solutions". Can you effectively sell your ideas as a faceless e-mail machine? Can you "WOW" your customers with tired voice mails and bland status reports?

Good customers want to see you as much as possible. They want to feel your enthusiasm, experience your excitement, and have you tell them eye-to-eye that "it’s all good".

Don’t cower (and sour) behind your keyboard sending status reports and e-mails and think your are doing your job. You can't gain your customer's trust unless you speak with them one on one.

As Tom Peter says, "If there is nothing special about your work...you won't get noticed, and that means you won't get paid much either".

It is hard to get noticed when people can't see you. BE VISIBLE!

Wednesday, February 22, 2012

Keep Hope Alive

Practice hope. As hopefulness becomes a habit, you can achieve a permanently happy spirit - Norman Vincent Peale

Monday, February 13, 2012

Office Gossip

This Soviet war poster conveys the message: "Don't chatter! Gossiping borders on treason" (1941).

According to Marilyn Haight, at BigBadBoss.com Office Politics “is the use of one's individual or assigned power within an employing organization for the purpose of obtaining advantages beyond one's legitimate authority.” Those advantages may include access to tangible assets, or intangible benefits such as status or pseudo-authority that influences the behavior of others. Both individuals and groups may engage in Office Politics."

I think most people would agree that those participating in office politics seek to gain an advantage. Being a skillful office politician may get you recognized or promoted, but it may also come at the expense of your or another’s integrity.

Remember, gossip is usually destructive (at a minimum unfair) to somebody, and should be discouraged whenever possible. If we are honest, we would all admit that we participate in office gossip. We need to limit office gossip to be the exception, not the norm in our daily conversations with others.

Be accountable for your words in the workplace. Work should be fun and our work relationships should be positive and healthy. Healthy work relationships are dependent on gossip being kept to a minimum.

Monday, February 06, 2012

The Perfect (IT) Project Manager


I have a book entitled “What Makes a Good Project Manager” by James S. Pennypacker and Jeannette Cabanis-Brewin. In the book, there is a reference to a ComputerWorld article that discusses “The Perfect Project Manager”. The consensus of the article was in the world of Information Technology (IT) there are three general areas of Project Management competency: Technology, Business, and Behavior (in no certain order).


One of the CIOs interviewed in the ComputerWorld article stated “in order to motivate IT workers, you need … an understanding of human behavior and how to motivate teams.” Do not miss this important point. Project Managers are primarily team leaders, motivators, and communicators. Project Managers will not be successful managing IT projects if they do not have an understanding of basic human behavior.

It has also been determined there are three Project Management skills that are required for success in IT:

General Management Skills

Project Management Skills

IT Management Skills


Under General Management, the key areas of expertise are (not in order):

Thinking Skills

Organizational Awareness

Leadership

Interpersonal Relations

Communication Skills


Many companies are now interviewing Project Managers placing a heavy emphasis on character traits versus professional competencies. These companies realize if a Project Manager cannot get along well with others and have poor communication skills they will not be successful.

The key to project success is having a competent project manager and the number one competency of a project manager is honesty. Research has shown that projects are more likely to fail because the human elements are not managed. In order to mitigate this type of risk project managers need to develop skills that support sound decision-making, good communications, motivational techniques, and conflict management.

Monday, January 30, 2012

Simple Problem Management Tips


Stand up for your team members. If other team members, individuals, or groups outside your team are leveling unfair criticism on your team, get out in front of the issue and defend your team.

Admit your mistakes. Do not allow pride or ego to prevent you from admitting your mistakes.

Take charge when needed. Some situations will solve themselves; others may require you to step in. Know when to get involved and when to stay on the sideline.

Fix problems quickly. Do not worry about assigning blame. Fix the problem first before trying to find the root cause.

Separate yourself from the problem – Learn to see problems from different perspectives. Learn to look for causes.

Take time to know the facts. Do not prescribe before you diagnose. Take the time to gather all the facts before you rush to judgment.

Retain control of your emotions. Do not let anger cloud your judgment.

Tuesday, January 24, 2012

Top Ten Project Management Trends for 2012 by ESI


ESI Announces Top 10 Project Management Trends for 2012
Collaboration Gains Importance as Project Complexity Grows

ARLINGTON, VA, USA – Jan. 5, 2012 – As the project environment grows in complexity, project management will require team, stakeholder and executive collaboration in 2012 like never before. On-the-job application of training, custom-made project approaches, innovative project tools and smarter resource management will be essential for driving the greatest business impact. Not only project management, but also the definition of “project success” has changed to encompass more than the triple constraint. Collaboration is a common theme throughout many of the 2012 Top 10 Trends for project management, which were determined by a global panel of ESI International senior executives and subject matter experts.
1.     Program management will gain momentum, but resources remain in short supply
Increasingly, large initiatives undertaken by corporations and government agencies are being recognized for what they are and aren’t: namely programs, not projects, which require a highly advanced set of skills supported by appropriate tools and methods to successfully execute. Yet many organizations struggle to find the right people and lack the management practices necessary to ensure success. In 2012 we will see more investments made in competency models, training, methodology development, tool use, and career pathing to ensure that professionals who carry the title Program Manager are fit for the role.

2.     Collaboration software solutions will become  an essential business tool for project teams
The proliferation of collaborative software in the project environment such as SharePoint® is going to intensify in 2012. Fueled by increasingly complex and virtual projects as well as tightened budgets, today’s environment demands a more efficient way to manage communication and workflow. Collaboration is central to project management and having a site which allows project artifacts to be created, shared, and distributed within a repository that provides Web-based access and critical functions such as automatic distribution and notification, version control, and user authentication, greatly enhances productivity.
3.     Learning transfer will become the new mantra, but with little structured application
Learning transfer–the ability to apply training back on the job--will continue to be on the minds of PMO heads and learning and development (L&D) professionals who want their project managers to return from training ready to apply what they learned immediately and accurately to their projects. While L&D and business heads agree that sustained learning is a sound idea, very few organizations will invest in a formal process to make it happen. In 2012 we will see many organizations discussing the importance of learning transfer without really putting in place a structured approach to ensure it happens.

4.     Agile blends with waterfall for a new “hybrid” approach
Having moved from “manifesto to mainstream,” Agile has confronted project teams with the difficulty of implementing the experimental and hyper-collaborative approach. To transition an organization into fully adopting certain aspects of Agile, project teams are combining traditional and Agile elements to create their own hybrid approach. In areas such as planning, requirements, and team communication, organizations are designing custom-made methodologies to do what works for them.

5.     Smarter project investments will require a stronger marriage between project management and business process management (BPM)     
In the financial services industry, and specifically in the insurance sector, there will be a continued laser-like focus on performing business processes as efficiently as possible to drive down operating costs. The philosophy of BPM is fast becoming a key factor in project selection. When new projects are proposed, their value will be judged to a large extent on the impact they will have on the organization’s business processes. The more impact the project has on reducing internal costs, the higher it will be ranked. The “smart” money will be spent on driving costs out of the business. Given the high premium being placed on efficient processes delivered through projects, BPM is a key concept with which project managers will need to be intimately familiar.
6.     Internal certifications in corporations and federal agencies will eclipse the PMP®
With roughly 470,000 Project Management Professional (PMP®) credentials having  been awarded worldwide thus far, the PMP® remains the most popular and ubiquitous credential on the planet. However, it is not the prominent credential everywhere. In the U.S. government as well as Fortune 500 corporations, a hierarchy of “internal” credentials has overshadowed the PMP® in terms of prominence. To be sure, the PMP® remains important, but it is now just one rung on the career ladder to get to the top.
7.     More PMO heads will measure effectiveness on business results
While introducing tools, using methodologies, mapping project management practices, sending project managers to training, and increasing the number of PMP®s in the organization are important metrics for a PMO head to collect and report on, they do not speak to the effectiveness of the PMO from a business perspective. To judge business effectiveness, PMO heads need to determine if their work has had a positive, quantifiable effect on the business in terms of troubled project reduction, lower project manager attrition, and faster time to market. In 2012 the practice of measuring the outputs, not the inputs, of project management will gain traction.

8.     Good project managers will buck unemployment trends
Even though unemployment is at record levels in many countries, good project managers are hard to find. Recruiting continues even in tough economies and organizations need individuals who can perform the basics flawlessly. The hunger for project management basics, in particular risk management, will continue to surge in 2012, especially in such countries as India and China where project manager attrition rates are disturbingly high and continuous training of new staff is critical.
9.     Client-centric project management will outpace the “triple constraint”
For years, time, cost and scope were the metrics upon which the success of all projects and their managers were judged. While the triple constraints remain important, they are no longer the be-all-and-end-all for project success. While risk and quality have also been cited as additional “constraints,” the clear trend in 2012 is the value the project delivers to the organization. The new definition of project success is that a project can exceed its time and cost estimates so long as the client determines that it is successful by whatever criteria they use. In today’s environment, project value is determined by the “recipient”—or client—not the “provider.”

10.  HR professionals will seek assessments to identify high-potential project managers
Because project management is such an important function, human resources professionals will be tasked more intensely with identifying high-potential project managers in 2012. The challenge HR professionals will face is that there is no ‘silver bullet’ assessment for identifying great project managers. Existing knowledge and skills assessments are of little use since they are not designed for entry-level project manager positions. Nonetheless, candidates must be measured not only on their technical abilities, but also on the all-important business and interpersonal skills. To the best of our knowledge, no one has yet developed such an assessment, but HR professionals will continue, and intensify, their assessment search this year.

“From the ascendancy of social media to the structured implementation of collaboration tools by the PMO and the steady rise of communities of practice, we are fast approaching a tipping point,” said J. LeRoy Ward, PMP, PgMP, Executive Vice President, Product Strategy & Management, ESI International “Those project organizations that don’t exploit such collaborative channels and technology will risk missing the most promising combination of force multipliers of the decade.”

# # #

About ESI International
ESI, a subsidiary of Informa plc (LSE:INF), helps people around the world improve the way they manage projects, contracts, requirements and vendors through innovative project management trainingbusiness analysis training and contract management training. In addition to ESI’s more than 100 courses delivered in more than a dozen languages at hundreds of locations worldwide, ESI offers several certificate programs through our educational partner, The George Washington University in Washington, D.C. Founded in 1981, ESI’s worldwide headquarters are in Arlington, Va., USA. To date, ESI’s programs have benefited more than 1.35 million professionals worldwide. For more information visit www.esi-intl.com.

Sunday, January 15, 2012

Ten Keys to Civility

A local foundation here in Florida, USA has developed a set of "Ten Keys to Civility".  These are a perfect set of guiding principles for the project manager. Click here to view their website and find out more.

Respect Others - Honor other people and their opinions, especially in the midst of a disagreement. 

Think Positively - Keep an open mind and assume others have good intentions.

Pay Attention - Be aware and attend to the world and the people around you.

Make a Difference - Get involved.

Speak Kindly - Choose not to spread or listen to gossip.

Say Thank You - Let others know they are appreciated.

Accepts Others - Our differences are what make us interesting.

Rediscover Silence - Keep noise to a minimum.

Listen - Focus on others in order to better understand their points of view.

Keep Your Cool - Accept life's challenges with grace.

Monday, January 09, 2012

Quick Tips for the New Week

Get up earlier

Go to bed later

Work harder

Finish what you start

Learn one new thing

Renew one contact

Ask, "How can I help you?" at least once

Make yourself visible

Be of good cheer

Say "Thank You" at least once a day

Repeat tomorrow