Agile Manifesto & Agile doesn't fit everywhere Flashcards

1
Q

Agile manifesto

A

Agreed upon a set of agile values and principles. (4 values and 12 clarifying principles, along with core practices)

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

When might it make more sense to use an agile approach?

A

When there is a high uncertainty of work.

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

Stacey complexity model

A

The Stacey Complexity Model helps determine the best approach to decision-making and management based on the level of certainty and agreement about a project or problem. It divides scenarios into four zones. This model helps identify when traditional project management works versus when adaptive, flexible methods are needed. (tech vs requirement uncertainty)

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

Simple zone (Stacey model)

A

High certainty and agreement. Use standard processes and best practices.

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

Complicated zone

A

Certainty is high, but agreement requires expert analysis. Use expert judgment and structured approaches.

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

Complex zone

A

Low certainty and agreement. Use iterative methods (e.g., Agile) and experimentation.

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

Chaotic zone

A

No certainty or agreement. Immediate action is required to stabilize the situation before planning.

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

Predictive (waterfall) approach

A

The frequency of delivery is low, and the degree of change is low. Fixed requirements, activities performed once for the entire project, single delivery, the goal is to manage cost.

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

Iterative approach

A

We get feedback all the time. Deliveries are low-frequency and high-degree of change. Dynamic requirements and activities are repeated until correct, and there is a single delivery. The goal is the correctness of the solution. Practical when a product or result must go through successive prototypes or proofs of concept before final release.

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

Incremental approach

A

Delivering in increments. High degree of delivery and low degree of change. Dynamic requirements, activities performed once for a given increment, frequent smaller deliveries, goal is speed.

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

Adaptive (Agile) approach

A

The frequency of delivery is high, and the degree of change is high. Dynamic requirements and activities are repeated until correct, with frequent small deliveries and customer value via frequent deliveries and feedback.

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

Hybrid approach

A

A mix of various approaches with retrospectives. It may be used as a transition strategy to a different approach. Uses some parts of predictive and some parts of agile.

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

Retrospective

A

A structured meeting held at the end of a project or a specific project phase (common in Agile/Scrum) to reflect on what went well, what didn’t, and how processes can improve in the future.

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

Mostly agile with some predictive (hybrid)

A

Integrating an external component developed in full by an external vendor means that a single iteration might be required after their component is delivered.

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

Mostly waterfall with some agile

A

Delivering a straightforward project but trialing a new material in incremental releases.

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

A combined predictive and agile approach

A

A linear project, where tasks are tracked using Kanban and daily scrums are used for updating work.

17
Q

Issue: Demand pattern is sporadic

A

Build in a cadence (sprint or regular timebox) to help the team demo, retrospect, and take in new work.

18
Q

Issue: A new team who needs process improvement

A

Retrospect more often and select improvements

19
Q

Issue: Flow of work is often delayed or interrupted

A

Make the work visible using Kanban boards, and limit the work in progress.

20
Q

Issue: Quality of deliverables is poor

A

Consider using the Test Driven Development practices (test-first), finding the root cause through retrospectives and error-proofing.

21
Q

Issue: More than one team is needed to build a product

A

Use Agile scaling frameworks, starting with Scrum of Scrums.

22
Q

Issue: Team is new to Agile approaches

A

Start by training team members in Fundamentals of the Agile mindset and principles. Workshop a specific approach once chosen.