Question
2
Replies
346
Views
Posted: January 29, 2018
Last activity: January 31, 2018
Closed
Solved
What does Sizing mean at Pega?
What is the meaning of 1 story Point at Pega? I have known different teams to do it differently. Some consider 1 Point to be a day. Some follow the classical Scrum thought process of picking us a baseline user story as a 1 pointer and do relative sizing for other stories. What is the suggested practice at Pega? Should we just use 1 point as 1 day because it helps in planning, with the risk of ignoring the aspects of complexity and uncertainty?
My scrum team is currently working almost exclusively in Pega.
I'd start by saying that, if you search the Scrum guide, you won't find the word "story" anywhere. The idea of a user story isn't something that comes from Scrum, so therefore neither does a story point.
In my opinion, the key thought from the Scrum guides that relates to this question is this: "No one (not even the Scrum Master) tells the Development Team how to turn Product Backlog into Increments of potentially releasable functionality." We believe strongly that the team does whatever works for them. My team, for instance, uses relative complexity as a sizing tool. The number of points does NOT correlate to the number of hours of work needed to complete it. We also do not use velocity as a metric that gets reported to stakeholders - it's only for team planning purposes. As we've been through many sprints now, we have a rough idea of the average points we can complete in an increment. That’s really all it’s good for to us.
The answer to your question of “should we use…” then is, you should use whatever works for you. Try something, see if it works. If it doesn’t work, try something different. If it works, see what you can do to improve it.
Hope that helps!