Vision_Stories_Epics_Capabilities_Features Flashcards

1
Q

The _________ is a description of the future state of the product or Solution.

A

Vision

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

Vision can be displayed as a postcard from the _______

A

future

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

True or False: A vision should be aspirational, yet realistic and achievable.

A

True

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

True or False: A vision should be motivational enough to engage others on the journey.

A

True

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

An _____ is a container for a significant Solution development
initiative that captures the more substantial investments that occur
within a portfolio .

A

Epic

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q
A \_\_\_\_\_\_\_\_ is a service that fulfills a 
stakeholder need and includes a name, a benefit 
hypothesis , acceptance criteria , and 
is sized or split as necessary to be 
delivered by a single ART in a Pl.
A

Feature

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

______ are short descriptions of a small piece of desired functionality , written from the perspective of the
user.

A

Story

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

An ______ supports the activities needed
to extend the Architectural Runway to provide future
business functionality and are captured
in various backlogs throughout SAFe.

A

enabler

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

True or False: Market rhythms are cyclical and predictable

A

True

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

True or False: Market events are adhoc and often unpredictable

A

True

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

True or False: During PI planning and backlog refinement Features are refined into stories.

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q
Epic, Feature or Story:
As a (user role)
I can (activity) 
So that (business value)
A

Story

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

True or False: Use personas to better understand users (for writing stories)

A

True

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

True or False: Personas are detailed fictional characters acting as a representative user

A

True

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q
I
N
V
E
S
T
in a good story
A
Independent
Negotiable
Valuable
Estimable
Small
Testable
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

True or False: Write stories that can be developed separately (Independent)

A

True

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

True or False: Write stories in which scope can be negotiated.

A

True

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

True or False: Write stories that are valuable to the customer.

A

True

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

True or False: Write stories that can be estimated (Estimable)

20
Q

True or False: Write stories that can fit in an iteration (small)

21
Q

True or False: Write stories that are testable (testable)

22
Q

3 C’s of writing good stories

A

Card - write the story on a card
Conversation
Confirmation - acceptance criteria

23
Q

Who creates the acceptance criteria of a story

A

The agile team

24
Q

True or False - Acceptance criteria should be written in the Given-When-Then format

25
What are the 4 types of enabler stories:
1) Infrastructure 2) Architecture 3) Exploration 4) Compliance
26
______ are a systematic approach to improving the system without changing observable system behavior. - Example: Improving maintainability, performance, or scalability
Refactors
27
______ are research activities to reduce risk, understand a functional need, increase estimate reliability, or define a technical approach.
Spikes
28
________ spikes - Researching a technical approach | or unknown
Technical
29
______ spikes - Researching how a user might use | or interact with the system
Functional
30
A _____ _______ is a singular number that represents: - Volume: How much is there? - Complexity: How hard is it? - Knowledge : What do we know? - Uncertainty : What's not known?
Story Point
31
3 anti-patterns of estimating 1) Pressure by ______ to lower estimations 2) Only a ______ people participate 3) Not using the adjust ______ scale
1) stakeholders 2) few 3) Fibonacci
32
Feature or Story: Title and description Acceptace Criteria Benefit Hypothesis
Feature
33
A __________ is a higher-level solution behavior that typically spans multiple ARTs. Capabilities are sized and split into multiple features to facilitate their implementation in a single PI. ar/
Capability
34
Avoid defining _______ with the ‘user story voice‘ format that’s designed to support one user role; features typically provide functionality for multiple user roles
Features
35
System Architects typically create enabler ________
Features
36
``` An ______ Hypothesis Statement contains: Funnel Entry Date Name Description Business Outcomes Leading Indicators Non Functional Requirements ```
Epic
37
The _______ Owner is responsible for working with Product and Solution Management and System Architect/Engineering to split the epic into Features or Capabilities during backlog refinement.
Epic
38
Scrum Master Role in Estimation (Best Practices): Encourage _________ to participate
everyone
39
Scrum Master Role in Estimation (Best Practices): Ensure relative _______ are used
estimates
40
Scrum Master Role in Estimation (Best Practices): Focus the discussion around the _______ items
contested
41
Scrum Master Role in Estimation (Best Practices): Identify subject matter experts who need to be ______
present
42
Scrum Master Role in Estimation (Best Practices): Keep time spent ______ stories to a minimum
Estimating
43
What is the adjusted fibonacci scale used in estimating?
1, 2, 3, 5, 8, 13, 20, 40, 100, infinity
44
Equal to the sum of the points for all completed stories that meet the Definition of Done and used to calculate the results of the team averaged over time.
Velocity
45
An estimated value of what can potentially be delivered as determined during PI planning. It is based on velocity and modified for the realities of holidays, staffing changes and absences.
Capacity
46
The teams' committed value of the # of points the team intends to deliver in a sprint or PI; based on capacity and the # of stories in the backlog
Load