Delusions of a SCRUM Developer

Delusion? Developers?!! It could be possible if SCRUM is not completely understood which turns into “SCRUM-does’nt-speedup-product-delivery” myth worldwide and Developers are puzzled as they Happily adopted SCRUM, but failed to deliver the results.

image from: https://www.benday.com/2017/02/24/top-3-scrum-people-skills-myths/

First of all, there is a need for a clear understanding of the Role of a Developer in SCRUM. What they are allowed to do and what’s consider a SCRUM sin if adopted by the developer.

Diving deep into SCRUM guide for the Developer Role which states:

“The Development Team consists of professionals who do the work of delivering a potentially releasable Increment of “Done” product at the end of each Sprint.”

Thus, the Development Team must Deliver something releasable at the end of each Sprint. There is no point in doing SCRUM if the increment cannot be released.

To achieve that, unfollow the following delusions while working:

• Need to only focus on my own tasks in the Sprint
• The most important thing is that I’m am productive
• Working together means we will be less productive = waste
• If I can’t complete my work because I’m depending on others it’s not my problem.
• Having to work with end-users distracts me from doing my job
• If we finish all work that was identified during Sprint Planning it equals a successful Sprint
• The Product Owner should describe all requirements in detail so that there can be no surprises during the Sprint
• If we have people issues in the Development Team the Scrum Masters will take care of it
• As a matter of fact, we can shove all the issues that distract us from doing our work to the Scrum Master
• If there are unforeseen circumstances we must ask the Product Owner to make a decision
• If the Product Owner tells us to take on additional work, it’s okay to sacrifice quality to make it happen
• It’s okay if we didn’t manage all the work from the Definition of Done, as long as we covered all the functional aspects from our Sprint Backlog. We can finish the remaining work in the next Sprint.
• All communication with stakeholders must be done via the Product Owner
• We will inform the Product Owner about the Sprint during the Sprint Review
• It’s good enough if we integrate all our work from the Sprint at the end of the Sprint

And that’s a wrap — Save me a candy! 🧁

Find me on Twitter and why not on LinkedIn 🤷‍♀

References:

Development Team - Why your Scrum Doesn't Work (2/3)

Scrum Guide | Scrum Guides