We don’t allow questions seeking recommendations for software libraries, tutorials, tools, books, or other off-site resources. You can edit the question so it can be answered with facts and citations.
Closed 6 years ago.
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
接受
或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
发布评论
评论(2)
Mike Cohn 在 他的博客。 我发现他的写作风格简洁明了。
我特别喜欢他的备用燃尽图,它跟踪团队在正 y 轴和负 y 轴上添加/重新调整范围的新工作。 通过使用已完成工作和添加工作的趋势,您可以合理地估计项目的结束日期。
Mike Cohn has a good example of the burndown chart on his blog. I find his writing style succinct and concise.
In particular I like his alternate burndown chart, which tracks the work completed by the team on the positive y-axis and the new work added/re-scoped on the negative y-axis. By using the trends of the work completed and work added will give you a reasonable guesstimate of the project's end date.
我总是发现 ScrumForTeamSystem 流程指南是任何 Scrum 的参考资料,例如:
http:// /scrumforteamsystem.com/processguidance/v2/ProcessGuidance.aspx
当事情按预期进行时,冲刺燃尽图将是一个漂亮的趋于零的线性图:
http://scrumforteamsystem.com/processguidance/v2/Images/SBBurndown.html
产品待办事项列表应该看起来像一个清晰的优先级产品所有者提供的用户故事列表,您可以在其中进行高级估计并用作创建小型开发工作项(也称为冲刺待办事项项)的基础:
http://scrumforteamsystem.com/processguidance/v2/Artefacts/ProductBacklog/ProductBacklogContents.aspx
希望这会有所帮助。
I always find the ScrumForTeamSystem process guidance as the place to go for reference for anything scrum like:
http://scrumforteamsystem.com/processguidance/v2/ProcessGuidance.aspx
A sprint burndown chart when things are going as they should be will be a nice linear graph towards the zero:
http://scrumforteamsystem.com/processguidance/v2/Images/SBBurndown.html
And a product backlog should look like a nice clearly prioritized list of user stories delivered by your product owner on which you can give high level estimates and use as a basis for creating small development work items otherwise know as sprint backlog items:
http://scrumforteamsystem.com/processguidance/v2/Artefacts/ProductBacklog/ProductBacklogContents.aspx
Hope this helps.