4 ms·
> slight sense of urgency This is my biggest beef with agile. The urgency is false, stressful, and unnecessary. If you're always in a "sprint" you're never ac
by 2023throwawayy 3y ago
> slight sense of urgency
This is my biggest beef with agile. The urgency is false, stressful, and unnecessary.
If you're always in a "sprint" you're never actually sprinting. No one can sprint forever.
- icedchai 3y agoThe urgency is often fake. You complete your sprint, only to find out you built a feature nobody needed any time soon (or maybe ever.)
- Lutger 3y agoThis is my biggest beef with deadlines in general and sprints in particular. The urgency is fake, but the cost is not. It is not 'free' to set a random deadline. You will pay with productivity and quality and cause stress. There is no way around it, so do it for a sound reason. These days if somebody sets a deadline I always probe them to find out why. "What happens if we are a week late, a month? Is there a reason for that date?" This often annoys people, which reveals me they don't really know what they are doing and it is not actually a real deadline. Just something that people think that project management is. 99% percent of deadlines could be replaced with something like: "this feature is worth a ballpark of 2 to 5 weeks of the team to me. Can we make it? Keep me posted if it doesn't work out, I want to know so I can consider dropping it and pivoting to something else, even when we already invested 4 weeks in it." That is a reasonably thing a manager can ask, and more often than not developers can actually answer this in a much more efficient way than detailing and monitoring a sprint plan.
- icedchai 3y agoI built something in one sprint, only to see it replaced with "V2" two sprints later. "V1" was never used by an actual end user. But, yeah, it worked for demos!