Skip to main content

0.0 Project Management - Fundamentals


Terminologies
1.       Organizational Process Assets (OPA), which contains historical information of all projects of your organization and project management policies/templates, are readily available. PMI advocates constant improvement and continuous learning from project to project.
2.       Enterprise Environment Factors (EEF), which represents all the factors not in the immediate control of the project, is something a Project Manager has to live with.
3.       Change Requests include Corrective Action, Preventive Action, Rework and changes that would affect the project configurations/ baselines/plans.
4.       Lessons Learned are important outputs.
5.       Expert Judgment is the single most important tool and technique which refers to knowledge gained through experience and/or studies. If it appears as one of the choices for a PMP® question, it is often the correct answer.
 The Project Manager
1.       The Project Manager has the responsibility to ensure the project is completed on time and within budget.
2.       The Project Manager should collaborate with stakeholders throughout the project lifecycle. Plans should be developed in collaboration with appropriate stakeholders and subject matter experts.
3.       The Project Manager should be proactive in identifying problems, solving conflicts and looking for changes for the better. Conflicts should be addressed directly.
4.       The Project Manager needs to tailor the PMBOK® Guide Processes to suit the scope and characteristics of individual projects.
5.       The Project Manager must carry out impact analysis should something unusual happens before asking for changes.
6.       The Project Manager may take up a stretch assignment but should first let management know that they lack the experience/expertise.
7.       The Project Manager should consult sponsors/senior management when they have to make decisions that are believed to be out of their assigned authority. However, the Project Manager to exercise his/her authority to manage the project as far as he/she can without escalating the matter to senior management.
8.       The Project Manager should not accept requests to trim down the budget (or time) while the scope and time (or budget) cannot be changed.
9.       The Project Manager is responsible for tailoring (identifying and selecting the most appropriate project management processes/activities for a particular project).
 Project Management
1.       Emphasis is placed on the planning rather than putting out the fire day in day out. Work should begin after the proper planning is finished.
2.       The Project Management Plan is approved by all designated stakeholders and is believed to be achievable.
3.       All activities, issues and risks should be assigned to designated project members for handling.
4.       Competing constraints are time, cost, scope, quality, risk and resources. Change in one constraint will affect at least one other constraints non-linearly, e.g. a reduction in 10% of cost may affect 90% of the quality.
5.       Risk Management is almost a must for all projects, project schedule and budget must take risks into consideration.
6.       Always follow the plan-do-check-act cycle.
7.       All changes must be handled through the Integrated Change Control Process, proper approvals must be sought and changes documented before work begins (except in the case of implementing workarounds during an emergency in which approval may be sought after the change has been carried out).
8.       Quality is an important consideration which needs constant improvement (through the control quality/process improvement).
9.       Project Management processes are not necessarily linear or one-off. Some processes are to be repeated more than once throughout the project.
 Others
1.       Meetings are used for idea generation, discussion, problem-solving or decision making, not status reporting.
2.       Gold-plating is derogatory to PMI.
3.       The Project Management Office (PMO) is assumed in most case.
4.       Work performed by resources (including overtime work) must be compensated. It is NOT recommended to ask resources to work overtime by sacrificing work-life balance.
5.       The goal of negotiation is to create a win-win result (problem-solving).
6.       Sunk cost is not to be considered when deciding when to terminate a project.
7.       Never tolerate sexual discrimination, even if it is customary in other cultures.

Comments

Popular posts from this blog

12.0 Project Procurement Management

Procurement is the formal processes many organizations follow obtain goods and services. Project Procurement Management is the process of selecting, monitoring and closing vendor contracts. The processes with the Procurement Knowledge Area are: ·         Plan Procurement Management ·         Conduct Procurement ·         Control Procurement Key Concepts There are many names for procurement documents, such as Request for Proposals (RFP), Invitation for Big (IFB), and Request for Quotation (RFQ ). Contract – A mutually binding agreement that obligates the seller to provide something of value (e.g. product or service) and the buyer to provide monetary compensation. The seller can also be referred to as: contractor, subcontractor, vendor, supplier, or service provider During the procurement lifecycle, the seller wears different hats. At the beginning, the seller is a bidder trying to win the contract. When they are selected, they become the selected source .

05.0 Project Scope Management

Key Concepts 1.        The primary aim of scope management to define the exact scope of work and to prevent scope creep ( additional requirements added without any proper control ) or gold-plating ( added by the project team with a view to impressing stakeholders ). 2.        Product Scope: a.         Features & functions that characterize a product, service or result b.        Assessed against the product requirements and WBS 3.        Project Scope a.         Work to be completed or Work performed to deliver product, service or result with specified features & functions 4.        Scope Baseline: scope statement + WBS + WBS dictionary 5.        WBS includes only the deliverables/outcomes/results (not actions) 6.        Project Scope – activities and processes needed to be performed to deliver the product scope, assessed against the scope baseline (scope statement, WBS and WBS dictionary), e.g. including testing & quality assurance, assessed against t