| A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
1 | SN# | Topics | SN# | Topics | Top | Sec | ||||||||||||||||||||
2 | 1 | 1.Recognize core terminology | 48 | Agile Frameworks/Methodologies | Terminology | 1.1 | ||||||||||||||||||||
3 | 2 | 1.1.1 Define a project, product, program, portfolio, etc. | 49 | 1.Recognize when agile project management is appropriate | ||||||||||||||||||||||
4 | 3 | 1.1.2 Define project management | 50 | 1.Identify the primary rationale for agile and traditional plan based projects | ||||||||||||||||||||||
5 | 4 | 1.1.3 Define a business case | 51 | 2.Identify the key tenants/principles of agile | ||||||||||||||||||||||
6 | 5 | 1.1.4 Define project scope | 52 | 3.Recognize hybridization | ||||||||||||||||||||||
7 | 6 | 1.1.5 Define deliverables | 53 | 4.Define the use of transparency in Agile projects | ||||||||||||||||||||||
8 | 7 | 1.1.6 Define a milestone and task | 54 | 5.Describe the principle of Servant Leadership | ||||||||||||||||||||||
9 | 8 | 1.1.7 List components of a project | 55 | 6.Describe the process of engaging customers | ||||||||||||||||||||||
10 | 9 | 1.1.8 List components of a business case | 56 | 7.Identify common agile methodologies | ||||||||||||||||||||||
11 | 10 | 1.1.9 Define issues, risks, assumptions, and constraints | 57 | Identify attributes of plan iterations of a project | ||||||||||||||||||||||
12 | 11 | 1.1.10 Identify features of traditional plan based delivery | 58 | 3.2.1 State the components of agile sequencing | ||||||||||||||||||||||
13 | 12 | 1.1.11 Identify features of agile delivery | 59 | 3.2.2 Identify the factors/inputs for determining the framework (e.g.,time, scope, etc.) | ||||||||||||||||||||||
14 | 13 | 1.1.12 Identify project management ethics (refer to PMI code of ethics) | 60 | 3.2.3 Identify Agile project progress metrics | ||||||||||||||||||||||
15 | 14 | 1.Identify concepts and terminology of project management planning | 61 | 3.2.4 State the importance of Agile project tracking | Identify Concepts | 1.2 | ||||||||||||||||||||
16 | 15 | 1.Identify concepts of a project management plan (e.g., cost, quality, risk, schedule, etc.) | 62 | 3.3 Identify agile roles and responsibilities | ||||||||||||||||||||||
17 | 16 | 2.Define the different types of resources (e.g., human and material) | 63 | 3.3.1 Define the role of the agile project lead | ||||||||||||||||||||||
18 | 17 | 3.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.) | 64 | 3.3.2 Define the role of the agile project member | ||||||||||||||||||||||
19 | 18 | 4.Identify the features of different organizational environments (e.g., co-location and virtual teams, decentralized and centralized organization, and organizational structures (functional, matrix, projectized)) | 65 | 3.3.3 Identify good team principles in agile project management | ||||||||||||||||||||||
20 | 19 | 5.Describe organizational structures (e.g., co-location and virtual teams, decentralized and centralized organization, and organizational structures (functional, matrix, projectized)) | 66 | 3.3.4 Identify examples of team collaboration in agile project management | ||||||||||||||||||||||
21 | 20 | 6.Identify benefits and concepts associated with risk register. | 67 | 3.4 Identify attributes of document project controls of an agile project | ||||||||||||||||||||||
22 | 21 | 7.Identify benefits and concepts associated with the stakeholder register. | 68 | 3.4.1 Describe the project controls in agile projects | ||||||||||||||||||||||
23 | 22 | Identify project roles and responsibilities | 69 | 3.4.2 Identify monitor and controlling techniques in agile projects | Identify Project Roles | 1.3 | ||||||||||||||||||||
24 | 23 | 1.Define the key stakeholder roles such as project managers, sponsors, team leaders, team members, project clients, etc. | 70 | 3.5 Identify components of an agile plan | ||||||||||||||||||||||
25 | 24 | 2.Define the key stakeholder responsibilities such as | 71 | 3.5.1 Identify the components of a specific agile plan (e.g., Scrum, XP, Scaled Agile Framework, Kanban, etc.) | ||||||||||||||||||||||
26 | 25 | project managers, sponsors, team leaders, team members, project clients, etc. | 72 | 3.6 Describe task management steps (e.g., Decomposition, Prioritize, etc.) | ||||||||||||||||||||||
27 | 26 | 3.Identify leadership and management. | 73 | 3.6.1 Describe the task decomposition process in an agile project management | ||||||||||||||||||||||
28 | 27 | 4.Identify tools and systems used for or associated with project management | 74 | 3.6.2 Describe the task prioritization process in an agile project management | Identify Tools & Systems | 1.4 | ||||||||||||||||||||
29 | 28 | 1.Identify the typical tools used for creating a project schedule | 75 | 3.6.3 Identify stakeholders of the final product | ||||||||||||||||||||||
30 | 29 | 2.Define the characteristics and benefits of various project management tools5.1 | 76 | BAF | ||||||||||||||||||||||
31 | 30 | Insert illustrations and text boxes | 77 | 1.Identify business analysis roles and responsibilities | ||||||||||||||||||||||
32 | 31 | 5.Identify common problem-solving tools and techniques | 78 | 1.List critical/core stakeholder roles and responsibilities (e.g., | Problem Solving | 1.5 | ||||||||||||||||||||
33 | 32 | 1.Define common information gathering tools or techniques | 79 | business analysts, business sponsor, process owner, product manager, product owner, etc.) | ||||||||||||||||||||||
34 | 33 | 2.Describe the components of an effective meeting | 80 | 2.Define types of roles (internal vs external) | ||||||||||||||||||||||
35 | 34 | Traditional Plan-Based Methodologies | 81 | Identify attributes of stakeholder communication | Plan-Based Methodologies | 2 | ||||||||||||||||||||
36 | 35 | 1.Recognize when a traditional plan- based approach is appropriate | 82 | 4.2.1 List elements in a communication plan | ||||||||||||||||||||||
37 | 36 | 1.Identify the primary rationale for traditional plan based projects | 83 | 4.2.2 Identify communication channels/tools | ||||||||||||||||||||||
38 | 37 | 2.Identify the process groups and knowledge areas (e.g., cost, quality, risk, schedule, etc.) | 84 | Identify attributes related to gathering requirements | ||||||||||||||||||||||
39 | 38 | 3.Identify project phases and the correct order of the phases | 85 | 4.3.1 List types of requirements (e.g.,functional, nonfunctional,stakeholder, security, solution,business, migrating, market, research, bench marking, etc.) | ||||||||||||||||||||||
40 | 39 | 4.Define a typical project structure for a traditional plan-based approach | 86 | 4.3.2 List ways of gathering requirements | ||||||||||||||||||||||
41 | 40 | Identify attributes of a project management plan schedule | 87 | 4.3.3 List tools used for capturing requirements (e.g., use case, userstories, process diagrams, etc.) | Project Management | 2.2 | ||||||||||||||||||||
42 | 41 | 1.Identify the steps to create a schedule | 88 | 4.3.4 Define requirements traceability matrix/product backlog | ||||||||||||||||||||||
43 | 42 | 2.Define a work breakdown structure | 89 | Identify product roadmap attributes | ||||||||||||||||||||||
44 | 43 | 3.List the types of dependencies (e.g., sequence, start to start, finish to start, etc.) | 90 | 4.4.1 Define what a product roadmap is | ||||||||||||||||||||||
45 | 44 | 4.Define a critical path | 91 | 4.4.2 List product roadmap components | ||||||||||||||||||||||
46 | 45 | Identify attributes of executing and controlling traditional plan-based projects | 92 | 4.4.3 Define a release plan | Plan-Based Project | 2.3 | ||||||||||||||||||||
47 | 46 | 1.Describe the project controls in traditional plan-based projects (e.g., earned value, baselines, etc.) | 93 | Identify components of product delivery | Projects | |||||||||||||||||||||
48 | 47 | 2.Identify monitor and controlling techniques in a traditional plan- based projects | 94 | 4.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 Roles | 3.3 | ||||||||||||||||||||||||
64 | ||||||||||||||||||||||||||
65 | ||||||||||||||||||||||||||
66 | ||||||||||||||||||||||||||
67 | ||||||||||||||||||||||||||
68 | Doc Projects | 3.4 | ||||||||||||||||||||||||
69 | ||||||||||||||||||||||||||
70 | ||||||||||||||||||||||||||
71 | Agile Plan | 3.5 | ||||||||||||||||||||||||
72 | ||||||||||||||||||||||||||
73 | Task Management | 3.6 | ||||||||||||||||||||||||
74 | ||||||||||||||||||||||||||
75 | ||||||||||||||||||||||||||
76 | ||||||||||||||||||||||||||
77 | BA | 4 | ||||||||||||||||||||||||
78 | ||||||||||||||||||||||||||
79 | ||||||||||||||||||||||||||
80 | ||||||||||||||||||||||||||
81 | ||||||||||||||||||||||||||
82 | SH | 4.2 | ||||||||||||||||||||||||
83 | ||||||||||||||||||||||||||
84 | ||||||||||||||||||||||||||
85 | Gathering Requirements | 4.3 | ||||||||||||||||||||||||
86 | ||||||||||||||||||||||||||
87 | ||||||||||||||||||||||||||
88 | ||||||||||||||||||||||||||
89 | ||||||||||||||||||||||||||
90 | Roadmap | 4.4 | ||||||||||||||||||||||||
91 | ||||||||||||||||||||||||||
92 | ||||||||||||||||||||||||||
93 | ||||||||||||||||||||||||||
94 | Product Delivery | 4.5 | ||||||||||||||||||||||||
95 | ||||||||||||||||||||||||||
96 | ||||||||||||||||||||||||||
97 | ||||||||||||||||||||||||||
98 | ||||||||||||||||||||||||||
99 | ||||||||||||||||||||||||||
100 |