Scrum and Agile - Full Deck 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 are some things you can do to keep the team focused on and working towards the sprint goal?

A
  • Limit work (PI Planning/Sprint Planning)
  • Use charts (Burn-down, Burn-up, Cumulative Flow, Velocty)
  • Resolve roadblocks and impediments
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What are 4 different types of testing?

A
  • AS EARLY AS POSSIBLE DURING DEV: Automated Testing (Complex, multiple steps, repetitive, [regression])
  • DURING: Unit Testing (testing individual code)
  • AT END: UAT (end user evaluation)
  • AFTER END: Regression (does stuff still work)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What are 4 benefits of SAFe?

A
  • 30% happier employees
  • 35% increase in productivity
  • 50% faster time to market
  • 50% defect reduction
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

7 Core Competencies of Business Agility

A

1) Enterprise Solution Delivery
2) Agile Product Delivery
3) Team and Technical Agility
4) Organizational Agility
5) Lean-Agile Leadership
6) Lean Portfolio Management
7) Continuous Learning Culture

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

Name 5 SAFe Lean-Agile Principles

A

1) Assume variability; preserve options
2) Build incrementally with fast, integrated learning cycles (PDCA)
3) Unlock the intrinsic motivation of knowledge workers
4) Systems thinking
5) Economic view
6) Decentralize decision-making
7) Base milestones on objective evaluation of working systems
8) Visualize and limit WIP, reduce batch sizes, and manage queue lengths
9) Apply cadence, synchronize with cross-domain planning
10) Organize around value

ABUSED

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

What are some charts you can use to analyze the data?

A

1) Burn-Down
2) Burn-Up
3) Cumulative Flow
4) Velocity Chart

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
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
11
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
12
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
13
Q

What are some problem-solving/root-cause-analysis methods?

A

1) Agree on the problem
2) Fishbone
3) 5 Whys
4) Rewrite problem statement

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

5 Core Values of Scrum

A

RCOFC
1) Respect
2) Courage
3) Openness
4) Focus
5) Commitment

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

3 Pillars of Scrum

A

1) Transparency
2) Inspection
3) Adaption

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
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
17
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
18
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
19
Q

What chart shows work completed?

20
Q

What does a ‘Cumulative Flow’ chart show?

A

Tracks the progress of items from to-do to done

21
Q

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

A

Cumulative Flow

22
Q

What does a ‘Velocity chart’ show?

A

The average amount of work completed during a sprint

23
Q

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

A

Velocity Chart

24
Q

HOW WOULD YOU HANDLE: Mixed experience levels with Jira/Agile/Scrum among team members.

A
  • Cheat sheets (simple 1-pagers)
  • Small group or individual training sessions
  • Weekly tips and tricks
  • Workshops
  • Create site dedicated to Continuous Improvement
25
3 Artifacts of Scrum
1) Product Backlog 2) Sprint Backlog 3) Increment
26
Sprint Planning: Goal, Participants, Roles, Timebox, Result
GOAL: Establish Sprint Objective PARTICIPANTS: Everyone ROLES: o PO: Present priority items, clarify requirements o SM: Facilitate o DEVs: Feedback on workload and commitment TIMEBOX: 4 hrs max per 2-week sprint RESULT: Objective and Backlog
27
Daily Scrum: Goal, Participants, Roles, Timebox, Result
GOAL: Inspect progress towards goal PARTICIPANTS: o DEVs (mandatory) o SM (desirable) o PO (optional) ROLES: o DEVs: Share progress o SM: Facilitate, time-check o PO: Clarification TIMEBOX: 15 min RESULT: Progress and Obstacles
28
Sprint Review: Goal, Participants, Roles, Timebox, Result
GOAL: Inspect work done, Adapt backlog PARTICIPANTS: o DEVs (mandatory) o SM (mandatory) o PO (mandatory) o Stakeholders (recommended) ROLES: o PO: Overall presenter, Gather feedback o SM: Facilitate o DEVs: Present items, Discuss challenges o Stakeholders: Provide feedback TIMEBOX: 2 hrs max per 2-week sprint RESULT: Stakeholder feedback integrated, Items validated for release
29
Sprint Retro: Goal, Participants, Roles, Timebox, Result
GOAL: Inspect sprint, Adapt and Improve PARTICIPANTS: o DEVs (mandatory) o SM (mandatory) o PO (mandatory) ROLES: o PO: Participate in discussions o SM: Facilitate, Encourage open discussion o DEVs: Participate in discussions TIMEBOX: 1.5 hrs max per 2-week sprint RESULT: AIs, Improvement Items
30
What is Plan, Analyze, Design, Develop, Test, Implement, Maintain
SDLC phases
31
What does the following refer to? - 30% happier employees - 35% increase in productivity - 50% faster time to market - 50% defect reduction
4 benefits of SAFe
32
What does the following refer to? 1) Enterprise Solution **Delivery** 2) Agile Product **Delivery** 3) Team and Technical **Agility** 4) Organizational **Agility** 5) **Lean-Agile** Leadership 6) **Lean** Portfolio Management 7) Continuous Learning **Culture**
7 Core Competencies of Business Agility
33
What does the following refer to? 1) Economic view 2) Systems thinking 3) Assume variability; preserve options 4) Build incrementally with fast, integrated learning cycles (PDCA) 5) Base milestones on objective evaluation of working systems 6) Visualize and limit WIP, reduce batch sizes, and manage queue lengths 7) Apply cadence, synchronize with cross-domain planning 8) Unlock the intrinsic motivation of knowledge workers 9) Decentralize decision-making 10) Organize around value
SAFe Lean-Agile Principles
34
What does the following refer to? 1) Commitment 2) Focus 3) Openness 4) Respect 5) Courage
5 Core Values of Scrum
35
What does the following refer to? 1) Transparency 2) Inspection 3) Adaption
3 Pillars of Scrum
36
What is the Agile Manifesto for Software Development?
- **Working software** over comprehensive documentation - **Individuals and interactions** over processes and tools - **Responding to change** over following a plan - **Customer collaboration** over contract negotiation
37
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
The Agile Manifesto for Software Development
38
What are the 12 Principles behind the Agile Manifesto?
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
39
What are some major objects of Scrum?
Product Product Backlog Sprints Sprint Backlog User Story Release Spike
40
What is the typical scrum process from Backlog to Release?
Define/groom product backlog Sprint Planning Work on agreed items Daily Scrum Throughout = Backlog Refinement Sprint Review Sprint Retro Product Increment
41
When did Scrum originate?
1995
42
When did Kanban originate?
1940s (Toyota)
43
When should you use Scrum vs Kanban?
Scrum - Strict deadline and deliverable dates - Heavy cross-team collaboration Kanban - "Go with the flow" - Differing priorities and deadlines - Organizations who are new to Agile
44
What are some cons of Kanban and Scrum
Scrum - Can be challenging for less experienced teams - Requires meetings to review sprints Kanban - Deliverables can move slowly due to no time constraints
45
What are some key differences between Agile and Scrum
- 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
46
What are the Kanban 5 Core Principles?
1) Visualize the Workflow 2) Focus on Flow 3) Limit Work in Progress (WIP) 4) Make Process Policies Explicit 5) Continuous Improvement