Chapter 7 - Techniques Flashcards
What is ‘backlog refinement’?
Ongoing feedback and revision of requirements.
Backlog: list of features/requirements
Requirement meeting: team reviews requirements
Definition of ready: criteria that means ready for the next iteration
What is ‘behavior driven development’?
Focus on intended customer behavior by using real examples.
Gherkin syntax: Given <a> when then .</a>
What is ‘impact mapping’?
Breaks down and aligns stakeholders organization goals; shows big picture while identifying details.
Goals: identifies organizational goal
Actor: stakeholders who contribute to goals
Impact: actions which actors can take to reach goals
Deliverable: those that help the actors
What is ‘job stories’?
Represent product backlog item/requirement in terms of a job done by a stakeholder.
Job story format: When I want to so I can .
Situation: provides context for when job needs to be completed
Motivation: focuses on customer motivation
Expected outcomes: should solve the situation/outcome
What is ‘kano analysis’?
Kano analysis questions grid: answers are mapped to functional/dysfunctional grid
Threshold: basic, expected features
Performance features: the more the better
Excitement: customer doesn’t know what they want until they see
Indifferent: things customer don’t want
What is ‘minimal viable product’?
Identifies smallest set of features/requirements to deliver value to stakeholders.
3 steps:
- Determine problem
- Identify minimum set of features to test hypothesis
- Analyze validated learning from customers
What is ‘personas’?
Understand and empathize with intended stakeholder to align solution with need.
- Personal name and image
- Traits/characteristics
- Motivations
- Needs
- Differentiators
What is ‘Planning Workshop’?
Backlog refinement occurs within planning workshops. Can be used at any horizon depending on goal and level of detail.
- Estimated and ordered backlog
- Team velocity
- Iteration goal or feature set
- Backlog item selection
- Task planning
What is ‘Portfolio Kanban’?
A system to manage flow of work during the entire delivery cycle.
- Kanban board - columns represent steps identified in the organization to move an initiative from idea to completion
- Done criteria per column
- Limits per column
- Strategic business initiatives or portfolio items
- Refinement meeting
- Metrics
- Visual
What is ‘Product Roadmap’?
Strategic plan used to describe how a product is likely to grow, to align to stakeholders’ needs, and to acquire a budget for delivery
- Defined vision and strategy
- Defined desired outcomes
- Product management team
- Themes: collection of requirement/features/stories
- High-level requirements
What is ‘Purpose Alignment Model’?
Rates features, processes, products or capabilities in two dimensions:
- market differentiation
- critical for continued functioning of organization
- Differentiating quadrant, parity quadrant, partner quadrant, who cares?
What is ‘real options’?
Provides conditions when a commitment should be made; delays decisions to the last minute
- Options
- Commitments
- Options expiry
- Right/Wrong/Uncertain
What is ‘Relative Estimation’?
Ability to accurately estimate improves over time as new information is discovered about both capacity and capabilities.
(planning poker, silent sizing)
- Order of magnitude
- Given set of resources
- Team based estimation`
What is ‘Retrospectives’?
Reflection on most recent deliveries and then identify ways to adapt. Held at end of each iteration.
- Review previous action items
- Preparation
- Safety check
- Identify the items
- Choosing future actions
What is ‘Reviews’?
Showcase a completed working solution in order to solicit feedback.
- Solution being delivered
- Stakeholders
What is ‘Spikes’?
Spikes are time-boxed activities that have clear objectives and desired outcomes.
Used when backlog item/initiative cannot be estimated.
- Spike goal
- Type of spike (functional, technical, exploratory)
What is ‘Storyboarding’?
Technique for understanding how people will use the solution
- Scenarios
- Illustrations of the solution
- Textual explanation
- Create storyboard
What is ‘Story decomposition’?
Provides a structure for defining elements in smaller levels of granularity (minimal marketable features).
Breadth-Before-Depth.
- Solution goals
- MMF/Component
- Story (user story, job story, use case, requirement)
- Acceptance criteria
What is ‘Story elaboration’?
Lowest level of story decomposition. Occurs in the delivery horizon.
During each iteration, the story is expanded on to understand the detail.
- Elicitation
- Story decomposition
- Acceptance criteria
- Additional optional elements (task definitions, examples, mockups, input/output data tables)
What is ‘Story Mapping’?
Provides visual/physical view of sequence of activities to be supported by a solution.
- Themes/activities
- Stories/features
- Ranked priority order
- Facilitation
What is ‘User Stories’?
Representation of customer need, expressed as a short, concise statement of a feature needed to deliver value. (INVEST criteria)
- Card
- Format (As a , I need to so that
- Conversation
- Confirmation
- User story management
What is ‘Value Modelling’?
Models value creation for stakeholders who use the solution. Customer value = benefits - cost. Used at all horizons.
- Customer
- Desired outcome/objective
- Examples: Value proposition canvas, glow chart of customer value, means value chart, value model
What are the steps for creating a value model?
- Identifying all the stakeholders
- Identifying the needs of each stakeholder group
- Identifying how to satisfy the need
What is ‘Value Stream Mapping’?
Represents flow of material and information required to bring solution to customer. (Current/Future state value stream mapping)
- Prepare
- Create current state
- Analyze current state (root cause analysis)
- Create future state
- Implement process improvement
