Chapter 2: An overview of agile Flashcards

some history behind agile and what it is today •agile basics including the frameworks, behaviours, concepts and techniques

1
Q

What is Agile?

A

The term ‘agile’ is very broad and is viewed in many different ways throughout the agile community. There is a set of well-known frameworks referred to as ‘agile methods’ and there are also well-known behaviours, concepts and techniques that are recognized as characterizing the agile way of working. But there is no single definition of agile that accurately encapsulates them all, although the Agile Manifesto (see Figure 2.1) comes the closest to achieving this.

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

What is Agile?

A

The term ‘agile’ is very broad and is viewed in many different ways throughout the agile community. There is a set of well-known frameworks referred to as ‘agile methods’ and there are also well-known behaviours, concepts and techniques that are recognized as characterizing the agile way of working. But there is no single definition of agile that accurately encapsulates them all, although the Agile Manifesto (see Figure 2.1) comes the closest to achieving this.

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

What are the main points of the Agile manifesto?

A
  • Individuals and interactions OVER Processes and tools
  • Working software OVER Comprehensive documentation
  • Customer collaboration OVER Contract negotiation
  • Responding to change OVER Following a plan
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What’s the contract between waterfall and agile phases?

A

Waterfall: Linear, serial <—-> Agile: Iterative and incremental

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

Does the Agile manifesto only apply to developing software?

A

No…
By definition, the Agile Manifesto only applies to developing software; most of its underlying principles appear to suggest that this is in the context of the continual timeboxed development of a software product. Although it was created as a way to develop software, it has since been recognized as a successful approach beyond software development. Many people use the Agile Manifesto, replacing the word ‘software’ with ‘products’ or ‘solutions’.

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

What’s the contract between waterfall and agile phases?

A

Waterfall: Linear, serial <—-> Agile: Iterative and incremental

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

Does the Agile manifesto only apply to developing software?

A

No…
By definition, the Agile Manifesto only applies to developing software; most of its underlying principles appear to suggest that this is in the context of the continual timeboxed development of a software product. Although it was created as a way to develop software, it has since been recognized as a successful approach beyond software development. Many people use the Agile Manifesto, replacing the word ‘software’ with ‘products’ or ‘solutions’.

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

Agile uses the term value or benefit?

A

Value…also check MVP

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

What’s the contract between waterfall and agile phases?

A

Waterfall: Linear, serial <—-> Agile: Iterative and incremental

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

Does the Agile manifesto only apply to developing software?

A

No…
By definition, the Agile Manifesto only applies to developing software; most of its underlying principles appear to suggest that this is in the context of the continual timeboxed development of a software product. Although it was created as a way to develop software, it has since been recognized as a successful approach beyond software development. Many people use the Agile Manifesto, replacing the word ‘software’ with ‘products’ or ‘solutions’.

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

What does a basic backlog and sprint structure for delivering software look like?

A

Product backlog (perhaps in form of user stories) –> [ Sprint backlog –> Spirnt (daily stand-up meetings)] (repeat) –> Shippable product

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

What does a basic backlog and sprint structure for delivering software look like?

A

Product backlog (perhaps in form of user stories) –> [ Sprint backlog –> Spirnt (daily stand-up meetings)] (repeat) –> Shippable product

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

Does the Agile manifesto only apply to developing software?

A

No…
By definition, the Agile Manifesto only applies to developing software; most of its underlying principles appear to suggest that this is in the context of the continual timeboxed development of a software product. Although it was created as a way to develop software, it has since been recognized as a successful approach beyond software development. Many people use the Agile Manifesto, replacing the word ‘software’ with ‘products’ or ‘solutions’.

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

What are the characteristics agile uses in general?

A

*a timeboxed and iterative approach to delivering software

*a collection of techniques such as daily stand-up meetings, sprints and user stories

*the Scrum framework (see Table 2.1).

10
Q

Does the Agile manifesto only apply to developing software?

A

No…
By definition, the Agile Manifesto only applies to developing software; most of its underlying principles appear to suggest that this is in the context of the continual timeboxed development of a software product. Although it was created as a way to develop software, it has since been recognized as a successful approach beyond software development. Many people use the Agile Manifesto, replacing the word ‘software’ with ‘products’ or ‘solutions’.

10
Q

What are the characteristics agile uses in general?

A

*a timeboxed and iterative approach to delivering software

*a collection of techniques such as daily stand-up meetings, sprints and user stories

*the Scrum framework (see Table 2.1).

10
Q
A
10
Q

What does a basic backlog and sprint structure for delivering software look like?

A

Product backlog (perhaps in form of user stories) –> [ Sprint backlog –> Spirnt (daily stand-up meetings)] (repeat) –> Shippable product

10
Q

Definition: Release

A

The set of products in a handover. The contents of a release are managed, tested and deployed as a single entity.

In PRINCE2 Agile, a release is typically a container for more than one low-level timebox (e.g. a sprint). This is not always the case as the act of releasing features into operational use may happen more regularly (e.g. after each sprint or several times during a sprint). The term ‘deployment’ is sometimes used in agile and has a similar meaning, although it is not used in PRINCE2 Agile.

11
Q

What is a product roadmap?

A

It is a plan of how a product will evolve.

12
Q
A
12
Q

Does the Agile manifesto only apply to developing software?

A

No…
By definition, the Agile Manifesto only applies to developing software; most of its underlying principles appear to suggest that this is in the context of the continual timeboxed development of a software product. Although it was created as a way to develop software, it has since been recognized as a successful approach beyond software development. Many people use the Agile Manifesto, replacing the word ‘software’ with ‘products’ or ‘solutions’.

12
Q

What is a product roadmap?

A

It is a plan of how a product will evolve.

12
Q

Definition: Flow-based

A

This avoids the use of partitioning work into timeboxes and manages work by using a queue. Work is then continually pulled into the system (which may itself be a high-level timebox) and moves through various work states until it is done.

13
Q

Definition: Flow-based

A

This avoids the use of partitioning work into timeboxes and manages work by using a queue. Work is then continually pulled into the system (which may itself be a high-level timebox) and moves through various work states until it is done.

13
Q
A
13
Q

Agile methods and approaches

A
13
Q

What is a product roadmap?

A

It is a plan of how a product will evolve.

13
Q

Does the Agile manifesto only apply to developing software?

A

No…
By definition, the Agile Manifesto only applies to developing software; most of its underlying principles appear to suggest that this is in the context of the continual timeboxed development of a software product. Although it was created as a way to develop software, it has since been recognized as a successful approach beyond software development. Many people use the Agile Manifesto, replacing the word ‘software’ with ‘products’ or ‘solutions’.

14
Q
A
14
Q

What is a product roadmap?

A

It is a plan of how a product will evolve.

15
Q

Does the Agile manifesto only apply to developing software?

A

No…
By definition, the Agile Manifesto only applies to developing software; most of its underlying principles appear to suggest that this is in the context of the continual timeboxed development of a software product. Although it was created as a way to develop software, it has since been recognized as a successful approach beyond software development. Many people use the Agile Manifesto, replacing the word ‘software’ with ‘products’ or ‘solutions’.

15
Q

Agile methods and approaches

A
  • ASD (Adaptative Software Development): IT only | Iterative dev process
  • Crystal: IT only | Iterative dev method
  • DAD (disciplined Agile Delivery): IT only | Entreprise-wide scalable process framework
  • DevOps: IT only | a collaborative approach between dev and operations aimed at creating a product or service where the two types of work and even teams merge as much as possible
  • DSDM (Dynamic Systems Development Method)/ AgilePM: An agile project framework that focuses on the iterative delivery of business systems through the use of timeboxing and continual business involvement. It has a defined process and corresponding set of products, a set of roles that operate at all levels of a project, eight guiding principles and a collection of key techniques that can be used throughout a project.
  • Kanban: A way to improve flow and provoke system improvement through visualization and controlling work in progress.
  • Lean: An approach that focuses on improving processes through maximizing value by eliminating waste (such as wasted time and wasted effort).
  • Lean startup: Originally an approach to creating and managing start-up companies, but now applied to any business, to help them deliver products to customers quickly.
  • SAFe (Scaled Agile Framework): IT only |
  • Scrum: An iterative timeboxed approach to product delivery that is described as ‘a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems’ (see Appendix H).
  • XP (eXtreme Programming): IT Only |
16
Q

How does PRINCE2 Agile regards Agile?

A

PRINCE2 Agile regards agile as a family of behaviours, concepts, frameworks and techniques.

17
Q

What are examples of Agile behaviors?

A
  • Being collaborative
  • Self-organizing
  • Customer-focused
  • Empowered
  • Trusting not blaming

Similar terms: Principles, values, mindset

18
Q

What are examples of Agile concepts?

A
  • Prioritizing what is delivered
  • Working iteratively and incrementally
  • not delivering everything
  • Time-focused
  • Inspect and adapt
  • Kaizen
  • Limiting work in progress

Similar terms: Fundamentals

19
Q

What are examples of Agile techniques?

A
  • Burn charts
  • User stories
  • retrospectives
  • timeboxing
  • measuring flow

Similar terms: Practices, tools