PMI Project Management Ready™ Certification Practice Test

The PMI Project Management Ready practice test contains 91 questions covering the following objectives: 

Project Management Fundamentals and Core Concepts – 23 questions 

Recognize core terminology  

• Define a project, product, program, portfolio, etc. 
• Define project management 
• Define a business case  
• Define project scope 
• Define deliverables 
• Define a milestone and task 
• List components of a project
• List components of a business case  
• Define issues, risks, assumptions, and constraints 
• Identify features of traditional plan-based delivery 
• Identify features of agile delivery 
• Identify project management ethics (refer to PMI code of ethics) 

Identify concepts and terminology of project management planning  

• Identify concepts of a project management plan (e.g., cost, quality, risk, schedule, etc.) 
• Define the different types of resources (e.g., human and material) 
• Identify common terminology in business concepts related to project management (e.g., change management, culture, strategy, governance, trade-off, performance metrics, prioritization, categorization, work breakdown, reporting, conflict, accuracy vs. precision, leadership, and motivation, etc.) 
• Identify the features of different organizational environments (e.g., co-location and virtual teams, decentralized and centralized organization, and organizational structures (functional, matrix, projectized))
• Describe organizational structures (e.g., co-location and virtual teams, decentralized and centralized organization, and organizational structures (functional, matrix, projectized)) 
• Identify benefits and concepts associated with risk register. 
• Identify benefits and concepts associated with the stakeholder register. 

Identify project roles and responsibilities  

• Define the key stakeholder roles such as project managers, sponsors, team leaders, team members, project clients, etc.
• Define the key stakeholder responsibilities such as project managers, sponsors, team leaders, team members, project clients, etc. 
• Identify leadership and management.  

Identify tools and systems used for or associated with project management  

• Identify the typical tools used for creating a project schedule 
• Define the characteristics and benefits of various project management tools
• Insert illustrations and text boxes 

Identify common problem-solving tools and techniques  

• Define common information gathering tools or techniques    
• Describe the components of an effective meeting 

Traditional Plan-Based Methodologies – 16 questions 

Recognize when a traditional plan-based approach is appropriate  

• Identify the primary rationale for traditional plan-based projects 
• Identify the process groups and knowledge areas (e.g., cost, quality, risk, schedule, etc.) 
• Identify project phases and the correct order of the phases 
• Define a typical project structure for a traditional plan-based approach 

Identify attributes of a project management plan schedule  

• Identify the steps to create a schedule 
• Define a work breakdown structure 
• List the types of dependencies (e.g., sequence, start to start, finish to start, etc.) 
• Define a critical path 

Identify attributes of executing and controlling traditional plan-based projects  

• Describe the project controls in traditional plan-based projects (e.g., earned value, baselines, etc.) 
• Identify monitor and controlling techniques in a traditional plan-based projects 

Agile Frameworks/Methodologies – 26 questions 

Recognize when agile project management is appropriate 

• Identify the primary rationale for agile and traditional plan-based projects 
• Identify the key tenants/principles of agile 
• Recognize hybridization 
• Define the use of transparency in Agile projects
• Describe the principle of Servant Leadership 
• Describe the process of engaging customers 
• Identify common agile methodologies 

Identify attributes of plan iterations of a project  

• State the components of agile sequencing
• Identify the factors/inputs for determining the framework (e.g., time, scope, etc.) 
• Identify Agile project progress metrics 
• State the importance of Agile project tracking 

Identify agile roles and responsibilities 

• Define the role of the agile project lead
• Define the role of the agile project member 
• Identify good team principles in agile project management 
• Identify examples of team collaboration in agile project management 

Identify attributes of document project controls of an agile project  

• Describe the project controls in agile projects
• Identify monitor and controlling techniques in agile projects 

Identify components of an agile plan  

• Identify the components of a specific agile plan (e.g., Scrum, XP, Scaled Agile Framework, Kanban, etc.) 

Describe task management steps (e.g., Decomposition, Prioritize, etc.)  

• Describe the task decomposition process in an agile project management
• Describe the task prioritization process in an agile project management 
• Identify stakeholders of the final product 

Business Analysis Frameworks – 26 questions 

Identify business analysis roles and responsibilities  

• List critical/core stakeholder roles and responsibilities (e.g., business analysts, business sponsor, process owner, product manager, product owner, etc.)
• Define types of roles (internal vs external) 

Identify attributes of stakeholder communication  

• List elements in a communication plan  
• Identify communication channels/tools 

Identify attributes related to gathering requirements  

• List types of requirements (e.g., functional, nonfunctional, stakeholder, security, solution, business, migrating, market research, bench marking, etc.) 
• List ways of gathering requirements  
• List tools used for capturing requirements (e.g., use case, user stories, process diagrams, etc.) 
• Define requirements traceability matrix/product backlog 

Identify product roadmap attributes  

• Define what a product roadmap is 
• List product roadmap components 
• Define a release plan 

Identify components of product delivery  

• Define components of project/product acceptance (e.g., requirements traceability matrix/product backlog, Transition Plan, etc.)