Marek Mucha
Agile Technical Project Manager |Scrum Master PSM II| FinOps Certified Practitioner |Electronic Trading
Published Mar 6, 2023
It is common to move unfinished tasks from one sprint to another. Unfortunately, it can have a negative impact on the scrum team and distract general performance. Therefore, it is better to avoid moving tasks that have not been finished to the next iteration. First of all, it should be discussed at a retro meeting, especially if it happens more frequently. The team should try to answer the question: why are we not able to complete tasks planned in the sprint?
The unfinished task can be moved back to the product backlog and then reprioritized. Maybe it is not so important. It can wait in the backlog so that a more critical task takes its place in the next sprint.
The unfinished task could be split into smaller pieces and delivered one by one in a few iterations.
To view or add a comment, sign in
More articles by this author
No more previous content
-
Managing Capital and TCO Costs in the Hybrid Cloud
Jul 17, 2024
-
Hybrid and Multi-cloud Strategies
Sep 13, 2023
-
The Impact of Artificial Intelligence on Network Management
Jun 27, 2023
-
Agile tools in Azure
May 25, 2023
-
Multicast in Financial Services: Advantages, Challenges and Its Impact on the Industry
Apr 28, 2023
-
Financial markets in the cloud.
Apr 11, 2023
-
Some of the Most Successful and Innovative Tech Startups Originated in Ukraine
Apr 4, 2023
-
New trends in low latency trading
Mar 6, 2023
No more next content
