Scrum development is based on listing user stories and their implementation during sprints. This approach - focusing on the real goals of the final product - certainly has its merits, but what bothers me is that it does not protect the creation of any universal / reusable code in the process, and in fact I feel that he advocates hacking. For example, if a user story says
It should be able to display x depending on y and place the string there.
My first thought is that "hey, I need to create a common graphic structure so that I can handle such cases more efficiently later." But this is not the goal in the sprint fight; the goal is just what the user story says.
Thus, it is more preferable (from the point of view of Scrum) to simply hack something together so that the user story is realized, instead of trying to understand the big picture and create something more general (which, of course, takes more time initially).
Is it really inevitable? Am I misunderstood something? How do you combine Scrum'ing with the actual product with the creation of something reusable at the same time? Is reuse old-fashioned and overrated?
source
share