Scrum and Agile Flashcards

Objective 1

1
Q

What does ‘INVEST’ stand for?

A
  • Independent
  • Negotiable
  • Valuable
  • Estimable
  • Small
  • Testable
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Name 5 methods you can use to split (break down) stories?

A
  • Workflow steps
  • Business rule variations
  • Minor/Major effort
  • Variations in data
  • Data entry methods
  • Defer system qualities
  • Operations
  • Use case scenarios
  • Break out spike
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What are the SDLC phases?

A

PADDTIM
* Plan
* Analyze
* Design
* Develop
* Test
* Implement
* Maintain

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

What is an ‘Inside-Out’?

A

A team member prepares a short presentation or flip chart talk for their team.
- Once every 2-4 weeks
- 30-60 minutes
- John will be sharing his knowledge on a new software we will be developing

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

What is a ‘BCB’?

A

Book and Coffee Break: Discuss a book on a new practice, technology, etc.
- Once per month
- 3-4 people
- 30-60 minutes

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

What is a ‘Coding Dojo’?

A

Developers and/or testers gather to discuss programming and testing challenges.
- 1-2 people sit at the computer and project onto a screen. As they code, people comment out loud. After 5-8 minutes, people rotate.
- 1-2 times per month
- 60-90 minutes

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

What does a ‘Burn-Down’ chart show?

A

Work remaining

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

What chart shows work remaining?

A

Burn-Down chart

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

What does a ‘Burn-Up’ chart show?

A

Work completed

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

What chart shows work completed?

A

Burn-Up

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

What does a ‘Cumulative Flow’ chart show?

A

Tracks the progress of items from to-do to done

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

What chart tracks the progress of tasks from to-do to done

A

Cumulative Flow

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

What does a ‘Velocity chart’ show?

A

The average amount of work completed during a sprint

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

What chart shows the average amount of work completed during a sprint?

A

Velocity Chart

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

What is the Agile Manifesto for Software Development?

A
  • Working software over comprehensive documentation
  • Individuals and interactions over processes and tools
  • Responding to change over following a plan
  • Customer collaboration over contract negotiation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What does the following refer to?
- Working software over comprehensive documentation
- Individuals and interactions over processes and tools
- Responding to change over following a plan
- Customer collaboration over contract negotiation

A

The Agile Manifesto for Software Development

17
Q

What are the 12 Principles behind the Agile Manifesto?

A

1) Motivated individuals
2) Self-organized teams
3) Face-to-Face Conversations
4) Customer satisfaction
5) Frequent delivery
6) Continuous improvement
7) Changing requirements
8) Simplicity
9) Technical excellence
10) Measure progress
11) Promoting collaboration
12) Maintain a constant pace

Motivated self-organized face-to-face customers frequently continuously change simple technical measures promoting maintenance

18
Q

What are some key differences between Agile and Scrum

A
  • Scrum is always Agile, but Agile is not always Scrum
  • Agile is a broad philosophy, while Scrum is a framework/methodology within that philosophy.
  • Agile focuses on continuous delivery, while Scrum delivers value in small increments
19
Q

What are the Kanban 5 Core Principles?

A

1) Visualize the Workflow
2) Focus on Flow
3) Limit Work in Progress (WIP)
4) Make Process Policies Explicit
5) Continuous Improvement