Yay or Nay Flashcards

1
Q

User stories are tools used in agile to capture a description of a feature from the end user’s perspective.

A

Yay

Stakeholder perspective / requirement

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

User stories are only written by the product owner

A

Nay

Team members can also write them

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

A good user story is independent, valuable and complex

A

Nay

I.N.V.E.S.T.

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

Agile is for software development teams

A

Nay

Can be applied to other areas of the organization

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

Agile is based on systems thinking

A

Nay

Lean is based on systems thinking
Disciplined Agile applies design thinking

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

One of the DA principles is “be cool”

A

Nay

Be awesome or Be pragmatic

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

Instead of prescribing best practices, DA provides strategies for maximizing the benefits of agile

A

Yay

Process goals and decision points - no best practices

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

You can take control of your processes if you don’t know what your options are

A

Nay

Need to know options and trade-offs

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

You can’t necessarily understand the behavior of a complex adaptive system by understanding its individual parts

A

Yay

Need to understand interaction of individual parts

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

A DA Enterprise responds swiftly to changes in the marketplace

A

Yay

Business agility is built into the enterprise

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

The foundation layer includes DAD and other enterprise aspects of Dev Ops

A

Nay

DA Dev Ops is another layer

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

DA addresses all possible roles that will occur in an organization

A

Nay

Roles vary across organizations

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

A person may take on several roles in parallel

A

Yay

Multiple hats common for smaller teams/organizations

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

There is no room for managers in DA

A

Nay

Managers can be stakeholders or hold supporting role

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

Cross-functional, “whole” teams enable agility

A

Yay

“Whole” teams include team members with the skills to address the problem that it faces

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

Agile teams must be small and co-located

A

Nay

Depends on context

17
Q

Co-located teams should have a dedicated workroom

A

Yay

Ideal situation, but not prescriptive

18
Q

Members of a collaborative enterprise team become members of a work team

A

Nay

Not always - however, it is an option

19
Q

Business agility is sometimes referred to as enterprise agility

20
Q

It is possible to understand a complex adaptive system by understanding the individual parts

A

Nay

Complex adaptive systems cannot be understood just by understanding the individual parts

21
Q

The agile lifecycle requires a mature set of practices around continuous integration and continuous delivery

A

Nay

This applies to Continuous Delivery: Agile life cycle

22
Q

The lean lifecycle is a Kanban-based project life cycle

A

Yay

Lean is Kanban-based
Agile is Scrum-based

23
Q

A value stream begins with a great idea

A

Nay

Value stream begins and ends with the customer

24
Q

Value is realized when customer pays for the service

A

Nay

Value is defined by the customer

25
Minimum business increments are about building something quickly to demonstrate to the product owner
Nay MBI is to build the smallest enhancement to an existing product - for revenue MVP is take the smallest step to determine viability of a new product without a customer base - for discovery
26
Benefits of MBI include adding value to the customer and providing feedback that the right functionality is being built and can be validated as useful
Yay
27
MBIs should be sequenced in order of priority
Nay Sequence MBI in order of what can realize the most value more quickly than others
28
Hand-offs are a way to eliminate waste and delays
Nay Hand-offs add to waste/delay
29
"Five Whys" analysis focuses on the tasks and processes within one phase that contribute to waste
Nay Continuous validation required to build quality in
30
Delays are a major form of waste in software development
Yay
31
Using pull is a way to manage workflow in the face of uncertain timing for getting tasks done
Yay Pulling work when we are ready allows us to manage our own workload level
32
Kanban boards can provide much of the information that value stream maps do
Nay Kanban boards depicts the team’s high-level process in terms of state Value stream map depicts processes, the time spent performing them, the time taken between them, and the level of quality resulting from processes - Used to explore the effectiveness of existing processes and to propose improved ways of working
33
Attendance in communities of practice is mandatory
Nay Voluntary
34
Centre of excellence is often referred to as a guild
Yay
35
An organization may have serval communities of practice and several centers of excellence at the same time
Yay
36
"Context counts" is a Lean principle
Nay Context counts is a DA principle
37
Lean seeks to optimize the whole value stream, not just individual functions and teams
Yay