Software development takes time and has many unanticipated challenges that makes time estimation difficult. When developers do provide estimates users, managers etc then get stroppy when they slip by.
Therefore the best strategy is just to ignore requests for time schedules because it's a no win situation.
Software development takes time and has many unanticipated challenges that makes time estimation difficult. When developers do provide estimates users, managers etc then get stroppy when they slip by.
Therefore the best strategy is just to ignore requests for time schedules because it's a no win situation.
I think you might be confusing estimates and fixed-cadence releases. It's really simple to provide a promise of fixed-cadence releases - just take whatever changes are merged (if any) and release them on the cadence.
Promising to release a specific feature within a specified timeframe is a different beast entirely.
I think releases are just whenever they're ready
He'll tickle your feet when he's ready to release
Usually tickling his feet makes him release.
Just leave us your address below and we'll send over a personal feet tickling service. Six hour guarantee!
Software development takes time and has many unanticipated challenges that makes time estimation difficult. When developers do provide estimates users, managers etc then get stroppy when they slip by.
Therefore the best strategy is just to ignore requests for time schedules because it's a no win situation.
I think you might be confusing estimates and fixed-cadence releases. It's really simple to provide a promise of fixed-cadence releases - just take whatever changes are merged (if any) and release them on the cadence.
Promising to release a specific feature within a specified timeframe is a different beast entirely.