ABCDEFGHIJKLMNOPQRSTUVWXYZ
1
SN#TopicsSN#TopicsTopSec
2
11.Recognize core terminology48Agile Frameworks/MethodologiesTerminology1.1
3
21.1.1 Define a project, product, program, portfolio, etc.491.Recognize when agile project management is appropriate
4
31.1.2 Define project management501.Identify the primary rationale for agile and traditional plan based projects
5
41.1.3 Define a business case512.Identify the key tenants/principles of agile
6
51.1.4 Define project scope523.Recognize hybridization
7
61.1.5 Define deliverables534.Define the use of transparency in Agile projects
8
71.1.6 Define a milestone and task545.Describe the principle of Servant Leadership
9
81.1.7 List components of a project556.Describe the process of engaging customers
10
91.1.8 List components of a business case567.Identify common agile methodologies
11
101.1.9 Define issues, risks, assumptions, and constraints57Identify attributes of plan iterations of a project
12
111.1.10 Identify features of traditional plan based delivery583.2.1 State the components of agile sequencing
13
121.1.11 Identify features of agile delivery593.2.2 Identify the factors/inputs for determining the framework (e.g.,time, scope, etc.)
14
131.1.12 Identify project management ethics (refer to PMI code of ethics)603.2.3 Identify Agile project progress metrics
15
141.Identify concepts and terminology of project management planning613.2.4 State the importance of Agile project tracking
Identify Concepts
1.2
16
151.Identify concepts of a project management plan (e.g., cost, quality, risk, schedule, etc.)623.3 Identify agile roles and responsibilities
17
162.Define the different types of resources (e.g., human and material)633.3.1 Define the role of the agile project lead
18
173.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.)643.3.2 Define the role of the agile project member
19
184.Identify the features of different organizational environments (e.g., co-location and virtual teams, decentralized and centralized organization, and organizational structures (functional, matrix, projectized))653.3.3 Identify good team principles in agile project management
20
195.Describe organizational structures (e.g., co-location and virtual teams, decentralized and centralized organization, and organizational structures (functional, matrix, projectized))663.3.4 Identify examples of team collaboration in agile project management
21
206.Identify benefits and concepts associated with risk register.673.4 Identify attributes of document project controls of an agile project
22
217.Identify benefits and concepts associated with the stakeholder register.683.4.1 Describe the project controls in agile projects
23
22Identify project roles and responsibilities693.4.2 Identify monitor and controlling techniques in agile projectsIdentify Project
Roles
1.3
24
231.Define the key stakeholder roles such as project managers, sponsors, team leaders, team members, project clients, etc.703.5 Identify components of an agile plan
25
242.Define the key stakeholder responsibilities such as713.5.1 Identify the components of a specific agile plan (e.g., Scrum, XP, Scaled Agile Framework, Kanban, etc.)
26
25project managers, sponsors, team leaders, team members, project clients, etc.723.6 Describe task management steps (e.g., Decomposition, Prioritize, etc.)
27
263.Identify leadership and management.733.6.1 Describe the task decomposition process in an agile project management
28
274.Identify tools and systems used for or associated with project management743.6.2 Describe the task prioritization process in an agile project managementIdentify Tools &
Systems
1.4
29
281.Identify the typical tools used for creating a project schedule753.6.3 Identify stakeholders of the final product
30
292.Define the characteristics and benefits of various project management tools5.176BAF
31
30Insert illustrations and text boxes771.Identify business analysis roles and responsibilities
32
315.Identify common problem-solving tools and techniques781.List critical/core stakeholder roles and responsibilities (e.g.,
Problem Solving
1.5
33
321.Define common information gathering tools or techniques79business analysts, business sponsor, process owner, product manager, product owner, etc.)
34
332.Describe the components of an effective meeting802.Define types of roles (internal vs external)
35
34Traditional Plan-Based Methodologies81Identify attributes of stakeholder communicationPlan-Based
Methodologies
2
36
351.Recognize when a traditional plan- based approach is appropriate824.2.1 List elements in a communication plan
37
361.Identify the primary rationale for traditional plan based projects834.2.2 Identify communication channels/tools
38
372.Identify the process groups and knowledge areas (e.g., cost, quality, risk, schedule, etc.)84Identify attributes related to gathering requirements
39
383.Identify project phases and the correct order of the phases854.3.1 List types of requirements (e.g.,functional, nonfunctional,stakeholder, security, solution,business, migrating, market, research, bench marking, etc.)
40
394.Define a typical project structure for a traditional plan-based approach864.3.2 List ways of gathering requirements
41
40Identify attributes of a project management plan schedule874.3.3 List tools used for capturing requirements (e.g., use case, userstories, process diagrams, etc.)
Project Management
2.2
42
411.Identify the steps to create a schedule884.3.4 Define requirements traceability matrix/product backlog
43
422.Define a work breakdown structure89Identify product roadmap attributes
44
433.List the types of dependencies (e.g., sequence, start to start, finish to start, etc.)904.4.1 Define what a product roadmap is
45
444.Define a critical path914.4.2 List product roadmap components
46
45Identify attributes of executing and controlling traditional plan-based projects924.4.3 Define a release plan
Plan-Based Project
2.3
47
461.Describe the project controls in traditional plan-based projects (e.g., earned value, baselines, etc.)93Identify components of product deliveryProjects
48
472.Identify monitor and controlling techniques in a traditional plan- based projects944.5.1 Define components of project/product acceptance (e.g., requirements traceability matrix/product backlog,Transition Plan, etc.)
49
Agile Frameworks
3
50
51
52
53
54
55
56
57
58
Identify Attributes
3.2
59
60
61
62
63
Agile Roles3.3
64
65
66
67
68
Doc Projects3.4
69
70
71
Agile Plan3.5
72
73
Task Management
3.6
74
75
76
77
BA4
78
79
80
81
82
SH4.2
83
84
85
Gathering Requirements
4.3
86
87
88
89
90
Roadmap4.4
91
92
93
94
Product Delivery
4.5
95
96
97
98
99
100