Scrum and Agile - Full Deck Flashcards

Objective 1 (36 cards)

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

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

A little more intimate than an Inside Out

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

3 Artifacts of Scrum

A

1) Product Backlog
2) Sprint Backlog
3) Increment

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

What are some major objects of Scrum?

A

Product
Product Backlog
Sprints
Sprint Backlog
User Story
Release
Spike

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

Sprint Planning: Goal, Participants, Roles, Timebox, Result

A

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

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

Daily Scrum: Goal, Participants, Roles, Timebox, Result

A

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

17
Q

Sprint Review: Goal, Participants, Roles, Timebox, Result

A

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

18
Q

Sprint Retro: Goal, Participants, Roles, Timebox, Result

A

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

19
Q

What is Plan, Analyze, Design, Develop, Test, Implement, Maintain

20
Q

What does the following refer to?
- 30% happier employees
- 35% increase in productivity
- 50% faster time to market
- 50% defect reduction

A

4 benefits of SAFe

21
Q

What does the following refer to?
1) Commitment
2) Focus
3) Openness
4) Respect
5) Courage

A

5 Core Values of Scrum

22
Q

What does the following refer to?
1) Transparency
2) Inspection
3) Adaption

A

3 Pillars of Scrum

23
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
24
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

25
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
26
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
27
When did Scrum originate?
1995
28
When did Kanban originate?
1940s (Toyota)
29
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
30
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
31
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
32
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
33
What is a Spike?
A short, focused investigation or experiment aimed at reducing uncertainty or gathering more info about something
34
What is the difference between a Scrum Master and a Project Manager?
- Unlike a Project Manager, a Scrum Master does not have direct authority of the team - A Project Manager's goal is to ensure the project is completed on time and on budget - A Scrum Master's goal is to ensure the team is best set up to complete that project on time and on budget
35
How do you measure the success or performance of a Scrum Team?
- Use both qualitative and quantitative metrics - Quantitative: Charts and metrics - Qualitative: Team satisfaction, anonymous surveys
36
How do you handle scope changes during a sprint?
- Discuss as a team - Evaluate the impact - Does it align with the end goal? - Is it a want or a need? - What are the risks/issues? - Decide as a team how to move forward