...

becoming projectized

PRE-TRAINING DETAILS

Dear Prospective PMP/CAPM, Thanks for choosing Tycoons Project as your educational provider for the PMP Exam Preparation. The No. 1 Project Management Professional Exam Preparatory Tutor in Nigeria. Our process is standardized and comprehensive, individual participants can rely on the in class experience and the expert judgment of our facilitators. Our unique selling point is embedded in our learning process and support system. Our ideology is "if the process is good, the product will be". We focus on the process and breaking down the program in an easy to understand and use way. Follow our process and we guarantee you success at first try. Hope this short introductory material will furnish you with preliminary understanding about Project Management before the training start date.

BAMIDELE AJIBOLA, PMP

THE NATURE OF PROJECT MANAGEMENT

Project bureaucrats When I teach project management, I often draw a distinction between Project Managers And Project Bureaucrats. We've all had encounters with project managers who turned into bureaucrats. Project bureaucrats are more interested in ensuring that every step of the methodology is applied and every line of every form is filled in than in what's actually happening on the ground. On the other hand, it's common to meet project managers who apply minimal project methodology, yet, through their expert use of relationships and personal interactions, always seem to know exactly where the project stands. In my experience, it's the project bureaucrats who often leave a bitter taste with both the delivery team and the client. These project managers turned bureaucrats have forgotten one of the key rules of project management: don't mistake the map for the journey. All the plans, charts, and milestones mean nothing if they aren't consistent with the reality on the ground. And there's the rub; especially in innovative projects, the plans and estimates are often based on a fallacy there's the idea that we can predict the progress of something that's never been done before. Project spec compliance = success? Not always The lesson that project managers should learn is that compliance with project specifications does not constitute project success; in the ultimate analysis, only business results matter. Stated another way, the largest risk in any project is not that it will deviate from plan; it's the risk that the final outcome won't fulfill the real need. Predictive methodologies, such as the techniques championed by the Project Management Institute in its PM Body of Knowledge, can add tremendous value.

PROJECT MANAGEMENT KNOWLEDGE AREAS [SUMMARY] The project manager must have clear understanding of the process, activities and deliverables in managing project. It includes knowledge on how to use specific tools to bring about the expected product of each project management process. Here are the PMBOK definitions of the project management knowledge areas: The PMBOK Definition: 1. Management of Integration describes the processes and activities that integrate the various elements of project management. 2. Management of Scope describes the processes involved in ascertaining that the project includes all the work required, and only the work required, to complete the project successfully. 3. Management of Time describes the processes concerning the timely completion of the project. 4. Management of Cost describes the processes involved in planning, estimating, budgeting, and controlling costs so that the project is completed within the approved budget. 5. Management of Quality describes the processes involved in assuring that the project will satisfy the objectives for which it was undertaken. 6. Management of Human Resource describes the processes that organize and manage the project team. 7. Management of Project Communications describes the processes concerning the timely and appropriate generation, collection, dissemination, storage and ultimate disposition of project information. 8. Management of Risk describes the processes concerned with conducting risk management on a project. 9. Management of Procurement Management describes the processes that purchase or acquire products.

...becoming projectized

PROJECT MANGEMENT PROCESSES SUMMARY Project management refers to the application of processes and knowledge in taking projects from start to finish. It is important to recognize that all projects need some level of project management. The larger and more complex the project, the more there is a need for a formal, standard, structured process. Smaller projects still need a structured process, but it does not need to be as elaborate or as complex. Obviously there is a cost to the effort associated with project management, but there are many benefits that are obtained as well. These benefits far outweigh the costs. The Project Management Process provides the information you need to be a successful Project Manager, including a step-by-step approach, starting with the basics and getting as sophisticated as you need for your particular project. It is a flexible and scalable methodology for managing work as a project. The basic philosophy is large methodology for large projects, small methodology for small projects. The summary below shows you what you need to know to manage projects of all size. Define the Work Before the project work begins, there needs to be time spent in planning to make sure that the work is properly understood and agreed to by both the Project Manager and Project Sponsor. In this step, the Project Manager spends the time defining the work to ensure that the project team and the customer have common perceptions of the project, including what it is going to deliver, when it will be complete, what it will cost, who will do the work, how the work will be done, and what the benefits will be. The larger the project is, the more important it is that these factors be mapped out formally and explicitly. All projects should start with this type of upfront planning to prevent future problems caused by differing viewpoints on the basic terms of the project. The major deliverable from this step is the Project Definition (some companies call this a charter).

...becoming projectized

Build the Schedule and Budget In this step, the Project Schedule is created. The schedule is a vital tool to ensure that the project team knows what they need to do. Different approaches should be taken in this step according to the size of the project. The schedule for small projects can be built without a lot of formality. It is possible to use project management package like MS Project, or a spreadsheet, or a piece of paper. The Project Manager can sit down, with other team members if appropriate, and lay out the work to be performed. If you do not have a schedule template to use as your starting point, the Work Breakdown Structure (WBS) technique can be used for both medium and large projects Manage the Schedule and Budget By now, you have created a Project Definition and a Project Schedule. Now you must manage the schedule and ensure that it represents the current status of the project. The schedule should be kept up-to-date and should always tell you how much work is remaining. For the most part, the schedule will need to be reviewed on a weekly basis. During this review, update the schedule according to work that has been completed. It is also important to identify work that has not been completed, but should have been at this point in time. The remaining work should be evaluated to see if the project will be completed within the original effort, cost, and duration. The schedule can be further adjusted according to this information. Other factors that should be considered when determining project progress include a comparison of budget and actual expenditures made, any signs that the project may be in trouble, and an examination of the project's critical path. For any size project, the first priority should be to complete the project within the original estimates for effort, duration and cost. If any of the original estimates cannot be met, new estimates need to be prepared and

...becoming projectized

communicated to your management and to the customer. On a monthly basis, adjust future work to reflect any additional information or detail.

...becoming projectized

Manage Issues If a problem arises that the Project Manager and the team can resolve, then it is just one of the many fires that will ignite and be put out in a given week. However, an 'issue' arises when a problem will impede the progress of the project and cannot be resolved by the Project Manager and project team without outside help. This step provides guidance to help put a process in place to make sure that the appropriate people are aware of the issue and that the issue can be resolved as quickly as possible. There are also a number of problem solving techniques identified to help resolve these issues. Issues management is one of the fundamental skills that all Project Managers must master. Most projects of any size have to deal with issues. Once an issue has been identified and possible consequences have been investigated, it must be resolved quickly and effectively. Issues cannot be ignored and they cannot be deferred to some later time. Appropriate stakeholders need to be informed of any changes to the original Project Definition caused by the issue and its resolution. Manage Scope It is said that the only constant in the world is change. You can describe the scope of your project perfectly at a point in time, but you cannot account for every potential change that may occur. The longer your project, the more likely you will be dealing with changes. You and your team need to do the best job you can of defining scope given what you know at the time. That is good enough. After that you need to manage the changes.

Scope is the way that we describe the boundaries and deliverables of the project. It defines what the project will deliver and what it will not deliver, what data is needed and what is not needed,

...becoming projectized

What organizations are affected and which are not, etc. The project deliverables are described more clearly by the requirements. Requirements are also part of the project scope. Without proper scope definition, you have no chance to manage scope effectively. The purpose of scope change management is to protect the viability of the current, approved Project Definition. When the project was defined, certain expectations were set as to what the project was going to produce for an agreed upon cost and within an agreed upon timeframe. If the deliverables change during the project (and usually this means that the customer wants additional items), then the estimates for cost, effort and duration may no longer be valid. That is really the essence and purpose of scope change management to ensure that the initial agreements are met, and that the project team and those same stakeholders agree to any changes to the expectations. Manage Communication Properly communicating on a project is a critical success factor for managing the expectations of the customer and the stakeholders. If these people are not kept well informed of the project progress there is a much greater chance of problems and difficulties due to differing levels of expectations. In fact, in many cases where conflicts arise, it is not because of the actual problem, but because the customer or manager was surprised. Two typical forums for communicating status are through a Status Meeting and Status Reports. All projects should communicate status. This includes reporting from the project team to the Project Manager and reporting from the Project Manager to the customers and stakeholders.

...becoming projectized

While small projects usually do not require much more than basic reporting, medium projects require a more formalized set of activities. Larger projects require the most sophistication in how they communicate to various constituents. This multi-faceted approach is defined in a Communications Plan. Manage Risk Risk refers to future conditions or circumstances that exist outside of the control of the project team that will have an adverse impact on the project if they occur. In other words, whereas an issue is a current problem that must be dealt with, a risk is a potential future problem that has not yet occurred. Successful projects try to resolve potential problems before they occur. This is the art of risk management. Risk management is a proactive process that is invoked to attempt to eliminate potential problems before they occur, and therefore increase the likelihood of success on the project. Since small projects usually do not have a long duration, there is not as much opportunity for future problems. For medium and large projects, you perform a complete assessment of project risk when the project is defined. A risk level should then be assigned to each risk identified, along with the likelihood that the risk will occur. Risk plans are created for high-risk items that have a large impact on the project. Other combinations of high to medium risks, and high to medium likelihood should also have risk plans prepared. During the project, the Project Manager needs to monitor the risk plans to ensure they are being executed successfully. At the end of each phase or major milestone, the Project Manager also needs to perform an additional risk assessment based on current circumstances.

Manage Human Resources A project manager is 100% responsible for the processes used to manage a project. The project manager also has people management responsibilities, although these responsibilities are shared with the functional managers of the team members. Some people go as far as to say that managing people on a project is the most challenging and the most important of all the project management responsibilities.

...becoming projectized

Managers that can manage processes but are not very good with people may still be successful on their project. Project managers that are not good at managing processes but are good at managing people may also experience success, although probably at a lesser degree than the prior case. The best project managers do a good job managing the project management processes, plus do a good job acquiring, developing and managing the project team. Manage Quality and Metrics
Quality is ultimately defined by the customer, and represents how close the project and deliverables came to meeting the customer's requirements and expectations. Our goal is to meet the customer's requirements and expectations. This is a critical point. Sometimes there is a tendency to think that 'quality' means the best material, the best equipment and absolutely zero defects. However, in most cases, the customer does not expect, and cannot afford, a perfect solution. The purpose of the quality management is to first understand the actual expectations of the customer in terms of quality, and then put a proactive plan and process in place to meet those expectations. One of the basic tenets of quality management is to find errors and defects as early in the project as possible. Therefore, a good quality management process will end up taking more effort hours and cost up-front in the project. However, there will be a large payback as the project progresses. Small projects do not require much more than basic quality control, but for medium and large projects, a Quality Plan should be constructed to make sure that the project is being completed to standards. To make the quality management process work, collecting metrics is vital.

...becoming projectized

Gathering metrics on a project is the most sophisticated project management process, and can be the hardest. Because metrics can be hard to define and collect, they are usually ignored. This is unfortunate because it is very difficult to improve the quality of your deliverables or your processes if you are not gathering metrics. Metrics are used to give some indication of what the beginning state of quality is, and whether quality is increasing or decreasing. Large projects should definitely be capturing metrics that will provide information on the quality of the project and the processes used to create the deliverables. This process will result in the creation of a Project Scorecard.

Manage Procurement Procurement refers to the aspects of project management related to obtaining goods and services from outside companies. This specifically refers to vendors and suppliers. This is an area that project managers definitely need to understand at some level, and it is an area into which the project manager will give input. If you are purchasing goods or services on your project, you should determine your project procurement strategy and plans. In some cases, you will simply follow the procurement contracts and plans that are already established by your company or your organization. In some cases, you will need to work with your Procurement Department to establish your own projectlevel vendor management plans.

...becoming projectized

PROJECT MANAGEMENT PROCESS GROUPS [SUMMARY] Initiate the Project The Project Management Process describes how to proactively plan and manage projects. However, this assumes that there is a project to begin with. Every organization has processes in place to identify and authorize a project. This process generally has the following characteristics. Some way to identify all of the possible projects that could be started. - A funneling process to narrow down all of the possible processes into the smaller number that have the most value and are most aligned to the business goals and strategies. - A means to document the costs and benefits so that the project can be compared to other projects. This document is generally called a Business Case. - Identification of a minimum set of high-level information required to gain final approval of the project.

The process described above is used to gain preliminary approval for a project. However, there may be a time lag between the time when a project is initially approved, and the time the project actually starts. Therefore, when a project is ready to begin, there are a number of items that must be validated to ensure that the project is ready to start.

Plan the Project The Initiation process validates that the project is ready to start. You have ensured the project is still valid, the sponsor is ready and the project manager is in place. However, you are not ready to actually begin executing the project and building the deliverables. At this point you don't know the deliverables, the resources required, the timeframe, the schedule, the risks, etc. Yes, you might know this information at a very high level from the Business Case. But you don't know nearly enough details to be able to actually start project execution.

...becoming projectized

Before you begin execution you must first plan. If you have a small project the planning may be relatively easy and short. Perhaps it is just validating the deliverables, creating a task list, understanding the client expectations and then start. On the other hand, a very large project may take weeks or months to plan at the level that is appropriate enough to begin execution. The answer to the question of how long should you take to plan a project is sufficient time. This is a key point. You need to plan at a sufficient level to be confident of success. If you do not plan enough, there is a good chance you will encounter problems and not be as successful as you want to be. If you spend too much time planning you are not providing value and you are wasting time and resources that you could be spending executing.

...becoming projectized

Execute Project Management Processes on Your Project After the project has been planned it is time to begin executing the project lifecycle. At this point, two of the project management process groups come into the forefront to manage the project. Some of these processes are classified as executing and some are classified as monitor and control. The biggest different is that the executing processes are those that are proactively carried out by the project manager. For instance, managing issues is a proactive project management process. There is no baseline for issues. When an issue arises, the project manager needs to address it through issues management.

Monitor and Control the Project The second project management process that occurs as the project is progressing is monitor and control. This set of process is more reactive. You first make a baseline plan, and then monitor the project to detect a change to the baseline. When you detect the change, you take action. For example, the scope management is a process of monitoring the project scope. If the scope changes (from the baseline version) the project manager invokes scope change management. Likewise you have built a schedule for your project. You need to monitor progress against your schedule. If you remain on schedule and your schedule continues to represent the path to project completion, you may not have to update it again. If you detect a variance against your schedule, corrective actions may be necessary. This is the nature of project management activities that are in this monitor and control section.

...becoming projectized

Close the Project Just as it is important to formally kick off a project, it is also important to successfully close the project. The value of having a planned project termination is in leveraging all of the information and experience gathered throughout the project. If the solution is implemented and the team immediately disbands, you don't have an opportunity to wrap up the loose ends, do staff evaluations, document key learnings or ensure that appropriate deliverables are transitioned to support. Of course, a project can end unsuccessfully as well. Even in this case, there are key learnings, team evaluations and other wrap up activities to make the most of what was done on the project.

TIME-TABLE
DAY 1
TIME
8.00AM - 8.15AM 8.15AM - 10.45AM

...becoming projectized

DAY 2
FACULTY
PROTOCOL

TOPIC
REGISTRATION FOUNDATIONAL CONCEPT

TIME
8.00AM-8.15AM 8.15AM - 8.45AM

TOPIC
REGISTRATION REVISING DAY 1 TIME MANAGEMENT

FACULTY
PROTOCOL PMP CERTIFIED PROFESSIONAL PMP CERTIFIED PROFESSIONAL

PMP CERTIFIED PROFESSIONAL

8.45AM -10.45AM 10.45AM-10.45AM 8.45AM -11.00AM 11.00AM-11.30AM

10.45AM - 11.10AM

TEA BREAK
FOUNDATIONAL CONCEPT INTEGRATION MANAGEMENT PMP CERTIFIED PROFESSIONAL PMP CERTIFIED PROFESSIONAL

TEA BREAK
TIME MANAGEMENT CONTD PMP CERTIFIED PROFESSIONAL

11.10PM - 12.30PM 12.30PM - 2.10PM 2.10PM - 2.25PM

11.30AM-11.45AM
11.45AM - 2.40PM 2.40PM - 3.10PM 3.10PM - 3.45PM 3.45PM-4.00PM 4.00PM-5.35PM

SHORT TEST
COST MANAGEMENT PMP CERTIFIED PROFESSIONAL

SHORT TEST
LUNCH BREAK
SCOPE MANAGEMENT PMP CERTIFIED PROFESSIONAL

LUNCH BREAK
COST MANAGEMENT CONTD PMP CERTIFIED PROFESSIONAL

2.25PM - 3.00PM 3.00PM - 5.30PM

SHORT TEST
QUALITY MANAGEMENT PMP CERTIFIED PROFESSIONAL

5.30PM - 5.45PM 5.45PM - 6.00PM

SHORT TEST
CLOSING REMARKS PROJECT COORDINATOR

5.35PM-5.50PM 5.50PM-6.00PM

SHORT TEST
CLOSING REMARK PROJECT COORDINATOR

TIME-TABLE
DAY 3
TIME
8.00AM-8.15AM 8.15AM - 8.45AM 8.45AM -10.45AM 10.45AM-10.45AM 8.45AM -11.00AM 11.00AM-11.15AM 11.15AM-11.45AM 11.45AM - 2.10PM 2.10PM - 2.25PM 2.25PM - 3.05PM 3.05PM-5.30PM 5.30PM-5.45PM 5.45PM-6.00PM

...becoming projectized

DAY 4
FACULTY
PROTOCOL PMP CERTIFIED PROFESSIONAL PMP CERTIFIED PROFESSIONAL 8.15AM - 8.45AM 8.45AM -10.45AM 10.45AM-10.45AM 8.45AM -11.00AM 11.00AM-11.45AM 11.45AM-12.45AM 12.45AM - 1.00PM

TOPIC
REGISTRATION REVISING DAY 2 HUMAN RESOURCES MANAGEMENT

TIME
8.00AM-8.15AM

TOPIC
REGISTRATION REVISING DAY 3 PROCUREMENT MANAGEMENT

FACULTY
PROTOCOL PMP CERTIFIED PROFESSIONAL PMP CERTIFIED PROFESSIONAL

SHORT TEST GROUP PHOTOGRAPH TEA BREAK

SHORT TEST TEA BREAK

SHORT TEST COURSE EVALUATION LUNCH BREAK MOCK TEST

SHORT TEST LUNCH BREAK

1.00PM- 1.15PM
1.15PM - 1.55PM 1.55PM-5.10PM 5.10PM-5.35PM 5.35PM-5.50PM

SHORT TEST
CLOSING REMARK
PROJECT COORDINATOR

MARK TEST
CLOSING REMARK
PROJECT COORDINATOR