3 ms·
Splitting the store into smaller tasks is better. It forces you to plan and communicate your progress. It allows for adjustments in both requirements and estima
by Chyzwar 7y ago
Splitting the store into smaller tasks is better. It forces you to plan and communicate your progress. It allows for adjustments in both requirements and estimation. In many business cases, this approach is better. The senior developer should outperform multiple juniors anyway, in most cases, it is seniors that carry progress.
Toxic companies will twist a good process and make it horrible. It is not Agile or Scrum to blame.
- eropple 7y agoSplitting things is not inherently bad. Doing so in an attempt to commodify its application is not inherently bad. Doing so in an attempt to commodify its application is definitely bad for developers' careers.
- Chyzwar 7y agoIf you care more about career than team success, project delivery and skills progression you are already in a sad place. "Commodify of application" is a good thing. This means that your team is flexible and can adapt to changes. It mean that there little of key person dependencies. It makes you go for holidays without worrying that your team will be able to finish a new service because you are one of two people that can navigate AWS :P