Results for “story-points”

Reads BA and TechLead artifacts to produce a sprint plan, task breakdown, and story point estimates, creating one tracked todo per sprint task for live pipeline tracking.

Breaks applications or features into thin vertical user-story slices with clear acceptance criteria and user-observable value, suitable for backlog planning and feature decomposition.

Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria, focusing on user situations and outcomes for JTBD-style backlog items.

Create job stories using the 'When [situation], I want to [motivation], so I can [outcome]' format with detailed acceptance criteria. Use when writing job stories, creating JTBD-style backlog items, or expressing user situations and motivations.

Create a six-frame storyboard that shows a user's journey from problem to solution, using a classic narrative arc to build empathy and align stakeholders.

Create user stories using Mike Cohn format with Gherkin acceptance criteria, translating user needs into development-ready work with clear outcomes and testable conditions.

Decompose large user stories into thin, independently deliverable vertical slices using the SPIDR method (Spike, Path, Interface, Data, Rules).

Build and maintain one coherent company story across all audiences — employees, investors, customers, candidates, and partners. Detects narrative contradictions and ensures the same truth is framed for each audience's needs.

Break large user stories or epics into smaller, independently deliverable stories using systematic splitting patterns.

Write a roadmap narrative that connects customer problems, company goals, bets, and sequencing.

Generate user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria, with descriptions, design links, and acceptance criteria.

Create user stories following the 3 C's (Card, Conversation, Confirmation) and INVEST criteria with descriptions, design links, and acceptance criteria. Use when writing user stories, breaking down features into backlog items, or defining acceptance criteria.

Plans a sprint with capacity estimation, story selection, dependency mapping, and risk identification. Use when preparing for sprint planning, estimating team capacity, or balancing scope against velocity. Triggers on: sprint planning, sprint plan, capacity planning, sprint scope, story points, sprint goal, backlog grooming, sprint prep, what do we build this sprint.