Kanban and sprints: see work progress
The board shows what is waiting, what is in progress and what is done. When there is a specific outcome to work towards by a chosen date, the Space owner can start a sprint.
The owner can enable or disable Kanban in Space features. This setting applies to all members. Disabling hides the board while preserving tasks and sprints; the Sprints switch remains independent.
One board per Space
Open “Kanban” and choose a Space. Tasks appear in three columns: “Open”, “In progress” and “Done”. This is a Kanban view: cards show each task’s stage. The board does not enforce work-in-progress limits, so agree on a manageable amount of work separately.
A blocked task stays in its column, with a marker and the reason it is blocked. You can see both the obstacle and where it arose. Remove the block in the task card when it is resolved.
Use the selector above the board:
- All tasks — tasks in the Space that are not archived, including completed tasks.
- Without sprint — tasks outside any draft or active sprint.
- A sprint’s name — its tasks, or its saved review if it has closed.
Search, date filters and “All / Mine” still apply. Check these filters if a card seems to be missing.
Assignee rows and moving cards
By assignee, at the right of the header, adds member rows beneath the shared status columns. Select it again to hide the rows. Unlike Assignments, this view shows both responsibility and work status for one Space or sprint.
Members start in alphabetical order. Use the arrows beside a name to change their order for yourself; Unassigned stays first. On desktop, the arrows appear when you hover or focus the heading.
Dragging highlights available destinations and dims unavailable ones. If you have reassignment permission, you can move your active task to another member’s Open cell. The board does not imply that the other person has already started it. You cannot stop someone else’s active work this way. Completed and blocked cards need the relevant status change in the card first.
On a phone, change the assignee and status in the card; use transfer buttons to move between backlog and sprint.
From a draft to history in Plynno
- Open “Kanban”. Sprints can be enabled in Space settings; the board is available without them. Choose a Space; a sprint needs a Space.
- The Space owner selects “New sprint”. Enter a name and goal in the draft, and set the period through “Sprint dates and settings”.
- Use “To sprint” on cards in “Space backlog”, or drag them across. Starting requires a goal and at least one task. Return completed cards to the backlog first.
- The Space owner selects “Start sprint” and confirms. Today must fall within its dates; close any other active sprint in the same Space first. The initial goal and scope are recorded.
- Work with the cards on the board. “Backlog” reveals available tasks; the card tooltip and sprint summary record work added after the start. Being able to add work does not mean the plan has room for it.
- The Space owner selects “Finish” → “Continue to summary”. Decide whether each unfinished task goes to the backlog or a next draft. You can create that draft here. Deletion requires permission and is a separate, permanent decision.
- Add an optional “Retrospective note”, select “Finish” and confirm closure. Find the closed sprint in “Kanban view”, marked “closed”. A note preserves a conclusion; it does not replace a conversation.
Working with Kanban
Starting everything is easy. Finishing everything at once is another story. Agree on how much work you can actually keep going, and try finishing or unblocking something before picking up another task.
Say you're preparing a poster and a workshop booking form. The form is waiting for email access. Before starting a mailing campaign too, ask for access or finish the poster. Fewer cards end up sitting in In Progress just waiting.
You may see this called work in progress, or WIP. Plynno doesn't impose an automatic limit; it's your agreement. Start with a manageable amount and reconsider after a few days.
For a deeper look, see The Kanban Guide and Kanban University's guide.
When to add a sprint
You can use the board without sprints. A sprint helps when you have a shared goal, a limited period and a manageable set of tasks. For example: get workshop bookings ready by Friday.
The Space owner enables sprints in Space settings, prepares them, starts them and closes them. A Space can have one active sprint, with future sprints prepared as drafts. Members work on tasks according to their permissions. Turning sprints off keeps the board and its history.
Scrum and personal sprints
You don't have to learn Scrum to make a short shared plan. You can simply agree to open workshop bookings by Friday, choose the tasks you need, and look at the result afterwards.
Scrum is a separate framework with defined roles, events and requirements for finished work. Its sprints last no more than a month. If your team follows Scrum, use the official guide. Creating a sprint in Plynno doesn't mean you've adopted the whole framework.
When a sprint helps
Try short cycles when a team can deliver a useful piece of work and adjust after feedback, such as testing a service or improving a product. If urgent requests dominate the day, first find out how much time remains for planned work. A sprint calendar will not remove interruptions.
Build a realistic plan
- State one outcome: “A trial customer can submit a booking and receive a response.”
- Agree what ready means: the full journey works, the message is clear and the responsible person receives the details.
- Count time available after meetings, support duties and absences. Working hours are not all task hours.
- Select only work that serves the goal from the backlog. Check dependencies and compare the scope with what you have actually finished before.
- Leave room for uncertainty. If the plan needs a perfect week, reduce it before starting.
During the sprint and at the end
Check daily what moves the outcome forward and where help is needed. Give a blocker a concrete next action: obtain access, clarify a decision or reduce a piece of work. Compare new requests with the goal and available time before taking them on.
At the review, demonstrate the real customer journey and ask whether it solves the intended problem. In the retrospective, discuss how you worked together. For example: “Email access delayed testing; next time we will check access during preparation.” Pick one improvement you can actually try.
Common mistakes
- Using a card list as the goal. Describe a change for whoever will use the result.
- Treating the calendar as available capacity. Allow for support, absences and uncertainty.
- Rolling everything over automatically. Reconsider relevance and remaining effort first.
- Turning a retrospective into blame. Discuss conditions and specific changes to the process.
Source
- Official Scrum Guide, November 2020 edition, checked on 13 October 2026. The examples and Plynno instructions are original.