How many story points is a day of work?
There is no fixed conversion, and that is the point. A point measures relative size, not time. Teams that force a points-to-hours rate end up with hour estimates under a different name.
What scale should I use for story points?
A Fibonacci-style sequence is the most common because the gaps grow as items get larger. Any scale works if the team uses it consistently and splits items that are too large to finish in one sprint.
Can non-developers understand story points?
Yes. Treat them as a size rating, like small, medium and large with numbers on top. You do not need to know how the code works to see that a large rating means more work or more unknowns.
What is velocity?
Velocity is the number of points a team completes in a sprint. Averaged over several sprints, it helps forecast how long the remaining backlog will take. It is a planning aid, not a performance score.
Are story points the same as function points?
No. Function points are a formal method that counts inputs, outputs and data in a specified way. Story points are a team's own relative scale, agreed through discussion.
Why would a vendor price by story points instead of hours?
Pricing by deliverable complexity ties what you pay to what you receive, and it removes the reason to pad time. You agree scope and budget up front, and changes show as additions to the baseline.
Is a story point equal to an hour?
No. A point is a relative measure of size and complexity, not time. Converting points to hours defeats the purpose and brings back the false precision they were meant to avoid.
Who should estimate story points?
The people who will do the work: developers, testers and designers on the team. Estimates handed down by managers or sales tend to be optimistic and are not owned by the people building.
Can you use story points on a fixed-price project?
Yes. Points measure the complexity of the scope, and that scope can be priced. StackLift prices by deliverable complexity in story points, with scope, budget and delivery path agreed before engineering begins.