Why stacks?
🟦 The stacks provide specialists with a clear, prioritized task list for focused work without constant queries or interruptions.
This text provides background information. What types of text are there?
The stacks are the final tool in the planning chain and serve as a personal work plan for specialists. They provide a clear, individual task list for each employee and enable a smooth workflow.
Function and aim of the stacks
The stack acts as a personalized Kanban board for each specialist and structures the workflow so that the tasks defined for an employee in the pipeline appear in the specified order. This promotes the productive processing of tasks and minimizes the need for queries.
Aim of the stacks: The stacks reduce the need for queries and enable developers to concentrate on their work without disruption.
Workflow within the stacks
- Processing the tasks: The specialist starts with the top task in the "Complete" lane and works their way down step by step. The aim is to move as many tasks as possible to the "Done" lane by the end of the week.
- Dealing with problems: If a problem arises with a task that cannot be solved independently, the task is moved to the "Obtain feedback" column and assigned to the ticket creator for clarification. This interrupts the processing of the task and the specialist can move on to the next task.
- Ongoing processing: While waiting for feedback, the specialist can continue seamlessly with the next task in the "Complete" lane. As soon as feedback on the first task is received, it is processed again until it is completed.
Application example
At the beginning of the week, a developer sees all the tasks assigned to them in the "Done" column of their stack. He works through the tasks one after the other. If he encounters a problem or needs feedback, he can move the ticket to the "Obtain feedback" column and assign it to the person responsible. This interrupts the processing of the task and they can move on to the next task.
The clear structuring and prioritization of tasks in the stack helps the developer to complete their work efficiently and purposefully without constant planning interruptions.