Design and Agile Estimation


May 20th 2010

Here's a problem my team confronts every sprint:

Feature X seems straight-forward, and so is given an estimate of 2 story points. At the start of the sprint, however, the developer realizes there are a few different options for how to design and implement this feature, and each option carries with it different "ility" trade-offs - e.g. reusability, reliability, extensibility, maintainability, etc. The option that is selected has significant impact on the time it will take.

There are a few different problems entangled in this scenario:

  1. Who is decides which design option is chosen?
  2. What happens Agile Estimation Techniques Agile Estimation - story points vs. hours Scrum - When do you Estimate the Effort for Product Backlog Items? Task Estimation: Do or Don't?
I'm an "old" programmer who has been blogging for almost 20 years now. In 2017, I started Highline Solutions, a consulting company that helps with software architecture and full-stack development. I have two degrees from Carnegie Mellon University, one practical (Information and Decision Systems) and one not so much (Philosophy - thesis here). Pittsburgh, PA is my home where I live with my wife and 3 energetic boys.
I recently released a web app called TechRez, a "better resume for tech". The idea is that instead of sending out the same-old static PDF resume that's jam packed with buzz words and spans multiple pages, you can create a TechRez, which is modern, visual, and interactive. Try it out for free!
Got a Comment?
Comments (0)

 None so far!