Method123

One of the frustrating parts of being a project manager is that it can be difficult to manage the project when you have no formal management authority over the members of your team. From an organizational perspective, if the people do not report to you as a functional manager, then you are probably operating in some type of matrix structure. The matrix makes the most efficient use of people resources, but it can also be very challenging on the part of project managers. How do you hold team members accountable for their deadlines without this authority? Proactively Manage Project Resources Without Authority If team members are missing their deadlines you must first try to determine the cause. For example, if it is due to a lack of skills, this should be addressed through training or replacement resources. If it is because they do not fully understand the expectations you have, then you may have some changes to make as well. Although the team members do not report to you functionally, th

Assumptions are statements that we believe to be true. You "assume" it to be true, but if it turns out not to be true there could be a detrimental impact to your project. The key point about an assumption is that you are not 100% sure if it true. You believe it to be true, but you are not certain. This means there is some risk that the assumption will not come true. Because of this uncertainty assumptions are v ery much related to risk, and in fact are simply low-level risks. They have the same characteristics as a risk - probability of occurrence and impact to your project. Assumptions and Risks - Two Sides of a Coin Let's take an example of a common statement that is included in many Project Definitions - that the resources needed for this project will be available when needed. What kind of a statement is this? Most people would say it is an assumption. After all, when a project starts, you always assume you will get the resources you need. However, is it really an a

Assumptions are statements that we believe to be true. You "assume" it to be true, but if it turns out not to be true there could be a detrimental impact to your project. The key point about an assumption is that you are not 100% sure if it true. You believe it to be true, but you are not certain. This means there is some risk that the assumption will not come true. Because of this uncertainty assumptions are v ery much related to risk, and in fact are simply low-level risks. They have the same characteristics as a risk - probability of occurrence and impact to your project. Assumptions and Risks - Two Sides of a Coin Let's take an example of a common statement that is included in many Project Definitions - that the resources needed for this project will be available when needed. What kind of a statement is this? Most people would say it is an assumption. After all, when a project starts, you always assume you will get the resources you need. However, is it really an a

We all have many wants in our lives but only a handful of needs—food, clothing, and shelter being the top three. Similarly, companies may want many things, but really only find a few things absolutely necessary for survival. A Project Management Office (PMO) should be at top of that list of priorities, along with sales, profits, and growth. Read on for the: Six Reasons You Need a PMO Consistent Methodology – The bane of many organizations is when departments and groups develop home-grown ways of completing projects. Some processes may work beautifully, some may work terribly; the point is that none are consistent with each other or across the organization. You need a common project management methodology. A PMO allows everyone in the company to speak the same language and follow consistent processes. Economies of Scale – It’s not uncommon for a company to have a half dozen or so timesheet or project management applications within a company, each with its own financial cost for i

We all have many wants in our lives but only a handful of needs—food, clothing, and shelter being the top three. Similarly, companies may want many things, but really only find a few things absolutely necessary for survival. A Project Management Office (PMO) should be at top of that list of priorities, along with sales, profits, and growth. Read on for the: Six Reasons You Need a PMO Consistent Methodology – The bane of many organizations is when departments and groups develop home-grown ways of completing projects. Some processes may work beautifully, some may work terribly; the point is that none are consistent with each other or across the organization. You need a common project management methodology. A PMO allows everyone in the company to speak the same language and follow consistent processes. Economies of Scale – It’s not uncommon for a company to have a half dozen or so timesheet or project management applications within a company, each with its own financial cost for i