3 ms·
Pivotal doesn't use sprints. Stories are pointed by engineers and ordered by the PM, but they're done when they are done, to the satisfaction of both. Tracker
by jacques_chester 7y ago
Pivotal doesn't use sprints. Stories are pointed by engineers and ordered by the PM, but they're done when they are done, to the satisfaction of both.
Tracker is able to give short-term forecasts of what will be done by when by averaging the last 3 weeks of deliveries (ie, velocity).
Personally I think the idea of sprints is a menace. It creates an artificial deadline that leads to either waste or stress. Deadlines should be reserved for actual meaningful deadlines.
- philliphaydon 7y agoI think that artificial deadlines and stress exist because the team and management allow it to exist. A story should fit into a sprint, but it may spill into the following sprint, but you shouldn't sacrifice quality just because you tried to finish it within the sprint. And a team should stand up for themselves in this regard, as a team, because a team succeeds and fails together. If you sacrifice quality because of some artificial deadline you put in place then you're only going to suffer maintaining that later on.
- jacques_chester 7y agoI agree with you on these points. Especially the importance of being a team that doesn't sacrifice quality for calendar sparkles. It's just that I've seen the evil twin version of sprints far more than the official version.
- pflenker 7y agoI think two core ideas of sprints are to 1) combat Parkinson's Law by creating an artificial deadline (the team should try to solve things within the sprint) and 2) protecting the team from changes (avoiding that requirements change all the time) With that in mind, sprints can work pretty well, and work "spilling over" to another sprint is generally no problem. It starts falling apart if the artificial deadline becomes a forced deadline, or if the protection part is dropped.