Guides
Guides: how to plan, scope and estimate software features
SprintProof’s guides cover the planning work that happens before a sprint: how to write a PRD engineers can estimate, how to break a feature down, a feature planning checklist of 12 areas, software estimation methods from planning poker to PERT and 50/80/90% dates, and how to handle scope creep and sprint scope changes. Each guide opens with a short answer and links to free templates and tools.
Email invitations checklist
“Invite a teammate by email” sounds like a form and an email. The parts that make it slip are the ones nobody lists in planning. Here are the ten questions to answer first, and an example plan that shows what the answers cost.
Feature planning checklist
Twelve areas and the questions that most often turn up mid-build when nobody asked them in planning. Run it against your plan, turn each answer into a requirement or an open question with an owner.
How to break down a feature
A six-step method for turning a feature or epic into parts, user stories and tasks your team can estimate and pick up, with a worked example.
How to write a PRD
Eight steps from a feature idea to a product requirements document your team can break down, estimate as a range and sign off, with a worked example.
Software estimation methods
Planning poker, story points, t-shirt sizes, three-point and PERT estimates, and simulated 50/80/90% dates. What each one answers, where it goes wrong, and how to combine them.
Scope creep and sprint scope changes
What causes scope creep, how to tell it from discovered scope, and what to do when scope changes mid-sprint.
Team
Plan the next feature before the sprint starts.
Create your account and name your workspace. Your first feature plan is free. To keep planning, subscribe to Team: the 14-day money-back guarantee applies.
Want to hear when the ChatGPT and Codex plugin ships? Leave your email.