Sprints

A Sprint is a time-boxed Project planning and delivery cycle. Sprints move through future, active, and done states and show progress across their committed Work Items.

Plan a Sprint

1. Create a future Sprint with a name and dates.
2. Add Work Items from the Project Backlog or Work Items view.
3. Reorder the Sprint list to make priority clear.
4. Start the Sprint when the team is ready to commit.

Items are appended when assigned. Returning an item to the Backlog clears its Sprint order.

Sprint order is its own order

Sprint ordering is separate from Board status ordering. A Board move can change a Work Item’s status without changing its priority in a Sprint, and Sprint reordering does not move a card between Board columns.

Reordering is conflict-safe: if another teammate changes the Sprint before your update is saved, Hamstik asks you to reload rather than silently overwriting their order.

Complete a Sprint

Completing a Sprint requires its Work Items to satisfy the current completion rules. If work remains, review the completion target and move unfinished items deliberately before trying again.

See Boards for status-based flow and Work Items for item fields and activity.