Fearless Scrum Board for Jira

User guide

Private pilot · Public Marketplace release not yet approved. Public Marketplace approval is not complete. These instructions describe the current production UI, version 2.10.0.

Start with the shared context

Open Fearless Scrum Board from your Jira project and select Refresh. Check that the project and Sprint are the ones you intend to use.

Product Goal describes the future product state the team is pursuing. Definition of Done is the shared quality commitment for an Increment. Choose the relevant Add or Edit button, enter the text, and select Save Product Goal or Save Definition of Done. Both fields require nonblank content and accept up to 10,000 characters. Cancel discards the current edit.

The current layout places Product Goal and Product Backlog on the left, and Sprint Goal, Sprint Backlog and Definition of Done on the right. Narrow screens stack these areas. Context panels grow to fit saved text. To adjust panel height, drag Resize height, or focus that control and use Up/Down. Home returns to a content-fitting height with the minimum panel height preserved.

Product context is entered manually. Automated Product Forge import, AI integration and retrospective integration are not current features.

Plan around the Sprint Goal

The Product Backlog follows Jira rank order. Release 2.10.0 uses Add to Sprint to add an eligible item to the selected Sprint. This changes Jira Sprint membership; it does not create another Jira issue.

Edit Sprint Goal, then select Save Sprint Goal to update Jira's actual Sprint Goal. A saved field is not proof that other people have refreshed their view.

The Sprint Backlog groups selected Product Backlog Items (PBIs) with their task plans. Remove from Sprint removes Sprint membership without deleting the Jira issue. Completed work may not return to the incomplete Product Backlog. The app blocks unsupported or ambiguous membership changes, including independently moving subtasks.

PBI cards show the issue key, summary and available metadata. The current implementation does not fetch and display the Jira issue's full Description field. Open the issue in Jira when you need that detail.

Build and adapt the task plan

Choose + Add Task beneath a selected PBI, describe the work, and press Enter. Descriptions accept 1–2,000 characters. Use the task's selector to move it through To Do, Doing and Done.

These are shared app tasks associated with a PBI and Sprint. They are not Jira subtasks, and moving one does not change the parent Jira issue's status. The current interface has no task-text editing or individual task-deletion control.

An oversized stored task plan is rejected rather than silently truncated. No validated ten-person simultaneous-editing capacity is claimed.

See teammates' changes and resolve conflicts

Select Refresh to retrieve colleagues' saved changes. Updates are not pushed automatically. Wait for an operation to finish before starting another.

After a rejected Product Goal or Definition of Done save, preserve important draft text outside the editor, cancel the draft, Refresh, inspect the latest saved text, and deliberately reapply an agreed edit. Refresh can retain your draft; it does not necessarily show the teammate's winning text while the editor remains open.

Sprint Goal drafts can also remain visible across Refresh. Preserve the draft and reload for a clean view when necessary. Coordinate concurrent changes rather than assuming a safe automatic merge.

If an operation reports an uncertain result, Refresh and inspect what was saved before trying again. Drafts held in the page are not a durable backup and may be lost when the browser is closed or the page reloaded.

Keep the Product Backlog deliberate

The app's Product Backlog capacity policy is 15 PBIs, not a target. Existing Jira work is not silently hidden to enforce that number. Returning an item to an already-full backlog can open Trim the Tail.

The count and Trim the Tail controls appear after the Product Backlog list. Tail candidates come from its lower half, presented lowest-ranked first. Reorder work in Jira first when needed, then Refresh before choosing items.

Warning: Trim the Tail permanently deletes selected underlying Jira issues. It is not an archive or removal from the Sprint. Check each key, summary and rank at Review deletion. Cancel unless deletion is intended and authorized. The app cannot undo it. A waiting return from a Sprint may proceed only after deletion and a successful capacity recheck.

Export or erase app data — administrators only

The App data export and erasure · project administrators section requires Browse Projects and Administer Projects permissions. Choose Product Context or Sprint task history. Task history requires the numeric Jira Sprint ID.

Select Review app data, then Download export page. Use Next export page until you have all pages through the displayed revision boundary. Later edits require a fresh review; one page is not necessarily the whole history.

Warning: Erase app data permanently seals the selected scope against future writes. It is not a reset. Review the scope and type the displayed confirmation only for an authorized erasure. Historical app text and retry receipts are scrubbed in batches, while minimal revision markers remain. Follow the continuation message when more batches are needed. Refresh does not reopen a sealed scope.

App-data erasure does not delete Jira-owned issues or Sprint Goals, does not erase an entire Jira project, and does not erase the separate retrospective app. Keep it distinct from Trim the Tail's permanent Jira-issue deletion.

Hosted destructive erasure was not part of the recorded two-account pilot verification. Do not experiment with these controls on valuable data.

Read our privacy page. For product help, email jimi@fearlessagility.com.