Inspect before downloading
See what is inside
These previews come from the published bundle files, so you can judge the method and writing before using it.
Example task
A team says, “Add a faster export so customers stop complaining.” Draft one product backlog item for review. No customer records, product metrics, current Product Goal, export format, performance target, owner, date, or tracker configuration are supplied.
Without the bundle
As a customer, I want exports to be faster so that I can work efficiently. Acceptance criteria: - Exports complete in under 10 seconds. - The feature ships this sprint. - Product Manager owns the story. Priority: High because customers are complaining.
Using the bundle
Draft a discovery-ready backlog item for improving export completion time, pending evidence and team confirmation. Do not commit to a target, owner, date, or order yet. Evidence Status - Verified: None. - Provided: A stakeholder reports that the team should consider faster exports; the report is not supported by records in this task. - Assumed: The requested work concerns an existing export capability; this is a working assumption only. - Needs verification: affected segment, export types and payload sizes, current completion-time distribution, error rate, user impact, Product Goal, definition of acceptable performance, constraints, dependencies, owner, estimate, and current backlog order.
Why this is better: The bundle-assisted output is stronger because it answers the task while refusing to invent a performance target, owner, date, customer evidence, Product Goal, or sprint commitment. It keeps the item useful by proposing an evidence-gathering slice and states what would change the ordering decision.
Inspect this example in the repositoryDeliverable guide
Product Backlog / User Stories
A source-backed, reviewable product backlog item or user story with acceptance evidence and ordering rationale.
Read the fileWorkflow
Draft and Refine a Backlog Item
Turns supplied product evidence into a small, testable, review-ready backlog item.
Read the fileWorkflow
Order and Review a Product Backlog
Makes backlog order and readiness transparent without treating a score as objective truth.
Read the fileQuality rubric
Backlog Item Quality Check
Reviews whether a backlog item is grounded, outcome-focused, testable, ordered transparently, and safe to act on.
Read the fileIs this bundle right for your task?
Who it is for
- People drafting, reviewing, approving, or relying on Product Backlog / User Stories
- Teams working in software, saas, digital products
When to use it
- A Product Backlog / User Stories draft needs a clear purpose, audience, evidence base, structure, and approval path.
- An existing draft needs unsupported claims, missing sections, unresolved decisions, and reviewer comments addressed.
What you need to provide
- The document purpose, audience, source evidence, required sections, constraints, approvers, and intended decision or action.
- Existing drafts, templates, policies, examples, terminology, and review criteria that the output must follow.
Tasks and expected outputs
Questions it helps answer
- turn product evidence into reviewable backlog items
- make backlog order and rationale transparent
- separate Scrum requirements from optional user-story and scoring practices
What it helps produce
- product backlog item
- user story
- backlog review
Practical example
Use it with an agent
Load the bundle as context, provide the evidence named above, then adapt this example to your situation.
Provide the document purpose, audience, source evidence, required sections, constraints, approvers, and intended decision or action. Ask the agent to draft or review Product Backlog / User Stories and return product backlog item with material claims tied to evidence and assumptions, open questions, reviewers, and approval gates marked. Begin with Scrum Guide 2020, then confirm that the reference is current and applicable. Inspect Product Backlog / User Stories before drafting.
Context path: bundles/deliverables/product-backlog-user-stories
What the bundle includes
Frameworks
- Product Goal alignment
- evidence and value-risk-dependency ordering
Evaluations
- backlog item quality check
Sources used to build this bundle
These are the public references behind the role definition and operating guidance. The bundle does not replace current documentation or evidence from your site.
Limitations and safe use
Do not use this for
- Publishing, approving, or acting on a draft before its material claims, source evidence, owners, and approval gates have been reviewed.
Known limitations
- This bundle does not replace customer research or product ownership.
- Local product facts, metrics, dates, owners, estimates, dependencies, and tool fields must be provided or verified.
- User-story syntax and prioritization scores are optional practices rather than universal Scrum requirements.
Safety notes
- Keep customer and product strategy data private.
- Require explicit confirmation before live tracker, roadmap, release, or external communication changes.
- Route regulated, accessibility, privacy, security, safety, or legal requirements to current authoritative review.