For a programmer, the answer is often "when I wrote the code". But for business, there is no direct benefit from the written code. Let's say the code was dragged to the prod
The purpose of the retrospective is to inspect the process and agree on changes. We felt all the stages of Bruce Tuchman, and the retro sprint showed it very clearly. 1. Forming. At
Ok. Now you're a product developer. What's next? I will talk about the development cycle from the point of view from the inside. Part 1. Working out the backlog.Work on the task
With a casual movement, the programmer disguises himself as a product developer. And now he can already participate in the development of the task at an early stage. Working through the task, the
So, okay, let's say there is a benefit for the product from involving the developer in the development of the task. And why should I, the developer, do this? I'll speak for myself:
