Timeline for How does a scrum team measure its productivity against its productivity pre-scrum?
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 9, 2016 at 15:43 | comment | added | Bartek Kobyłecki | @JeffLindsey While replying, I had a Scrum hat on :) I encourage people to use Scrum when they really mean Scrum described in the Scrum Guide. This sentence: "An accurate forecast for Sprint Backlog, meeting a Sprint Goal and satisfied Product Owner is enough to measure Productivity." means to me exactly what you wrote in your comment, that is, well-used features by end users. | |
| Mar 9, 2016 at 14:16 | comment | added | Jeff Lindsey | Quick comment here - not sure if you were replying with the "strict Scrum hat on" (forgive me if you were!), but I think most agilists are quickly moving away from velocity and quality as key metrics, and focusing more on actual, measurable value delivered. That is, a PO-dependent team delivering 100 bug-free story points that are hardly used by customers is not as "productive" or effective as a team delivering only 50 story points of well-used features with minor bugs, on a path to becoming domain experts themselves. | |
| Mar 8, 2016 at 21:40 | history | answered | Bartek Kobyłecki | CC BY-SA 3.0 |