• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Bear Bibeault
  • Ron McLeod
  • Jeanne Boyarsky
  • Paul Clapham
Sheriffs:
  • Tim Cooke
  • Liutauras Vilda
  • Junilu Lacar
Saloon Keepers:
  • Tim Moores
  • Stephan van Hulst
  • Tim Holloway
  • fred rosenberger
  • salvin francis
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Carey Brown

Agile and Estimation

 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Robert,

This is another issue that I have been grappling with. Do you have any word of advice as to how you balance business expectations for a target product delivery vs. the realities of development and the fact that "estimation is hard". It's a conundrum that I frankly don't have an answer for. The reason being, there is a cost-benefit analysis for any product/feature that needs to be developed and it is always a tough conversation when you have to set the right expectations.

Thanks
 
Sheriff
Posts: 15801
264
Mac Android IntelliJ IDE Eclipse IDE Spring Debian Java Ubuntu Linux
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
The book has a section about the "Iron Cross" of project management: Good, fast, cheap, done. Pick any three you like. You just can't have the fourth. This is also referred to as the Iron Triangle of project management. Agile is supposed to give you data that you can use to make those hard choices.
 
VP Krish
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Thanks. Hope to review that.

Regards
 
Consider Paul's rocket mass heater.
    Bookmark Topic Watch Topic
  • New Topic