What is a scrum workflow in Strkr?
A scrum workflow in Strkr is a project in the Projects module built on the scrum shape: a prioritized backlog, time-boxed sprints, a kanban-style sprint board, points-based estimates, a burndown chart, sprint review, and retrospectives. The engineering lead creates the project, picks the scrum type, and the project surface renders backlog, sprint, board, and retro tabs. The scrum workflow sits beside the CRM record, so engineering work and the account it serves share one platform.
How is Strkr Projects different from Jira or Linear?
Jira and Linear are standalone engineering scrum tools. Strkr Projects is the project surface of a CRM-plus-Projects platform. The feature depth on pure scrum motions is comparable for most teams - backlog, sprints, board, burndown, retro, capacity. The difference is context: in Strkr the project links to an account, the customer success manager sees the sprint, the account executive sees the roadmap. Teams running a connected customer-and-engineering motion benefit from the shared platform. Teams running engineering-only may still prefer a specialized tool.
Does Strkr support Kanban as well as Scrum?
Yes. A project in Strkr can be scrum-shaped (sprints, burndown, retro), kanban-shaped (continuous flow, WIP limits), or hybrid. The project type is set on creation and dictates the available views. Teams running a mix - scrum for feature work and kanban for ops - create two project types in parallel. The underlying issue model is shared, so an issue can move between projects without a format change.
How does the account link work?
A project can link to a CRM account. On the account record, the Projects tab lists linked projects with status, sprint burndown summary, and open issue count. On the project, the Account block links back to the account record. The engineering lead sees the account notes and renewal date. The customer success manager sees engineering progress. The two roles share context without a sync.
What does the retro template look like?
The retro template is a four-section surface: Keep (what worked), Start (what to try), Stop (what to drop), and Action (committed changes). Each section accepts bullet entries from the team. Action items can be converted to issues on the next sprint with one click. The retro saves per-sprint and the project maintains a retro history, so the team can read what they learned three sprints ago and whether the actions landed.
Is the scrum workflow included in the Projects module?
Yes. The scrum project type, backlog, sprint planning, sprint board, burndown chart, sprint review, retrospective template, capacity planning, and the account link are included in the $79 per month flat-fee Projects module. There is no separate scrum SKU and no per-user charge on top. The Projects module is a flat add-on to the CRM seat price, which keeps budgeting simple for engineering teams.
