4 ms·
Sprints and (point-based) estimations on tickets are not to improve software quality, they are to improve manageability of the software development process. If
by cies 4y ago
Sprints and (point-based) estimations on tickets are not to improve software quality, they are to improve manageability of the software development process.
If you work at a product shop, you might well be able to do without them.
If you build software for clients, the planning is VERY important in order keep the client happy. Knowing ASAP that the project is going to miss a deadline/budget/feature is key to whomever manages the relation with the client.
This is why we do sprints and estimations: to know how the project is going so we can update the client ASAP (or find another solution) when things are off.
- adrianmsmith 4y agoAre your projects just two-week projects for the client? Or, if they're longer, do you plan out all the sprints in advance (which isn't really Scrum best practices as far as I understand?). I mean if you have a larger project (larger than two weeks) and you just plan for the next two weeks (as Scrum tells you to do, as far as I understand) how do you know that if you deliver this sprint you'll be able to deliver the project?
- cies 4y agoyou dont. but at least you know when you go off, and can inform the client timely.