TE
科技回声
首页24小时热榜最新最佳问答展示工作
GitHubTwitter
首页

科技回声

基于 Next.js 构建的科技新闻平台,提供全球科技新闻和讨论内容。

GitHubTwitter

首页

首页最新最佳问答展示工作

资源链接

HackerNews API原版 HackerNewsNext.js

© 2025 科技回声. 版权所有。

Making productive retro of a feature that went over estimation

1 点作者 deepsy大约 4 年前
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?

暂无评论

暂无评论