CAPM MOD 10 Flashcards

1
Q

PMs want to focus on ___ metrics over ___

A

leading;lagging

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

__ steers project based on trends, projections, forward looking forecasts
__ and __ focus on what happened

A

PM; accountants and auditors

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

KPIs must be ___

A

SMART
* Specific - clearly defined
* Measurable – criteria to evaluate progress and results
* Achievable – team has skills and resources for it
* Relevant – accurately measures team’s performance
* Timely – start and end date

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

SMART =

A
  • Specific - clearly defined
  • Measurable – criteria to evaluate progress and results
  • Achievable – team has skills and resources for it
  • Relevant – accurately measures team’s performance
  • Timely – start and end date
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

main benefits of agile metrics

A
  • Track progress – can spot risks before they occur to avoid it
    o Plan next iteration
    o Allows forecasting and modeling
    o Measure tasks completed, project spend, customer satisfaction
    o Real-time metrics and reporting to keep up with fast-paced complex projects
  • Support decision making – capacity – can do more or less in next iteration
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Since requirements change over time in adaptive projects, there is __ emphasis on documentation
However, documenting __ is important

A

less; control

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

used to document ___
* Product backlog
* Definition of done (DoD)
* Definition of ready (DoR)
* Kanban board

A

control

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

things team works on – describes features, changes, bug fixes, infrastructure changes, or other activities team works on for specific outcome. Won’t be worked on it not on here, but just because it’s on here doesn’t mean it will be delivered

A

product backlog

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

criteria that ensures all work is complete and meets necessary quality standards before released (test finished, design approved, customer approved, known defects fixed?)

A

definition of done DOD

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

criteria met before user story is ready for development. (INVEST – Independent, negotiable, valuable, estimable, small, testable). Once met, spring transforms items that met DOR into DOD

A

Definition of ready DOR

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

visual control for items that shows state, progress, and work in progress items (like SG pipeline). Don’t want too much work in one stage ex: if too many items in “in progress column” there is a bottleneck in task execution. Not tasks finalization since that box is empty and tasks are moved out of pipeline quick once done

A

kanban board

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

__ projects __ __ capture lessons learned in __ after __

A

agile; more frequently; retrospectives; iterations

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

___ are processed faster than text

A

visuals

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

___ ___ is project board people can see to get information without asking questions

Shows info about team being on track, behind, ahead, etc.

A

information radiator

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

highlights pending work
o Shows amount of work done in an iteration and the total work remaining
o how quickly team is working through it’s tasks
o Helps team manage time to work at sustainable pace
o Doesn’t separate impact of changes in scope from rates for progress

A

burndown chart

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Adaptive project metrics can be communicated using:

A

burndown chart
velocity chart
cumulative flow diagram

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

rate team should work to finish tasks iteration by due date
o Above line – behind schedule
o Below line – ahead of schedule

A

ideal work line

18
Q

promised too much, underestimated complexity, overestimated team productivity

A

missed forecast

19
Q

sign that work hasn’t been estimated accurately – may lead to defects

A

sharp drop

20
Q

average # of incomplete stories over the previous 2-3 sprints

A

reserve/buffer needed

21
Q

trigger “interrupt” pattern where you need to replan or abort plan

A

buffer overflow

22
Q

= like burn down charts, but only show work that’s been completed
“ Monitor performance and progress
“ See scope increases
“ But don’t show the whole picture - like work in progress or how close team is to completion

A

Release burn up charts

23
Q

measure quantity of work done

A

velocity chart

24
Q

measure of team’s capacity during each iteration. How much work they can do in a time frame
* Used to project schedules and costs

  • Measured in storypoints
  • Easy metric to manipulate
  • Not easily compared across team – unique to each team
A

velocity

25
Q

number of units produced during a specific interval

associated with work in progress. Tasks started by not finished yet.
Limiting # of tasks can ensue better throughput ex: highway laned dedicated to busses

A

throughput

26
Q

ways to control cycle and lead times

A

control chart
lead time
throughput

27
Q

monitor cycle times and reveal possibly productivity improvements and problems
* Can compare productivity between teams if tasks are similar

A

control charts

28
Q

function of how many tasks enter system
Ex: when many tasks enter system at once, lead time for a task will increase since tasks will be waiting for execution. To much lead time needed means system’s capacity for demand is not sufficient

A

lead time

29
Q

visualizes task distribution – like kanban board
o Visualize effort overtime
o Analyze stability of work flow
o Understand project issues, cycle times, and completion dates

A
  • Cumulative flow diagram
30
Q
  • Cumulative flow diagram
A

lagging indicator

31
Q

trend line of predictor of future performance

A

leading indicator

32
Q

amount of time it takes to complete a task

A

cycle time

33
Q

duration between start and completion of a process

A

lead time

34
Q

Uncertainty emerges from:

A
  • Project
  • Stakeholders
  • Context
35
Q

PESTLE

A

Consider Political, economic, social, technological, legal, environmental, competitive (PESTLE) that can affect project

36
Q

conditions leading to ___
* Project complexity
* System dynamics
* Time pressure
* Technological novelty
* Uniqueness

A

Conditions leading to uncertainty:

37
Q

ways to…

  • regular review and feedback sessions with stakeholders
  • daily standup
  • impediment log
  • demo products for feedback more frequently
  • test and experiment
A

ways to track and manage risk in adaptive projects

38
Q
A
39
Q

to identify threats and opportunities/ team cohesion
o share details of work done and planned
o share roadblocks and issues to be logged

A

daily standups

40
Q

impact x probability =

A

risk severity

41
Q

conditions of __ may produce __

can’t know every possible risk but can be –__ about managing risks

A

uncertainty; risk; proactive