1 / 11

Cultivating Agile Requirements

Cultivating Agile Requirements. Mark Wavle, CBAP, PSM. The Agile Manifesto. The Mission Statement. We Value:. over. Individuals and Interactions. Process and Tools. C omprehensive D ocumentation. Working Software. C ontract N egotiation. Customer Collaboration. Responding to Change.

dalmar
Download Presentation

Cultivating Agile Requirements

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Cultivating Agile Requirements Mark Wavle, CBAP, PSM

  2. The Agile Manifesto The Mission Statement We Value: over Individuals and Interactions Process and Tools Comprehensive Documentation Working Software Contract Negotiation Customer Collaboration Responding to Change Following a Plan That is, while there is value in the items on the right, we value the items on the left more.

  3. Scrum Framework

  4. Product Backlog • List of all remaining desired features for the product • Ordered / stack ranked (1 to n…) • Each feature expressed as a Product Backlog Item • Visible to all stakeholders • Product Backlog changes constantly throughout development of the product

  5. Definition of Ready • A ready item is: • Clear • Feasible • Testable

  6. Questions for Backlog Items • What is the idea? • How does the user benefit? • How important is it? • What high-level items can we do in the next 6-12 months? • How big is it? • What specific items can we do in the next 1-3 Sprints? • How are we going to implement it? • How will we know it is done?

  7. Discuss with stakeholder Analyze and decompose Identify Acceptance Criteria Identify test data Document idea Estimate (t-shirt sizes) Estimate (story points) Complete UX/UI design Identify user benefit Identify dependencies Work dependencies Legal, compliance, security reviews Prioritize Identify place in 6-12 month plan Identify place in next 1-3 Sprints Plan for team delivery Free-form User Story Acceptance Criteria Supplementary artifacts, wireframes

  8. Techniques to Mature Backlog Items • Backlog Grooming Sessions • Ensures whole team understands backlog items as they are matured • Estimating/Sizing • Drives whole-team understanding of each item as it is sized • Splitting Backlog Items • Splits items so they deliver value and fit within one Sprint • Modeling Visually • Encourages conversation and collaboration while ensuring the whole team understands the item

  9. Thank You Mark Wavle Email: mwavle@cardinalsolutions.com Twitter: @wavle

More Related