Framework Rationale Flashcards

(76 cards)

1
Q

When does Framework 1 (Requirements Elicitation) apply?

A

When we’re not sure we’re solving the right problem or aiming at the right outcome.

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

Framework 1: What is the trigger question?

A

What problem are we solving and what outcome do we need?

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

Framework 1: One-line test?

A

If intent is unclear, go back to elicitation.

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

Framework 1 applies when stakeholders say what?

A

This isn’t what we needed / We’re solving the wrong thing.

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

Framework 1 applies when there is misalignment about what?

A

Goals, scope, desired outcomes, constraints, timelines.

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

Framework 1: What does it prevent?

A

Building the wrong solution for the wrong need.

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

Framework 1: What is the simplest memory phrase?

A

Right problem, right outcome.

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

Framework 1: What does ‘align’ mean?

A

Get shared agreement on the problem, goals, scope, constraints, and timelines.

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

Framework 1: What does ‘uncover’ mean?

A

Elicit the real needs, pain points, gaps, and assumptions.

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

Framework 1: What does ‘validate’ mean?

A

Confirm your understanding with stakeholders so nothing is misunderstood.

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

Framework 1: What does ‘accelerate’ mean (simple)?

A

Turn clarity into buildable requirements and next steps.

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

When does Framework 2 (Requirements Decomposition) apply?

A

When something is missing or incomplete in the requirement’s parts and pieces.

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

Framework 2: Trigger question?

A

Do we have all the elements needed to define this completely?

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

Framework 2: One-line test?

A

If a component is missing, decompose.

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

Framework 2 applies when you need to break requirements into what?

A

Processes, Tasks, Rules, Data, Validation.

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

Framework 2: What does ‘Processes’ mean?

A

End-to-end workflow: handoffs, decisions, and steps.

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

Framework 2: What does ‘Tasks’ mean?

A

Specific actions done by a person or system.

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

Framework 2: What does ‘Rules’ mean in decomposition?

A

Rule placeholders to ensure rules are captured while breaking work down.

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

Framework 2: What does ‘Data’ mean?

A

Inputs/outputs, fields, sources, formatting, and quality needs.

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

Framework 2: What does ‘Validation’ mean?

A

How we will verify correctness (AC, success checks, error handling).

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

Framework 2: What does it prevent?

A

Surprises caused by missing details.

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

When does Framework 3 (Business Rules) apply?

A

When behavior depends on conditions, constraints, eligibility, thresholds, or exceptions.

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

Framework 3: Trigger question?

A

What happens if X occurs? What if it doesn’t?

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

Framework 3: One-line test?

A

If it’s if/then, it’s a business rule.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Framework 3 applies when you need to define what?
Conditions, constraints, decisions, eligibility, exceptions.
26
Framework 3: What does it prevent?
Edge-case failures and inconsistent behavior.
27
Framework 3 applies when users ask what?
What if I’m not eligible / What if it fails / What about exceptions?
28
Framework 3: Where do rules usually hide?
In people’s heads, SOPs, compliance, timing assumptions.
29
Framework 3: Simple memory phrase?
If/Then logic.
30
Framework 3: How do rules relate to edge cases?
Rules define exceptions and how the system should respond.
31
Framework 3: How do rules relate to access/permissions?
Access and role constraints are business rules.
32
When does Framework 4 (Process Modeling) apply?
When people disagree about flow: steps, sequence, handoffs, decisions, or exceptions.
33
Framework 4: Trigger question?
Do we all see the workflow the same way?
34
Framework 4: One-line test?
If flow is unclear, visualize it.
35
Framework 4 applies when the issue is confusion about what?
Who does what, when, and what happens next.
36
Framework 4: What does it prevent?
Problems at the seams (handoffs, decisions, exceptions).
37
Framework 4: Simple memory phrase?
Visualize the flow.
38
Framework 4 applies when teams interpret sequence differently because?
They don’t share the same mental model of the workflow.
39
Framework 4 applies when ownership is unclear between?
People/roles, teams, or systems (handoffs).
40
Framework 4: What are 'seams' in your phrase?
Decisions, handoffs, and exceptions.
41
Framework 4: One practical output of process modeling?
A shared workflow diagram that exposes gaps and disagreements.
42
When does Framework 5 (User Stories & Acceptance Criteria) apply?
When success is unclear, expectations differ, or you need clear proof it met the need.
43
Framework 5: Trigger question?
How will we know this worked for the user?
44
Framework 5: One-line test?
If success is subjective, define proof.
45
Framework 5 applies when stakeholders say what?
It works but it’s not what I expected.
46
Framework 5: What does it prevent?
Shipping something that technically works but doesn’t meet expectations.
47
Framework 5: Simple memory phrase?
Clear intent + clear proof.
48
Framework 5: What makes a good user story (plain)?
A clear user outcome for a specific persona in context.
49
Framework 5: What does INVEST remind you to check?
Stories should be independent, negotiable, valuable, estimable, small, testable.
50
Framework 5: What makes strong acceptance criteria (plain)?
Objective, testable, includes edge cases, tied to outcomes.
51
Framework 5: Ready vs Done (simple)?
Ready = buildable; Done = meets acceptance criteria and agreed success.
52
When does Framework 6 (Backlog Refinement / Readiness) apply?
When work is about to enter dev and the team would have to guess.
53
Framework 6: Trigger question?
If we start today, where will engineers have to guess?
54
Framework 6: One-line test?
Ready = buildable without guessing.
55
Framework 6 applies when you see what pattern?
Ambiguity surfacing mid-sprint instead of before commitment.
56
Framework 6: What does it prevent?
Churn, rework, and sprint chaos.
57
Framework 6 applies when what shows up late?
Dependencies, unanswered questions, unclear AC.
58
Framework 6: What is it NOT?
Not discovery—it's the readiness check before commitment.
59
Framework 6: Simple memory phrase?
Last gate before build.
60
Framework 6: What does 'definition of ready' mean (plain)?
Enough clarity and dependencies resolved so dev can proceed confidently.
61
Framework 6: Who benefits directly from readiness?
Engineering (fewer blockers) and stakeholders (fewer surprises).
62
When does Framework 10 (Communication) apply?
When understanding didn’t transfer correctly, even if information was sent.
63
Framework 10: Trigger question?
Did the message land the way it needed to?
64
Framework 10: One-line test?
If people misread it, fix the communication path.
65
Framework 10 applies when you hear what?
I didn’t understand / I thought it meant something else.
66
Framework 10: Simple model?
Right info -> right people -> right format -> right time.
67
Framework 10: What does it prevent?
Surprises, misinterpretation, and rework from misalignment.
68
Framework 10: What is it NOT?
Not documentation depth; it’s delivery of understanding.
69
Framework 10: Simple memory phrase?
Transfer of understanding.
70
Framework 10: What’s a common trap?
'I already sent it' isn’t the same as shared understanding.
71
Framework 10: What’s the goal?
Demonstrated shared understanding, not just message delivery.
72
When does Framework 11 (UAT Coordination) apply?
When you need proof it works for real users in real scenarios before release.
73
Framework 11: Trigger question?
How do we know it works in real-world use?
74
Framework 11: One-line test?
If issues appear after release, UAT wasn’t sufficient.
75
Framework 11 applies when you need to validate what?
User workflows, edge cases, and business expectations in practice.
76
"Framework 11: What does it prevent