TE
TechEcho
Home24h TopNewestBestAskShowJobs
GitHubTwitter
Home

TechEcho

A tech news platform built with Next.js, providing global tech news and discussions.

GitHubTwitter

Home

HomeNewestBestAskShowJobs

Resources

HackerNews APIOriginal HackerNewsNext.js

© 2025 TechEcho. All rights reserved.

Making productive retro of a feature that went over estimation

1 pointsby deepsyabout 4 years ago
Our team got into the situation in which a feature that was planned to take 2-3 days (estimated as 5 days, because a less experienced developer was working on it) took almost 2 months to build. The feature was in python - previously the developer didn&#x27;t have experience with it, but it was as fairly simple: mapping an input to external API and mapping the response back.<p>How would you advise us to do a productive retrospection of the events that happened without turning it into a blame war?

no comments

no comments