|
|
|
|
|
|
by nihil75
1930 days ago
|
|
|
Now I want to be devils advocate and give you the "corporate" perspective - You say Agile disrupts your "flow", makes you deliver buggy code and just work to close tickets like a drone? Good!
Who said code needs to be perfect and bug-free? remember Lean? Just get it out there! we can always fix things later. From a business perspective - we are spending money to develop functionality, not our peoples skills.
Tickets and tasks should result in adding value to the business, not to our codebase. This is a cruel and unsustainable way of thinking, which will have your best developers leaving the company very quickly. But if you're an enterprise corp - you see them as interchangable "resources" anyway, and Agile helps you accomodate to them leaving by splitting the work to small bits and having no single owner. This is also a way of looking at things... |
|
|
I mean, they should but its not always a direct path. Resolving tech debt should speed up delivery of future products and features. Do businesses actually understand that reasoning... not really from my experience. This is really just a lack of understanding or appreciation of nuance for how software is developed by non tech companies that have been forced to hire engineers and create engineering departments.
> Agile helps you accomodate to them leaving by splitting the work to small bits and having no single owner.
This only holds true if you have a team structure and organization that prevents specialists and keeps everyone as a generalist. I don't believe that's actually possible...
Instiutional knowledge is massive, and I feel its often vastly undervalued by companies when engineers decide to leave.