The following Project Management MCQs have been compiled by our experts through research, in order to test your knowledge of the subject of Project Management. We encourage you to answer these multiple-choice questions to assess your proficiency.
Please continue by scrolling down.
A. PMO
B. Only coder
C. Only tester
D. Project manager
E. Both coder and tester
A. Project tasks, priority, allocated to, and target date
B. Project start time, project start date, project finish date, project finish time
C. Project stakeholder names, project name, customer name
D. Project team member details, date of birth, address
E. Project name, project closure date, project sponsors
A. Schedule Extension
B. Decreased Budget
C. Increased Budget
D. All of these
A. All payment can be claimed from customer
B. A project can't be treated as successful
C. A project can be closed successfully if PMO agrees
D. A project can be treated as successful
A. Requests or orders given by one's chain of command (Managers/supervisors)
B. Scope, Schedule, or Budget
C. Government regulations
D. The project charter
E. Corporate or industry norms, guidelines, or standard practices
A. PMO
B. All of these
C. Customer management
D. End users
E. Project managers
A. All of these
B. Project closure
C. Project execution
D. Project Initiation
A. Release of project resources
B. Customer acceptance
C. All of these
D. A formal closure note
A. Deliver at agreed budget.
B. Foster team communication.
C. Ensure timely delivery.
D. All of these
A. Risk mitigation
B. Crisis management
C. All of these
D. Project closure
E. Team management
A. All of these
B. Project charter is complete
C. Team participation
D. Client participation
A. Outputs
B. Durations
C. Inputs
D. All of the above
A. Poor project management
B. Poor team management
C. Poor governance
D. All of these
E. Poor development
A. Planning
B. Closure
C. Execution
D. Cleansing
A. All of these
B. Explain implication of bug
C. Find out the bug in code
D. State severity of bug
E. Documentation of Bugs Report
A. Come up with one idea
B. Understand whats needs to be done
C. Stick to the script
D. Finish quickly
A. All of the Above
B. Statistical Analysis
C. Feedback Systems
D. Trouble Shooting Techniques
A. Strategy
B. All of the Above
C. Scope
D. Purpose
A. A logical sequence of project phases comprising of associated activities
B. Defining project in a cyclic manner
C. Checking how many cycles there are in a project
D. Writing a report on life of a project
A. All of these
B. When project documentation is filed.
C. When all deliverables are signed off.
D. When contracts are closed.
A. Project team
B. All of these
C. Client contacts and management
D. Team supervisors
A. Monitoring project performance and control of risks
B. Monitoring project team behavior
C. Monitoring business
D. Monitoring customer end users
A. Performance Plan
B. Project Runner
C. Project Management Plan
D. Change Management Plan
A. Risk Assessment and mitigation plan and execution
B. Risk execution and identification
C. Risk Assessment and award
D. Risk evaluation and propogation
A. Project closure
B. If management of project fails
C. Project Initiation
D. Product deployment
A. True
B. False
A. Resolving conflict
B. Building trust
C. Active listening
D. Denying change requests
A. Project planning
B. Project control
C. Project closure
D. Project execution
A. Sharing failures of past projects
B. Sharing project team details
C. Sharing success stories of past projects
D. Sharing practices with team and assigning roles in monitoring
A. Cease Plan Mode
B. Crystallize Plan Mode
C. Critical Path Method
D. Control Problem Maps
A. Relegate
B. Reproduce
C. Denigrate
D. Oversee
A. Work required
B. Duration
C. Effort
D. Time required
A. Execution
B. Interpolation
C. Closure
D. Initiation
A. Project Cost Management
B. Project Planning
C. Project Quality Management
D. Performance Management
A. Project Assessment
B. Project Initiation
C. Project Referral
D. Project Delays
A. Resistance to change, lack of support, team management
B. Scope, schedule, cost
C. No specification, difficult users, political intervention
D. Budget, time, knowledge
A. Project management team
B. Customer
C. Project team themselves
D. Chief Information Officer (CIO)
A. If the project budget is less than the requested budget, count the difference as contingency.
B. Clarify with the sponsor which project attribute is most important to them. Plan the project with that attribute fixed.
C. If the project budget is more than the requested budget, agree to the terms but add change penalty fees into the contract.
D. If the project budget is more than the requested budget, negotiate the cost estimates down.
A. Schedule Variance
B. Schedule Vitals
C. Scalable Volue
D. Summary and Vision
A. Impacts negatively on progress and success of project
B. Enhances progress of project
C. Improves efficiency of product
D. Reduces failure chances
E. Increase market visibility
A. Product Manager
B. Program Manager
C. Scrum Master
D. Project Manager
A. Pie
B. Kant
C. Flow
D. Gannt
A. Identifying the details and environment surrounding the issues and enacting a post-assessment plan
B. Hiring a new team and requesting budget increases
C. Informing the stakeholder of misinformation and ensuring forward progression.
D. Forming an independent troubleshooting team and increasing the pay of top performers
A. Communications Management Plan
B. Project Planning
C. Quality Plan
D. Performance Plan
A. When contrasting final deliverables to original contract.
B. When documenting a team member change.
C. When cancelling vendor agreements.
D. When identifying activities needed to create deliverables.
A. Project execution
B. Project initiation
C. Project control
D. Project planning
A. Burndown chart review, finished work review, updates from team.
B. Task list review, new task assignments, questions.
C. Reporting the progress on the project since the last meeting, reporting of plans until the next meeting, noting issues that are delaying progress.
D. Team review of product that is almost ready for release, noting of issues, assignment of issue owners.
A. Cancellation Clause
B. Autopay Clause
C. Buyout Clause
D. Extension Clause
A. Setting up incentives to motivate the team to work faster.
B. Arranging some project activities to happen concurrently, rather than sequentially.
C. Reassigning activities that can be done faster through outsourcing.
D. Bringing in additional project management to oversee the schedule.
A. Project Quality Management
B. Project Planning
C. Performance Management
D. Project Cost Management
A. Risk mitigation
B. Risk acceptance
C. Risk analysis
D. Risk prevention
A. Business benefits are being realized
B. Scope is realistic and managed
C. Complex tasks are postponed
D. Work and schedules are predictable
E. Risks are being mitigated
A. Project
B. Perspective
C. Process
D. People
A. Project Scope Management
B. Change Management
C. Performance Management
D. Project Planning
A. Critical path method
B. event chain methodology
C. project plan
D. Delphi method
A. Quantification
B. Delegation
C. Relaying
D. Representation
A. Availability & Skill Set
B. Speed & Adaptability
C. Availability only
D. Skill Set & Speed
A. Issues are categorized based on urgency and impact
B. Issues are clearly stated
C. The project team member that caused the issue is identified
D. An owner is assigned to every issue
A. Individual team members try to outperform one another.
B. Individual skills improvement so team members can perform assignments more effectively.
C. Improvements in competencies that raise overall team performance.
D. Reduced staff turnover rate.
A. Actual Cost (AC)
B. Total cost estimate
C. Estimated Cost at Completion (EAC)
D. Budget at Completion (BAC)
A. Reallocate funds from another project.
B. Renegotiate other areas of the budget.
C. Proceed with the project and hope that things sort out.
D. Use a contingency budget.
A. technical capability
B. open change requests
C. understanding of need
D. cost
A. Determining resource availability
B. Isolating Quality concerns
C. Distributing tasks
D. Predicting Cost and Schedule Overruns
A. Project initiation
B. Project control
C. Project execution
D. Project planning
A. Asymptote
B. Aspect
C. Assumption
D. Assertion
A. Scope change
B. Risk prevention
C. Bug fixes
D. Project planning
A. Control
B. Initiation
C. Closure
D. Planning
A. Scope Creep
B. Scope Drip
C. Screening
D. Blind Screening
A. Project execution phase
B. After the project is completed
C. Project planning phase
D. Project closure phase
E. Project initiation phase
A. Burndown charts
B. Network diagrams
C. Code register
D. WBS
A. Risk mitigation
B. Risk prevention
C. Risk acceptance
D. Risk consequences
A. Make-or-buy analysis
B. Time-and-materials contract
C. Procurement analysis
D. Project planning
A. Project Cost Management
B. Performance Management
C. Project Communications Management
D. Project Quality Management
A. Performance control
B. Integrated Change Control
C. Performance plan
D. Plan management
A. Performance
B. Quality
C. Earned value
D. Gold-plating
A. Risk mitigation
B. Risk prevention
C. Risk planning
D. Risk analysis
A. Scope, quality, stakeholders
B. Expertise, communication, tools
C. Scope, schedule, cost
D. Time, cost, schedule
A. Evaluate the impact and communicate to the team.
B. Hope that later activities will make up for the loss of time.
C. Add additional resources to future activities.
D. Renegotiate shorter time estimates on future activities.
A. Matrix
B. Projectized
C. Enterprise
D. Hierarchy
A. Review Project Plan
B. Prototypes
C. Interviews
D. Questionnaires and surveys
A. Project initiation
B. Project execution
C. Project control
D. Project planning
A. Performance Plan
B. Change Management Plan
C. Project Charter
D. Project Management Plan
A. Quality team
B. Project manager
C. Project management team
D. Business analysis team
E. Development team
A. Stakeholders effected, communication requirements
B. Contact, history
C. Cost impact, schedule impact
D. Probability, impact
A. Plan procurements
B. Retain procurements
C. Conduct procurements
D. Administer procurements
A. Overrun
B. Wideband
C. Gap
D. Float
A. To authorize a project or phase of a project.
B. To design a quality software project.
C. To ensure that the work necessary, and only the work necessary, to successfully complete the project has been defined.
D. To define and document stakeholders' needs to meet the project objectives.
A. Liabilities
B. Gold-plating
C. Scrap
D. Rework
A. A slower than desired progress in completing the scope of a project.
B. Features and deliverables not agreed to in the original plan.
C. That slimy guy with glasses.
D. When a client repeatedly adds new features during planning.
A. Scope plan
B. Project plan
C. Project charter
D. Preliminary plan
A. Safety
B. Self Performance
C. Self Actualization
D. Physiological
A. Expected value technique
B. Work Breakdown Structure
C. Peer Review
D. Delphi Technique
A. Cost of quality
B. Bottom-up estimating
C. Delphi method
D. Parametric estimating
A. To estimate team member energy level.
B. To show the organizational hierarchy of the project.
C. To visualize schedule progress.
D. To estimate remaining cost.
A. Sit back and relax, watch the project execute.
B. Investigate the possibilities for enlargement of financial budget for future problems?
C. Making clear and timely decisions
D. Discuss with all stakeholders, that the Projectmanager communicates with, about the status of the Project
A. The common practice of vertically sequencing the deliverables from most complex to least complex.
B. The look of project activities scheduled back to back on a Gantt chart.
C. The way that traditional project management rolls up costs.
D. The focus of traditional project managers to push communication through a hierarchy.
A. Quality audit
B. Fixed price contract
C. Deliverable inspection
D. Service level agreement
A. Overhead costs related to an activity.
B. Items needed before an activity can be done.
C. The documents needed to run a WBS meeting.
D. Time estimates for an activity.
A. Reserve
B. Planning
C. Hold back funds
D. Risk mitigation
A. Quality
B. Grade
C. Scope
D. Performance