Section 16: Mindset

Question 1

What is the purpose of the “mindset” section?

Answer 1

A concise review of exam-focused bulleted points (traditional, agile, hybrid) to guide how you choose answers; watch all prior videos first.

Question 2

Should I watch other videos before this section?

Answer 2

Yes — this section assumes you’ve completed the earlier lessons; it’s a review, not a primary course.

Question 3

How many mindsets are there?

Answer 3

Two main mindsets — Traditional (predictive) and Agile — plus a Hybrid approach combining both.

Question 4

How should I approach unknown project types at work?

Answer 4

Be prepared for either: know both traditional and agile methods so you can manage any project.

Question 5

How often should stakeholders be identified?

Answer 5

Continuously — stakeholder identification and analysis happens throughout the project.

Question 6

Why keep identifying stakeholders?

Answer 6

To learn changing needs, tailor communications, and update engagement strategies.

Question 7

What must happen before changing the project plan in a traditional project?

Answer 7

Submit, assess, and approve a documented change request (use your change control process / CCB).

Question 8

How are changes handled differently in Agile?

Answer 8

Add requested changes as product-backlog items and reprioritize — no formal change-request required.

Question 9

What should you do before taking action on an issue?

Answer 9

Don’t act impulsively — analyze the problem, create a plan/strategy, consult stakeholders and team.

Question 10

Who should be consulted when making decisions about how to do work?

Answer 10

The project team — they are subject-matter experts and give practical, implementable solutions.

Question 11

How should final decisions be chosen?

Answer 11

Select the option that best meets the project’s objectives and delivers the most value.

Question 12

When solving problems, should you use complex tools or simple methods?

Answer 12

Prefer simple, inclusive tools (whiteboards, face-to-face) to encourage participation and speed.

Question 13

How should scope changes be assessed?

Answer 13

Evaluate impacts on schedule, cost, quality, resources, communications, risk, procurement, and stakeholder engagement.

Question 14

Which estimation method is preferred for accuracy?

Answer 14

Bottom-up with expert judgment (more accurate but more work); use top-down only for early/initiation estimates.

Question 15

What is the project manager’s main role?

Answer 15

Integrator — coordinate and balance all knowledge areas so the project delivers as a whole.

Question 16

Should you focus on one knowledge area and ignore others?

Answer 16

No — monitor all areas (scope, schedule, cost, quality, risk, communications, stakeholders, procurement, resources).

Question 17

What must be maintained throughout the project for knowledge transfer?

Answer 17

A lessons-learned register — update it continuously so future projects can benefit.

Question 18

What must be done before formally closing a project?

Answer 18

Pay outstanding bills, release resources formally, and complete administrative closeout.

Question 19

If a project is terminated early, must you still close it formally?

Answer 19

Yes — perform formal close (pay bills, release resources, document lessons learned) even if stopped early.

Question 20

Who is best to break down work and estimate activities?

Answer 20

The project team (they perform the work and give the most realistic estimates and sequencing).

Question 21

When should quality requirements be defined and checked?

Answer 21

Define early (during requirements) and check frequently throughout execution and control quality.

Question 22

Who should validate deliverables for scope and quality?

Answer 22

The customer/end users — they are best positioned to confirm conformance and acceptance.

Question 23

How should team conflict be handled?

Answer 23

First find the root cause, then resolve in a way that benefits project objectives (not to favor one person).

Question 24

What should you do before sending communications to stakeholders?

Answer 24

Analyze stakeholder needs: what info, frequency, delivery method, and who should send it.

Question 25

Why is emotional intelligence important?

Answer 25

It helps read others, manage feelings, de-escalate conflict, coach and motivate teams, and meet stakeholder needs.

Question 26

When should risks be identified?

Answer 26

As early and as often as possible — risk ID and assessment is continuous throughout the project.

Question 27

What types of risk must be identified?

Answer 27

Both negative (threats) and positive (opportunities).

Question 28

Where are identified risks recorded?

Answer 28

The risk register.

Question 29

What risk analysis steps are used?

Answer 29

Qualitative (probability/impact ranking) and quantitative (numeric impact), then plan responses (mitigate, transfer, accept, exploit, etc.).

Question 30

How should procurement contracts be chosen?

Answer 30

Select contracts that are mutually beneficial to buyer and seller and that support project objectives.

Question 31

How often should stakeholders be engaged?

Answer 31

Early, often, and regularly — use meetings, demos, one-on-ones, presentations to keep them involved.

Question 32

What is the Agile PM’s leadership style?

Answer 32

Servant leader: empower the team, remove impediments, give tools and support, don’t dictate.

Question 33

Who prioritizes the product backlog?

Answer 33

The Product Owner — never prioritize it yourself; coach the Product Owner if they refuse.

Question 34

What communication setup helps an Agile team?

Answer 34

Co-location, face-to-face interaction, lots of wall space and whiteboards for visual, shared work.

Question 35

What are “information radiators”?

Answer 35

Visible displays (big charts, burnup/burndown, Kanban) that show project status at a glance.

Question 36

Who should resolve problems in Agile?

Answer 36

The project team — let them choose solutions while you coach and support.

Question 37

How should disagreements within the team be treated?

Answer 37

Encourage safe disagreement — it can produce better solutions; avoid punishing dissent.

Question 38

What is the purpose of a Kanban board?

Answer 38

Limit work-in-progress (WIP), reveal bottlenecks, and make flow visible.

Question 39

Why continually re-communicate the project vision?

Answer 39

To keep the team focused, motivated, and aligned with the project’s purpose and benefits.

Question 40

How do you keep the team motivated?

Answer 40

Use emotional intelligence to identify motivators, adjust rewards/conditions, and vary incentives.

Question 41

Why show what failure looks like?

Answer 41

To highlight consequences, prevent issues, and focus team on avoiding costly mistakes.

Question 42

What is "fail fast"?

Answer 42

Deliver early, get feedback quickly, detect failures early and fix them before production.

Question 43

What ethical behaviors are essential on projects?

Answer 43

Honesty, transparency, never hiding or lying — build and protect trust with the team and stakeholders.

Question 44

What are retrospectives and when are they held?

Answer 44

End-of-iteration reviews (retrospectives) to identify what to start/stop/continue — create feedback loops.

Question 45

What is a feedback loop?

Answer 45

Take lessons learned from one iteration and immediately apply them to the next task/sprint.

Question 46

How should lessons learned be used in Agile and Traditional projects?

Answer 46

Capture continuously and apply the lessons to future work — don’t just record them and ignore them.