Skip to main content
7 events
when toggle format what by license comment
Oct 24, 2018 at 13:42 comment added Todd A. Jacobs @Pat No. Velocity should not continually increase once it reaches a stable optimum. Nor should stories that require less effort have the same point value. Comments are not for extended discussion, so please turn your comment into a new, linked question if you want a more complete answer.
Oct 24, 2018 at 5:23 comment added Pat I always see this kind of calculations where velocity is thought to be constant. While the fact is, it should see a gradual increase over sprints, as the team gets proficient at implementing features, plus later stories may leverage some of the existing features to be implemented. E.g. to add the first authorisation role of say 'Support' will need the implementation of Auth framework, but later adding a new role 'Admin' wouldnt be same effort. Though, they both relatively may be of similar points. So velocity should ideally increase. This invalidates the projected release date.
May 11, 2018 at 17:13 comment added Seasoned Project manager The "cashing out" early assumes the PO and whole team have understood MVP properly and have been working on this before all else - that is a major statement/assumption and I would say exists more in Scrum classrooms rather than the real world.
Oct 5, 2015 at 17:48 vote accept John
Oct 3, 2015 at 21:51 comment added Todd A. Jacobs @Tivep In that case you guesstimate. The important thing is that you acknowledge that it's a guesstimate cobbled together for planning purposes, and don't treat it as a high-confidence precision value.
Oct 3, 2015 at 16:41 comment added John Oh this is great @codegnome! Just one clarification. When you say the velocity for the team based on history is 20, each of the members of the team may be from different teams. While their past team's velocities might be known, how do I calculate the velocity of the new team?
Oct 3, 2015 at 15:06 history answered Todd A. Jacobs CC BY-SA 3.0