Rushing code to production
For some unfathomable reason, it seems like most people think Agile means getting new code out the door as quickly as humanly possible, if not faster.
A sprint is taken as "we can release new stuff every 1 or 2 weeks!" which leads to the sales drones thinking "the customers will love us!". Its all about fast turnaround to new features. The sprint is turned into the tech equivalent of an assembly line or sweat shop, churning out deliverables at a break neck speed.
The idea of an MVP is reduced to "Whats the minimum possible thing we can get away with doing just so it looks good on a feature checklist". Because of the sprints and supposed rapid development, it is thought that you can just flesh things out later.
This is bad both for the customers and for the developers.
For the customer it can mean features that don't really work, or work only within narrowly defined areas. But customers are notorious for exploring features and they will quickly realize the limitations if you don't properly design the feature. They will complain. They will get frustrated. Especially if the feature is what sold them on your product. You are better off having a few features that are well implemented than to have a ton of features that are for lack of a better term half-assed. Even worse is if you have bugs even with the part you have implemented because you didn't take the time to even test what you've created.
For the developers it can mean a complete breakdown in proper development processes. Because process goes out the window, except for the sprint. And even a proper sprint can be pared down to nothing more than "get x features done by this week". It means no real planning, no testing, no discussion between developers. It results in developers being told to implement features in isolation, churning things out without mind to the bigger picture. Or even going behind the backs of senior developers just to get things out quickly.
The short of it is this: You are going to piss off your customers. And you are going to piss off your developers, particularly your senior developers because they've seen this happen before.

No comments:
Post a Comment