Just reminded of the an old trope for estimates, either: - less than 3 months - 3 months - 6 months Anything less than 3 months - is an accurate estimate. O

Just reminded of the an old trope for estimates, either: - less than 3 months - 3 months - 6 months Anything less than 3 months - is an accurate estimate. Otherwise, 3 months is the amount of time it takes to do _anything_, right? If it's a really hard problem, then we say, okay, it's 6 months. At the end of the day, those 3 months and 6 months means "NFC", which goes back to the estimation technique that everything is either a "1", "TFB", or "NFC". 3 months = TFB, 6 months = NFC On a more serious point, we (as software engineers) generally feel we can solve almost any problem with 3 months worth of resources and effort. 3 to 6 months sometimes (IMO) can be a bit of the scariest estimate to give or receive. For reference & more on NFC/TFB/1 estimation technique: https://pm.stackexchange.com/questions/26218/how-to-implement-tfb-nfc-1-sprint-estimation-technique https://pm.stackexchange.com/questions/26218/how-to-implemen...