Since we finished the Planning deviations in our last article, we would like to open another interesting and often-discussed topic: User Stories that have set deadlines.
In upcoming articles, we will provide our thoughts on User Stories that have deadlines. Of course, in Scrum, User Stories should not have pre-determined deadlines. However, in the real world, sooner or later they will, and you will have to think about how to deal with them. So, how would you work with them? Would you take them into a Sprint right away and give them your full attention? What about planned User Stories? What would happen to them as a result? What would be the impact on the Backlog, the Sprint and the team? You might say to yourself, “if it happens only once, it's an exception; nothing major will happen”. Once, maybe not. But what if it happens a second time? And a third time? That would be a problem, wouldn't it?
Along with deadlines, we would also like to make delivery times of User Stories a bit clearer. Why is it that when you submit a request to the Product Owner, they tell you it won't be ready for a month? Why can’t they deliver it in a week? Often, our Stakeholders simply don't know how we work within the ScrumOne framework. Maybe they don't know why we can't just take all the work coming in from all sides and put it immediately into a running Sprint. And so, it's up to the Scrum Master and Product Owner to explain that this creates chaos in our working environment, a mess in the Backlog and the team to become frustrated over time. Without an explanation, collaboration will be difficult because each side will have different expectations.
As you can see, there is a lot to consider and clarify. We hope to shed some light on this issue with the articles we are publishing in the next few weeks.
Thank you for reading and see you soon!