Re:Chrome was delivered without any sprints at all (2021)
by Cthulhu_ on Wednesday August 16, 2023 @03:34AM
(#37143868)
That sounds like a lack of discipline and retrospection. This is also the problem I have with scrum; people don't stick to the process, and cite how the agile manifesto says that the process isn't important.
But this is a misconception. Stick to the process (religiously) at first, then assess how it works.
In this case: you did not meet your sprint goals, which either meant you overcommitted (meaning the next sprint you pick up less work), the tasks did not meet the definition of ready (that is, they could not be finished in a single sprint), or you had impediments that weren't solved on time. All of those need to be spoken out loud during a retrospective session, and action undertaken.
Not having any artifacts isn't the issue, you still need to set a moment to stop your work, review what has been done, consider what went well and what could be better, learn and improve.
If the learning is that scrum doesn't work for you - and you can show that you did it properly - then there's other processes that might work better for you, as suggested.
But this is a misconception. Stick to the process (religiously) at first, then assess how it works.
In this case: you did not meet your sprint goals, which either meant you overcommitted (meaning the next sprint you pick up less work), the tasks did not meet the definition of ready (that is, they could not be finished in a single sprint), or you had impediments that weren't solved on time. All of those need to be spoken out loud during a retrospective session, and action undertaken.
Not having any artifacts isn't the issue, you still need to set a moment to stop your work, review what has been done, consider what went well and what could be better, learn and improve.
If the learning is that scrum doesn't work for you - and you can show that you did it properly - then there's other processes that might work better for you, as suggested.