News for hackers. Stuff that matters.
Re:Coding, Fast and Slow: Developers and the Psychology of O... by Aqueous on Tuesday April 23, 2013 @09:07PM (#5599024)
I've run into this problem and I've gotten much better at estimating. Solution? You should schedule your sprints exactly by degree of difficulty (in descending, not ascending, order). During my design phase I focus on what the hardest problems are and always schedule my sprints to do them first. If you've abstracted away your planned functionality well enough you should be able to isolate that problem and go there first, no matter how much other functionality is intertwined with the feature. That way as you go further along in the project it gets easier, not harder, to meet your deadline.

There are no comments on this comment yet.