Discovery
Work stories out before they reach a sprint.
Half-specified stories are a main cause of delivery problems: questions surface mid-sprint, designs arrive late, estimates are guesses. In FlowGazer, every story starts in discovery.
Discovery and pre-work
Add pre-work tasks to a story, such as a feasibility check for a lead engineer, UX research or designs, assign them, and attach links to designs and research.
Feasibility first
Hard technical questions are answered before the team commits to a sprint.
Designs and research attached
Prototypes, research notes and constraints live with the story, not in someone's inbox.
Ready for the backlog
Only product managers decide a story is ready and promote it to the backlog. If pre-work isn't finished yet, FlowGazer warns before promoting.
The product manager decides
Promoting to the backlog is a product decision, so only product managers (and admins) can do it.
Ranked by priority
Promoted stories land after the last backlog story of the same priority; reorder by dragging.
Back when needed
Managers can send a story back to discovery if it turns out not to be ready.
Estimate, then plan
The team sizes backlog stories in grooming. A story without an estimate can't enter a sprint.
Bring your backlog
Import Markdown files, one story per file, straight into discovery. Optional front matter sets the title, points, priority and tags; the rest becomes the story's description.
Stories can carry tags, and the specs behind them can live in product documents and diagrams.
Documents & diagrams arrow_forward