01 / 04
PI planning wall.
Squads, iterations and work items on one screen, with live dependency lines between cards and a “today” marker. One action generates every squad’s sprints on identical dates.
Explore the productSAFe-native work management · Self-hosted
Portfolios, ARTs, Squads, Program Increments, risks and dependencies, built into the product. Boards, wiki, chat, meetings and documents behind one login, on your own infrastructure.
The problem
| Need | What teams use today | What goes wrong |
|---|---|---|
| Backlogs and boards | A generic issue tracker | “Epic” and “Feature” are only labels; the tool does not know what an ART is |
| PI Planning | Spreadsheets and sticky notes | The Program Board goes stale on day two |
| Risks (ROAM) | A slide | Risks are disconnected from the work they threaten |
| Documentation | A separate wiki | Pages cannot see the work they describe |
| Conversation | A separate chat tool | Decisions are buried in threads |
| Meetings | A separate video tool | Ceremonies leave no trace on the increment |
| Source code | A separate Git host | Another set of accounts to administer |
Most tools make you simulate SAFe. WS Crafter models it.
Why WS Crafter
Chat, meetings, wiki, whiteboard, documents and storage live inside the product, not as links to other services.
A wiki page knows its ART. A chat topic can be a work item. A meeting can belong to a PI ceremony.
One sign-in, one access model, one audit trail. Add a person to a space and they get what they need in every app.
The ecosystem
Backlog, Board, Scrum, Calendar, Gantt, Program Board and PI Timeline
Create spaces; each one configures its own project
See Portfolio → Solution → ART → Squad as one hierarchy
Plan and run Program Increments, sprints, risks and dependencies
Draw statuses, transitions and the rules work must pass to move
Design the create, view and edit page for every work item type
Documentation that knows its place in SAFe
A live shared canvas that knows your work items
Team chat where every conversation is bound to the work
Video meetings attached to work items and PI ceremonies
Documents, spreadsheets, presentations, PDF and Markdown in the browser
Personal and shared file storage with admin quotas
Users, access profiles, security policy, SSO and audit
Repositories, pull requests, packages and CI
The SAFe model
A Portfolio space says “Add Epic”. An ART says “Add Feature”. Stages, boards, colours and wording follow the level you choose, and every one of them stays editable.
See the SAFe modelSpotlight
01 / 04
Squads, iterations and work items on one screen, with live dependency lines between cards and a “today” marker. One action generates every squad’s sprints on identical dates.
Explore the product02 / 04
Every risk Resolved, Owned, Accepted or Mitigated, with an owner, a squad and a linked work item. A dependency health view flags blockers scheduled later than the work waiting on them.
Explore the product03 / 04
Draw statuses and transitions on a canvas. Each transition carries conditions (who may move it), validators (whether the move is legal) and post functions (what happens next). The server enforces every rule.
Explore the product04 / 04
Channels and topics, where a topic can be bound to a work item. Mark a message as a decision and it appears on the work item. A standup digest is generated from what actually moved.
Explore the productCraft it your way
That is the “Crafter” in the name: shape spaces, types, workflows and pages to fit how your organisation actually works.
Add your own work item types and spaces that sit outside the hierarchy, nest under a SAFe space, or act as a level.
Assign a workflow to each work item type, with a workspace default.
Decide which fields appear when an item is created, viewed and edited, and which are required.
Platform
Comparison
| Generic tool stack | WS Crafter | |
|---|---|---|
| SAFe levels and artifacts | Simulated with labels | Built into the model |
| PI Planning and Program Board | Spreadsheets and whiteboards | Native, live, linked to the work |
| ROAM risks | Slides | A board, owned and linked to work items |
| Wiki, chat, meetings, whiteboard, documents | Separate products | Native apps that know the work |
| Source code Next | A separate Git host | Native Git service, same accounts |
| Accounts and permissions | Administered in every tool | One login, one model |
| Hosting | Vendor cloud | Your infrastructure |