Forums for the Business Analyst

 
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  User Story Points
Previous Previous
 
Next Next
New Post 5/13/2009 2:30 AM
User is offline George
6 posts
10th Level Poster


User Story Points 
Modified By George  on 5/13/2009 4:31:02 AM)

 

I'd like your opinion and any advice you can offer on the following scenario please:

We have a organisational business need to be able to compare projects across departments. As such the business has picked up on story points and is looking to compare project based on their story point velocity!!!
 
I see two possible solutions to the above requirement:
 
  1. Replace the use of story points with Ideal Days which should give a better comparison across projects (but does lose the benefits of Story Points).
 
  1. Change Story Point estimation from a relative measure of complexity (within a project) to an absolute measure of complexity that can be compared across projects – this would require some level of governance to ensure a standard is applied.

 

 
New Post 5/13/2009 10:32 AM
User is offline Adrian M.
733 posts
3rd Level Poster




Re: User Story Points 

Hi George,

You bring up a great question!

I think that the "relative" property of Story Points is exactly what you need and you don't want to change that. Story points (similar to Function Points & Use Case points) have been introduced so that projects can be measured and quantified much sooner in the development process, based on the requirements and desired features, and do it in a way that can be compared across projects, etc.
The idea is that you can compare the relative complexity of requirements between projects - which is probably all you need at the high-level.

If you want to go to a deeper level of granularity you would need to employ a formula for converting Points (story, function, use case, etc.) into effort rather than changing the relative nature of points. Unfortunately, that is not easy since given the same exact requirement (sorry - I mean story) the actual effort could vary depending on a number of parameters such as:

  • type of technology employed,
  • type of programming language,
  • technical team skills set,
  • familiarity with the subject matter (on the BA side),
  • etc.

What is it exactly that you are trying to accomplish when comparing projects across departments?

If you're using story points, you will still need some level of governance and/or standards to ensure that story points are counted consistently across teams/departments.

Just some thoughts!

- Adrian


Adrian Marchis
Business Analyst Community Blog - Post your thoughts!
 
New Post 5/18/2009 2:35 AM
User is offline George
6 posts
10th Level Poster


Re: User Story Points 

Thanks Adrian,

Appreciate the comments.  You've highlighted the problem we face in how to correctly translate a story point into something the Board can understand and hold you to.

It is hoping to accomplish a baseline measurement for current and new projects where a project from any channel can be picked up and estimated by a Programme Director.  This is where our dilemma of 'complexity' scoring vs 'ideal day' scoring has come from.

The variables involved in coming up with something useful here are very awkward due to the cross-channel functionality of this business.

I agree when you say we need to come up with a formula that can account for a lot of these variables.

Thanks for replying.   

 
New Post 8/25/2009 2:35 PM
User is offline Craig Brown
560 posts
www.betterprojects.net
4th Level Poster




Re: User Story Points 

George -definitely take a look at Mike Cohn's book 'Agile planning and estimating.'  This scenario is explicity addressed.

What I am about to do this next fortnight is use story points across two different projects and get a compare. I am not following Cohn's advice exactly but am doing the following; Creating two sets of SP estimates independent of each other - obe is from an existing 'in train' project and one is new. The new one will only have  high level storis - hich means that th scale won't be comparable. 

(One will have a bunch of 2, 5 and 13 point stories, the other if using the same baseline will be full of 100point stories.)

We'll then be picking a sample from one of the new stories and and breaking it down so we can do a detailed compare of the SP at a detailed level.  Then we'll calibrating the new to the old.

This sounds complex, but that may just be my explanation.

The real issue is that team velocity will vary based on a number of factors, some of which Adrian mentioned.  So Story points alone don't give an end date.  You really have to invest a sprint two (or 3) before you start to get  picture of the duration.

 
Previous Previous
 
Next Next
  Modern Analyst Forums  Business and Sy...  Agile Analysis ...  User Story Points

Community Blog - Latest Posts

Gen1us2k
Gen1us2k
Most of the IT projects imply constant cooperation between the team members and customers. Although it might be often overlooked, the role and the importance of the client within the project is very crucial. Thus, it is in your interest to build a strong relationship based on trust. However, gaining trust on a single occasion is not a dealmaker &md...
0 Responses
emorphistechno
emorphistechno
Introduction In today's world, most enterprises work aggressively to achieve a higher level of business growth, which is made possible by leveraging one of the best automation technologies. One such technology is Robotic Process Automation (RPA) that plays a vital role in streamlining the customer experience in the most profitable manner.&nb...
0 Responses
Nick Stowers
Nick Stowers
Introduction   When I was introduced to scrum, the burndown chart was a tool that was highly emphasised however I feel the purpose has changed from it being a tool to predict (to a certain level) timescales for delivery to a tool that measures a team’s productivity…..in other words, the focus is on the number of points clear...
0 Responses






Copyright 2006-2020 by Modern Analyst Media LLC