Sprinting Slows You Down: A Better Way to Build Software
thenewstack.io
Sprinting Slows You Down: A Better Way to Build Software
1–8 of 8 posts
Re: Sprinting Slows You Down: A Better Way to Build Software
#2It’s a brave person who stakes their business on swimming against perceived common wisdom. I’ve seen it succeed, at least for a while, at some startups.
The cognitive load of managing expectations of clients, investors, etc who are trained to expect the stand way of doing things seems to get too much though, over time.
Re: Sprinting Slows You Down: A Better Way to Build Software
#3It’s a brave person who stakes their business on swimming against perceived common wisdom. I’ve seen it succeed, at least for a while, at some startups. The cognitive load of managing expectations of clients, investors, etc who are trained to expect the stand way of doing things seems to get too much though, over time.
[flagged]
Re: Sprinting Slows You Down: A Better Way to Build Software
#4It’s a brave person who stakes their business on swimming against perceived common wisdom. I’ve seen it succeed, at least for a while, at some startups. The cognitive load of managing expectations of clients, investors, etc who are trained to expect the stand way of doing things seems to get too much though, over time.
It wasn’t long ago that switching to agile was the “swimming upstream” activity.
Re: Sprinting Slows You Down: A Better Way to Build Software
#5[deleted]
Re: Sprinting Slows You Down: A Better Way to Build Software
#6Deadline by the end of the sprint is not how we typically approach things even in a scrum context. I'm not sure whether there's any words about it in the scrum dogma.
Re: Sprinting Slows You Down: A Better Way to Build Software
#7If you look at sprints as a delivery schedule instead of a benchmark for development speed, sure.
Re: Sprinting Slows You Down: A Better Way to Build Software
#8Small brain: Waterfall
Big brain: Sprints
Galaxy brain: “it will be ready when it’s ready”