Reverse Triangle Flashcards

1
Q

Why executives like being agile?

A

Efficiency: speed and quality

  • Agile teams are very productive, PO/SM protect the team from distractions, self-organized
  • Lean: minimize non productive tasks
  • Easier to understand development progress: simple, timely, on-demand visual support

Increased ROI opportunity

  • Functionalities delivered earlier: speed-to-market advantage
  • Product quality is higher
  • Products can self-fund
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Why customers like being agile?

A

Improved adaptation to change

  • Even at later phases
  • Features and changes based on priority
  • Business priority always aligned with development activities
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Why management like being agile?

A

Higher quality

Less product and process waste (Lean)

Emphasis on value

  • fewer, shorter, focused meetings
  • barely sufficient documentation
  • joint responsibility customer-team for quality and value
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Why development team like being agile?

A

Power and respect to organize themselves

Sustainable pace of work

SM remove impediments and distractions

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

TPM Iron Triangle

A

Guess driven

Fixed requirements (Scope), estimate resources (cost) and time

(bonus) Resource and time estimation
- Analogy estimation: look at similar projects
- Parametric: breakdown into know parameters
- Expert: scenario analysis

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

APM Iron Triangle

A

Priority driven

Fixed resources and time, estimated feature

You don’t know what the final product will look like

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

Advantage of APM vs TPM

A

More stable to introduce changes over time, not at once later

Faster and less costly failure (lower risk)

  • Easier and more frequent opportunities to detect failure
  • Assessment and action opportunity every few weeks
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

How the customer is treated in Agile?

A

Agile is customer focused as well as client focus

  • client: pays for the product or service development
  • customer: end user

Rarely the client understand exactly what the customer needs

First step for development teams is to understand not only client requirements but also final users needs.

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

Tools to understand who is the customer

A

Product Canvas or Business Model Canvas

Customer maps (empathy and journey map) and Customer Interviews

Product discovery workshop

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

Tools to identify root causes of customer problems

A

Pareto rule

5 why’s

Ishikawa (fishbone)

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

How does the Product Canvas work?

A

Template with 12 slots

Used to explore and understand product’s key elements to find the sweet spot

“Discover a valuable, usable and feasible product” -> sweet spot

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