Why Agile Scrum Matrix Story Pointing
To begin, let me state unequivocally that there is no problem with story points. The major problem is how to get to the number. The relative sizes of stories are expressed in story points. They can be beneficial for short-term planning. Unfortunately, individuals might get caught up in the numbers and lose sight of the substance, as the process is much more complex than one may think.
People can develop a habit of repeating buzzwords and marketing phrases associated with a specific named or branded system. Many software development teams, I've found, incorporate certain buzzwords into their regular speech and utilize them creatively. It's quite OK for a team to create its own internal dialect. It promotes team identification and attachment while also making work more enjoyable. People, on the other hand, can lose track of a term's original meaning or value. This might sometimes lead to them focusing on things that aren't as important or useful.
What we came up with is not to talk about the points, well at least not at first. We talk about what we can measure on each ticket. This measurement is defined in a matrix which makes the standard for all tickets fitting the same category, providing consistent, educated and repeatable process. Using the matrix rather than the points directly, will encourage teams to understand each Story/Task before pointing them. It will also spark conversation during the grooming session. It is easier to defend the thought process backed by a measurable matrix rather than just a number.
This tool is not a solution to the complex issue od story pointing. It is a system that makes it a bit simpler or less painful to arrive to the desired point.
This is How it works
matrixpointing is a tool mostly benefiting scrum agile teams helping teams to properly point stories. Sctrum Master has an admin role and can create teams and customize them based on their needs by visiting Manage Groups page. The team is created with default pointing matrix categories (Unknown, Complexity, Effort, and Dependency). Each category, has a set of options defined which represent a measurement scale for each category. All categories their options are customizable. You can add or remove them so the matrix aligns with your industry and specific needs. The user becomes admin for any group created automatically.
Adding admins and users to the group
Group admin can add/remove additional Admins and Users. Users are team members helping point the stories and actioning on each ticket.
Setting Up The Pointing Matrix
Required for predefined point
Group admin can add/remove additional Admins and Users. Users are team members helping point the stories and actioning on each ticket.
Adding tickets to the be pointed
Scrum Master adds ticket's details to the pointing page which makes them visible to team members. This has to be does ahead of the grooming session so team members have enough time to review and size them.
Team ticket review and sizing
Each team member can see the tickets added for each group and choose the option they think best represent the task/ticket. These chooses are only visible to group admins and is not revealed until the grooming session.
Grooming session and finalizing the results
During the grooming session, group admin will reveal everyone's choices and team will discuss the reasoning behind each selection. Final choices are set by admin and the matrix will suggest a point for the selection, if it is set previously.
Cleaning up
Finally, admin can save the final choices and move the ticket to archive for referencing.