DevStride supports two kinds of estimate, configured on two Settings pages and both assigned per item type:
You can use either, both or neither; each item type decides.
Configure Settings → Data Model → Effort Point Estimation (needs Manage work types). The page lists every item type with an Effort Points setting:
| Option | What people can enter |
|---|---|
| Decimal | Any number, including fractions (2.5). |
| Integer | Whole numbers only. |
| Fixed List | Only the values you list, comma-separated, for example 1, 2, 3, 5, 8, 13 for Fibonacci or 1, 2, 4, 8 for powers of two. |
| Disabled | The type is not pointed; the Point Estimate field does not appear on its items. |
Changes save as you make them. Point a type that represents the unit of planning (Stories, Tasks); leave container types (Epics, Features) disabled and let their totals roll up.
People set an item's points from the Point Estimate field in the item drawer sidebar, the Points cell of a table, or the bulk-edit menu. See Point estimates.
Configure Settings → Data Model → Time Estimation (needs Manage work types). Here you define named estimation ranges — T-shirt sizes, typically — so people pick a size and get sensible hours they can then refine.
Click New and enter a Range Name plus its Default Hours: Optimistic, Likely and Pessimistic. A new organization starts with XXXS (0.25 / 0.5 / 1 hrs) through XXXL. People can refine the three numbers on an individual item; the range just gives them a starting point.
Click New to create an Estimation Collection, choose its Confidence Percentage (68, 95 or 99, that is one, two or three standard deviations), and drag ranges into it. The confidence level decides how wide the ± margin on the computed estimate is. The starter collection is Story Sizes.
For each item type choose a collection, or Time Estimates Disabled to hide time estimates on that type.
If your teams only ever estimate the likely hours, turn on Optimistic and pessimistic are optional at the top of the Time Estimation page. Changing it needs permission to manage the organization's settings, and it applies to the whole organization.
With it on, the estimate dialog marks Optimistic and Pessimistic (optional). Type only Likely and save: the blank bounds take the likely value, so the estimate is exactly the likely figure with no ± range. If you do type a bound, it is kept and still checked (optimistic can't exceed likely, likely can't exceed pessimistic). Reopening a likely-only estimate shows its bounds blank again, so changing Likely carries them along.
It's off by default. Turned off, every estimate needs all three values, as before.
In the item drawer, click Time Estimate, pick a range or type the optimistic, likely and pessimistic hours (only likely when optimistic and pessimistic are optional), and review the Range, Estimate and Confidence before Save Estimate. The estimate is the PERT weighted mean, (optimistic + 4 × likely + pessimistic) ÷ 6, shown with a ± margin at the collection's confidence level. Time estimates also appear in the Time Estimate cell of tables and in the bulk-edit menu. See Time estimates and best practices.
Priority Levels
Define your organization's priority scale, group levels into collections with a default, and choose which scale each item type uses.
Item Statuses
Define the statuses work moves through, group them into collections for boards, restrict a status to certain item types, and set WIP limits that warn when a column holds too much.