ITPM Reviewer Finals

Download as pdf or txt
Download as pdf or txt
You are on page 1of 5

Project Quality Management

• Project Quality Management includes the processes required to ensure that the project
will satisfy the needs for which it was undertaken.
• Quality management plan provides input to the overall project plan and must address
quality control, quality assurance, and quality improvement for the project.
• Quality Planning - identifying which quality standards are relevant to the project and
determining how to satisfy them.
• Benchmarking involves comparing actual or planned project practices to those of other
projects in order to generate ideas for improvement and to provide a standard by which to
measure performance.
• Cause-And-Effect Diagrams, also called Ishikawa diagrams or fishbone diagrams, which
illustrate how various causes and sub causes relate to create potential problems or effects.
• The judgmental forecasting methods used to predict the future project performance are
based on opinions and probable cost and schedule estimates. Example of a judgmental
methods scenario building, forecast by analogy, delphi method.
• A work breakdown structure, a status report, and a responsibility assignment matrix are
frequently used throughout a project. However, their usage might be iterative. These are
examples of deliverables.
• All of the following are ALWAYS inputs to the risk management process Historical
information, Lessons learned, and Work breakdown structure.

Project Human Resources

• Project Human Resource Management includes the processes required to make the most
effective use of the people involved with the project.
• Team Development - developing individual and group skills to enhance project
performance.
• Organizational Planning involves identifying, documenting, and assigning project roles,
responsibilities, and reporting relationships.
• Roles, responsibilities, and reporting relationships may be assigned to individuals or to
groups.
• Staffing requirements define what kinds of skills are required from what kinds of
individuals or groups and in what time frames.
• Project roles (who does what) and responsibilities (who decides what) must be assigned to
the appropriate project stakeholders.
• Team development includes both enhancing the ability of stakeholders to contribute as
individuals as well as enhancing the ability of the team to function as a team.
• Team-building activities include management and individual actions taken specifically
and primarily to improve team performance.
• Training includes all activities designed to enhance the skills, knowledge, and capabilities
of the project team.
• Project human resource management includes numerous "soft" skills that are not easy
to learn, and many project managers require additional training or development to
effectively schedule and coordinate resources. Human resource planning includes all of the
following, except team skills analysis.
• You are the head of a software development project where the developers involved are
working within a rented office space. It’s taking longer than anticipated to write the code.
You have requested the landlord to rent the office for another week. Unfortunately, the
landlord informs you that the office is booked for that period. You capture the problem in
the project documents. So, you should make revisions in the resource management
plan.

Project Risk Management

• Project Risk Management includes the processes concerned with identifying, analyzing,
and responding to project risk.
• Risk Identification determines which risks are likely to affect the project and documents
the characteristics of each.
• Risk Response Development defines enhancement steps for opportunities and responses
to threats.
• Risk identification and risk quantification are sometimes treated as a single process, and
the combined process may be called risk analysis or risk assessment.
• Risk identification should address both internal and external risks.
• Sources of risk are categories of possible risk events (e.g., stake- holder actions, unreliable
estimates, team turnover) that may affect the project for better or worse.
• Potential risk events are discrete occurrences such as a natural disaster or the departure of
a specific team member that may affect the project.
• Variance/trend analysis is done during risk monitoring and control.
• Potential risk events should be identified in addition to sources of risk when the
probability of occurrence or magnitude of loss is relatively large (“relatively large” will
vary by project).
• A project manager holds the first risk meeting of the project team. The client is present at
the meeting. At the meeting several risks are identified and assigned to members of the
project team for evaluation and quantification. The result of the meeting is a list of
potential risk events.
• A system development project is nearing project closing when a previously unidentified
risk is discovered. This could potentially affect the project's overall ability to deliver. The
next thing to do is to qualify the risk.
• During Plan Risk Response risk management process is a determination to transfer a
risk made.
• You need to establish the relative priorities of risks recognized in a project. The tasks that
most likely to not affect this prioritization is generating the risk report.

Project Communication Management

• Project Communications Management includes the processes required to ensure timely


and appropriate generation, collection, dissemination, storage, and ultimate disposition of
project information.
• Administrative Closure - generating, gathering, and disseminating information to
formalize phase or project completion.
• The general management skill of communicating is related to, but not the same as, project
communications management.
• Communications Planning involves determining the information and communications
needs of the stakeholders: who needs what information, when will they need it, and how
will it be given to them.
• Information distribution involves making needed information available to project
stakeholders in a timely manner.
• Communication Skills
• Verbal Communication
• Non-verbal Communication
• Written Communication
• Oral Communication
• Active Listening
• Project records may include correspondence, memos, reports, and documents describing
the project.
• Performance reporting involves collecting and disseminating performance information
in order to provide stakeholders with information about how resources are being used to
achieve project objectives.
• Trend analysis involves examining project results over time to determine if performance
is improving or deteriorating.
• Successfully communicating technical concepts to another team member in a different
country involves encoding, decoding and feedback. The lesser is the noise the more
meaningful will be the message. But, the most efficient way of communication that ensures
common understanding between participants is known as Interactive communication.

Project Procurement Management

• Project procurement management can be used to obtain the services of specific


individuals or groups of individuals to per- form project activities.
• Procurement Planning is the process of identifying which project needs can be best met
by procuring products or services outside the project organization.
• Cost Reimbursable Contracts - this category of contract involves payment
(reimbursement) to the seller for its actual costs.
• Fixed Price or Lump Sum Contracts - this category of contract involves a fixed total
price for a well-defined product.
• The statement of work (SOW) describes the procurement item in sufficient detail to allow
prospective sellers to determine if they are capable of providing the item.
• Solicitation involves obtaining information (bids and proposals) from prospective sellers
on how project needs can be met.
• Due to funding related issues, both the buyer and seller have reached a collective agreement
and agreed to end the contract in an IT project. Ending a contract using a collective
agreement is done during the control procurements process.
• Your project is in the final test stage, the user acceptance test. It meets all the product specs
and is under planned costs. In terms of schedule, this project is ahead. Your customer meets
you and requests that he will not accept the product unless you make several changes. You
should ask the customer to file a change request.

(Weh tunay?, magrereview ka nga? Hahaha joke lang po , GOOD LUCK GUYSSS )

You might also like