Rally Software

Expand all | Collapse all

Actual Stories Completed versus Committed Stories

Jump to Best Answer
  • 1.  Actual Stories Completed versus Committed Stories

    Posted 12-08-2015 01:58 PM
    What is the best way to measure actual user stories (and story points) completed versus committed user stories (and points)?  I cannot use the "Track > Release Metrics" page because it counts user stories that were continued into the next iteration as completed (the process of splitting the user story marks the incomllete story as Accepted), nor does it show story points.

    There seem to be lots of different ways to gather each data element and calculate it outside the tool, but is there an easy way inside the tool?


  • 2.  Re: Actual Stories Completed versus Committed Stories

    Posted 12-09-2015 09:36 AM
    Have you checked out the Cumulative Flow Diagram chart app to see if that'll help?


  • 3.  Re: Actual Stories Completed versus Committed Stories

    Posted 12-09-2015 11:54 AM
    Yes, I have been using this at the release level.  Your reply caused me to realize that the app also versions for the iteration level as well.  This is useful managing the team in-sprint.




    More than this, though, I am looking more for a method of creating a metric that I could calculate for each sprint, and then trend it.  At this point, all I can come up with is manually reviewing the burn reports, writing down the story points committed on the first day of the iteration, then writing down the number of point completed on the last day of the iteration.  Not very elegant...


  • 4.  Re: Actual Stories Completed versus Committed Stories

    Posted 12-09-2015 12:17 PM
    One other way may be to use the Rally Excel add-in and get targeted data using queries (each workbook can have a specific query). Then you could use pivots etc. to capture this data somewhat automatically. You may want to keep the chart data separate from the query page data for trending purposes as the query data will override existing data in that workbook where it is run. Not sure if this helps?
    Agreed - Rally could certainly do a lot more by offering useful apps that capture such needs better.


  • 5.  Re: Actual Stories Completed versus Committed Stories

    Posted 12-09-2015 02:00 PM
    Good idea on the Excel Add-In.  I had completely fogotten about it.  Thanks.  I will give ita try.


  • 6.  RE: Actual Stories Completed versus Committed Stories

    Posted 01-17-2020 09:33 AM
    I was searching around for a way to measure user stories committed vs. completed and came across this older post. With all of the feedback and improvements, are there been any new apps or methods to get this information?

    ------------------------------
    Agile Coach
    Boston, MA
    ------------------------------



  • 7.  RE: Actual Stories Completed versus Committed Stories

    Posted 01-17-2020 09:39 AM
    Hi Stephen,

    Don't know if you are aware of this app: https://github.com/RallyTechServices/committed-vs-delivered

    ------------------------------
    Nik
    Rally Sales Engineer
    Rally Software
    ------------------------------



  • 8.  RE: Actual Stories Completed versus Committed Stories

    Posted 01-17-2020 10:13 AM
    Hi Nik - Thanks! I was not aware of that app. I'll check it out.

    ------------------------------
    Agile Coach
    Boston, MA
    ------------------------------



  • 9.  RE: Actual Stories Completed versus Committed Stories

    Posted 01-18-2020 06:59 PM
    I've used that app and even modified it to show defects. I would love to see it show stories and defects together, and to give the option of points instead of count.

    ------------------------------
    Terry Ginzburg
    ------------------------------



  • 10.  RE: Actual Stories Completed versus Committed Stories

    Posted 01-23-2020 02:49 PM
    It looks like a great app. Although I agree with Terry, having the option to look at it with points would make it very valuable.
    Just a count of stories, really doesn't give a lot of meaningful information, atleast in our case.

    Regards,
    Nivi

    ------------------------------
    Project Coordinator
    John Deere
    Cedar Falls, Iowa
    ------------------------------



  • 11.  RE: Actual Stories Completed versus Committed Stories

    Posted 01-28-2020 09:03 AM
    I totally agree.It will be great if this app also display the story points.


  • 12.  RE: Actual Stories Completed versus Committed Stories
    Best Answer

    Posted 01-28-2020 10:49 AM
    Hi Eda,

    https://github.com/nikantonelli/committed-vs-delivered

    Added an app setting so that you can do it for stories. I didn't do a similar change for Portfolio items. Pick up the contents of Ugly.txt from the deploy directory.

    ------------------------------
    Nik
    Ask me a question, I'm All Ears!
    Rally Sales Engineer
    Rally Software
    ------------------------------



  • 13.  RE: Actual Stories Completed versus Committed Stories

    Posted 01-29-2020 01:48 PM
    Wow, Nik, thank you! I modified a version of this app to do add an Acceptance offset window and accept a query, but hadn't figured this one out yet.

    Can you make a version that combines stories and defects, so a team can see their total commitments and delivery?

    I don't ask for much...  ;)

    ------------------------------
    Terry Ginzburg
    ------------------------------



  • 14.  RE: Actual Stories Completed versus Committed Stories

    Posted 01-29-2020 02:55 PM

    Thank you Nik! This would be a great metric!

     






  • 15.  RE: Actual Stories Completed versus Committed Stories

    Posted 02-03-2020 12:19 PM
    Follow up question, Nik.

    In the below graph, I understand the Committed bar - both green and yellow. But I'm struggling with the Accepted bar.
    What do the green and yellow mean here?
    Do they correspond to the Green and Yellow on the committed?




    ------------------------------
    Project Coordinator
    John Deere
    Cedar Falls, Iowa
    ------------------------------



  • 16.  RE: Actual Stories Completed versus Committed Stories

    Posted 02-03-2020 01:13 PM
    For the Delivered colour stack, the green is for those stories that are currently marked as accepted and were placed into the timebox at the start (up to and including the planning window you have set), and yellow is for those stories that are marked as accepted that were added to the timebox after the planning window had elapsed.

    Hope that helps.

    ------------------------------
    Nik
    Ask me a question, I'm All Ears!
    Rally Sales Engineer
    Rally Software
    ------------------------------



  • 17.  RE: Actual Stories Completed versus Committed Stories

    Posted 02-03-2020 01:20 PM
    One clarification - this app doesn't show all items 'currently marked accepted' but rather items accepted during that timebox. So if a print ended on January 31st and a story within that sprint was accepted on February 3rd, it would not show in the Delivered column for that sprint. I frequently have to explain this to our users - if they don't Accept work during their sprint, it won't show as Delivered on this app. This is different from the Rally Velocity Chart, which shows accepted items with two colors - one for items accepted during the sprint and one for items accepted after the sprint.

    ------------------------------
    Terry Ginzburg
    ------------------------------



  • 18.  RE: Actual Stories Completed versus Committed Stories

    Posted 02-03-2020 02:12 PM
    Ahh, yes. There is a bit of code that looks like it wasn't finished. If a story is "AcceptedBeforeTimeboxStart", which means it was flagged as "outside of timebox", it doesn't actually count them. I suppose that could be easily changed by someone.....

    ------------------------------
    Nik
    Ask me a question, I'm All Ears!
    Rally Sales Engineer
    Rally Software
    ------------------------------



  • 19.  RE: Actual Stories Completed versus Committed Stories

    Posted 02-03-2020 02:48 PM

    It also doesn't count items accepted after timebox ends. On my local version I added an Acceptance Offset that works like the Planning Offset, so that if teams plan their sprints on Day 1 rather than before Day 1, which means they may also be doing clean-up of the prior sprint, they can set both Offset values to 1 and have it pick up as Planned anything added by the end of day 1, and pick up as Accepted anything accepted by the end of the day after the sprint ends. It would be nice if it would show all accepted work in that sprint, but maybe highlight the items accepted after the timebox in some way so you can see the difference.

     

    Terry Ginzburg
    Lead Platform Engineer
    Product Tooling
    3400 New Hyde Park Road
    North Hills, NY 11042
    p: 516.300.4687 | 
    m: 516.322.8226

     






  • 20.  RE: Actual Stories Completed versus Committed Stories

    Posted 02-04-2020 07:06 AM
    I started to look at this (see image below), but came across a bit of an issue that would probably mean a large change to fix. If you move stories about in iterations (or releases), then the  LBAPI gets a snapshot record for it's presence in that timebox. At the moment, the app doesn't know which timebox it should be in unless it checks for something like which timebox it was started in (InProgressDate) and then use the 'current' setting of its timebox for comparison/calculation.

    @Terry Ginzburg, I will post the code changes I did to make the image below on this branch:https://github.com/nikantonelli/committed-vs-delivered/tree/comm-vs-del-with-exception



    ------------------------------
    Nik
    Ask me a question, I'm All Ears!
    Rally Sales Engineer
    Rally Software
    ------------------------------



  • 21.  RE: Actual Stories Completed versus Committed Stories

    Posted 02-19-2020 12:50 PM
    Could someone please explain the logic behind "Committed" in this app?

    ------------------------------
    Agile Coach
    Boston, MA
    ------------------------------



  • 22.  RE: Actual Stories Completed versus Committed Stories

    Posted 02-19-2020 12:57 PM
    Committed items are items that are in the iteration. If they were added before the iteration started (or by the end of the offset day if that is set) they are green, identifying them as Planned. If they were added during the iteration, they are yellow, or Not Planned.

    ------------------------------
    Terry Ginzburg
    ------------------------------



  • 23.  RE: Actual Stories Completed versus Committed Stories

    Posted 02-11-2020 09:42 AM

    Hello there!

    Thank You for the code!

    Any chance that it can be modified so it works on an iteration filtered custom page?

    When I try that it loads indefinitely.

    It works when I add it to a simple custom page.

    Thanks

    Janos




  • 24.  RE: Actual Stories Completed versus Committed Stories

    Posted 02-24-2020 10:30 PM
    Hi Nik,

    I am a Program Manager (RTE) at Unum and we are using Rally to manage our enterprise portfolio.  I have configured a dashboard and added several apps from the app catalog available w/in Rally which includes many apps from Github.  While researching online via Google I came across this thread which mentions an Actual Stories Completed vs Committed Stories app.  I don't see this available via the Rally app catalog but I do see it available via GitHub.

    While I used to be a Software Developer many moons ago, I am not sure how/if I can download your app direct from GitHub and run it local on my laptop against our cloud-hosted version of Rally.

    Any insights you can share that may help would be appreciated as I'd really like to use your https://github.com/nikantonelli/committed-vs-delivered 

    Actual Stories Completed versus Committed Stories app.

    Chris K.

    ckennedy@unumcom 




  • 25.  RE: Actual Stories Completed versus Committed Stories

    Posted 02-25-2020 01:49 AM
    Edited by Nik Antonelli 02-25-2020 01:52 AM
    Hi Chris,

    You will need to grab the contents of this file: https://github.com/nikantonelli/committed-vs-delivered/blob/master/deploy/Ugly.txt and stick it into the HTML field in the app settings of the Custom HTML app.

    There is a little bit of info about the Custom HTML app here: https://techdocs.broadcom.com/content/broadcom/techdocs/us/en/ca-enterprise-software/agile-development-and-management/rally-platform-ca-agile-central/rally/customizing-top/use-apps/app-catalog/custom-html.html.

    Once you save it, the app should run and create its own app settings menu entry under the gear menu icon.

    ------------------------------
    Nik
    Ask me a question, I'm All Ears!
    Rally Sales Engineer
    Rally Software
    ------------------------------