游戏开发编程估算.pptVIP

* Complexity Points: Estimates the “bigness” of a problem, influenced by its difficulty and how much of it there is. Effort- Hours: Estimates the ideal effort to complete a task. Regardless of which you use, make sure you understand and are consistent in the use of the “unit” you’re talking about. * * * Your ability to decompose a large task is related to how familiar you are with it. If you are unable to decompose the task, this is a sign you should seek help (collaboration). * * 1. Find a method that works for you. 2. Note that your project may use a different method, so be sure to have a convenient mapping between them. * * * Note that tracking time spent on a task allows you to identify how much time you’re spending on the task in a given day. It can help lead to other questions. * * * * Velocity is work (complexity points, effort hours, etc.) / unit time (day, week, sprint, or release). Calculating velocity makes the connection between the estimate and the schedule. Keep in mind that this can be at different scales. Typically user-stories operate on a Complexity Point / Ideal Days level, while tasks operate on an Effort Hours level. * Remember, velocity is concerned about complexity or effort hours / unit time while MRE is concerned about the accuracy and precision of your estimate. While you CAN game the system, since the data is really only for your own consumption, you’re not really helping yourself if you do. This works using both complexity points and effort hours * 1. Note: By updating the work remaining you’re not changing the original estimate. Updating future estimates != Updating Work Remaining. * 1. You cannot expect the project or the project’s choice of project management tools to do this for you. This WILL require work on your part. * * * 1. We didn’t just make this stuff up. 你的时间都花在何处？ 练习：在下一个用户故事（user-story）或任务中，请试着跟踪你的时间使用情况。观察一下你把时间都花在了何处。 回顾 我是如何做的? 我是如何做的? 问以下问题： 你工作有多快？ 你的估算与实际结果有多接近？ 我是否忘了对有利于下次任务估算的某事项作出预测？ 对结果进行分析 有用的计算 速度 你工作有