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 04-15-2020 08:47 PM
    Hi Janos,

    Did anyone reply to your issue?  I just added the code and get the same issue for a cutom page that is iteration filtered, it just tries to load indefinitely.  Has anyone looked into this or found a solution for this?

    Regards,
    Tony


  • 25.  RE: Actual Stories Completed versus Committed Stories

    Posted 04-17-2020 10:32 AM
    Hi Tony,

    It is unlikely that anyone will modify the code to do this. The app was really intended to show the numbers across a collection of iterations. The whole code may need to be ovehauled to make it respect the timeboxscope of the page. The reason for the crash is that someone started to write it to support timeboxscope, but never followed through on it.

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



  • 26.  RE: Actual Stories Completed versus Committed Stories

    Posted 04-17-2020 10:44 AM

    Is it possible to make it 'disrespect' or ignore the timebox filter at the top of the page?  I think the use case is that a team might have a dashboard that mostly shows information about a specific iteration, but then includes this app to show a historical trend on the same page. Otherwise why would you want it to show just one Iteration? Is there a simple setting to tell it to ignore the page-level filter?

     

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

     






  • 27.  RE: Actual Stories Completed versus Committed Stories

    Posted 04-17-2020 10:49 AM
    Sure, it's here: https://github.com/nikantonelli/committed-vs-delivered


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



  • 28.  RE: Actual Stories Completed versus Committed Stories

    Posted 04-20-2020 10:48 AM
    Edited by Soares 04-20-2020 05:05 PM
    Thanks Nik​ and all contributors - It is now working within my Iteration filtered view.  I would like to use this for an Iteration status and that is why I needed it filtered by Iteration.
    What is the feasibility of displaying the actual metrics for all, meaning the number of scheduled, the number of unscheduled actually displayed on the screen, either within the graph or as a table at the bottom?  The values now appear when I hover over them with the mouse, but if I want to take a snapshot, to save as a pdf point in time, for instance, I only get the overall total committed vs completed, and don't see the breakdown.

    Also, the committed column has the planned count, which is what we use to show the load after day 1 of sprint planning, but the unplanned gets a bit confusing, because in some cases, user stories are swapped with other blocked stories, etc, and this gives the appearance of a total commitment much higher than planned.  Is there a way to make it selectable, if I just want to see the planned committed and not the unplanned?

    Thanks,
    Tony


  • 29.  RE: Actual Stories Completed versus Committed Stories

    Posted 04-27-2020 11:47 AM
    ​Hi Nik,

    Do you have any feedback on the proposed changes that I mentioned earlier?  Having the flexibility to show the actual data would be very helpful, especially to leverage the graph view as part of a status that is being extracted as an image and not real time.  Also, we use committed as the committed number of points after day one of Iteration, once teams plan their iteration.  We then measure that against what is accepted at the end of iteration.  The accepted portion of the graph is perfect. however, the committed side, it would be preferable if we could select if we want to see unscheduled vs scheduled, if possible.  For our purposes, I just need to see the scheduled committed.  Please advise if this is doable or not.

    Thanks,
    Tony Soares


  • 30.  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 




  • 31.  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
    ------------------------------



  • 32.  RE: Actual Stories Completed versus Committed Stories

    Posted 04-29-2020 04:12 PM
    Nik,

    I just copy/pasted in the March 27th version of the code you pointed me tohttps://github.com/nikantonelli/committed-vs-delivered/blob/master/deploy/Ugly.txt
    and pasted it into the HTML field in the app settings of the Custom HTML app.  I then modified the app settings to show iterations versus releases and then hit save.  It has been spinning indefinitely with a "Loading..." spinning icon and message but the page does not paint with the graphical result.

    Is there something wrong with the latest version of the HTML code behind the link you provided?

    Chris K.

    ------------------------------
    IT Program Manager
    Unum
    ------------------------------



  • 33.  RE: Actual Stories Completed versus Committed Stories

    Posted 04-30-2020 04:42 AM
    I have rebuilt both variants (App.txt and Ugly.txt) to the latest contents of my machine. The one you picked up won't work on an Iteration Scoped page, but the latest build should.

    If you are not using an Iteration scoped page, then I am not sure what the issue might be. In these situations, I open the debugger in the browser and look at what gets spewed out of the console. If there is an error there, can you copy and paste it in a PM to me?

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



  • 34.  RE: Actual Stories Completed versus Committed Stories

    Posted 05-11-2020 04:46 PM
    Hi Nik -
    I really like this app and want to have my teams start using it; however, there is 1 observation that causes confusion.  If a story reflects the current sprint at any point during the day, it could show as unplanned; however, I see situations where seconds later, the sprint was changed (perhaps typo, perhaps copy) to a future sprint and was never in the current sprint.  Some Scrum Masters were trying to compare to the scope line of the Iteration Burnup app and it takes a while to go through and figure out the differences.  Could the app just look at where the stories land at end of day?  Thanks!

    ------------------------------
    E Vargas
    ------------------------------



  • 35.  RE: Actual Stories Completed versus Committed Stories

    Posted 05-12-2020 11:22 AM
    Hi @Erin Vargas, I understand what you are trying to say there, but the app is not designed like that. The premise of the app was that​ you decide what stories are going to be in the sprint during the planning window and then the stories are fixed for that sprint. In this scenario, there shouldn't be any "Oops!' moments like you describe if your planning 'goes to plan', so to speak.

    If you have an issue with ongoing scope change throughout the sprint, you might want ot consider this app: https://github.com/RallyTechServices/iteration-scope-change-by-project

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



  • 36.  RE: Actual Stories Completed versus Committed Stories

    Posted 05-12-2020 12:24 PM

    Hi Nik,

    I agree with the way the app is working.  We do get the same feedback from our users because they copy stories that are in the current iteration, so the copy is automatically IN the current iteration. They immediately move the copy so think it shouldn't show on this app in the current iteration since it was only there for a few minutes. My question back to them is "Why are you copying stories?"  There are so many issues caused by copied user stories (including a defect we reported where the schedule state of the copied story is changed based on the task workflow) that I always recommend NOT doing it at all. I recommend using templates if you're copying to carry over some common features (e.g. tasks, description, etc.).



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



  • 37.  RE: Actual Stories Completed versus Committed Stories

    Posted 05-29-2020 09:48 AM
    Hi Nik and Terry,

    I have been following this specific post for some time, and ​in my world, I can relate to what Erin Vargas raised. Our reality is that throughout the sprint, rarely is it "perfect" in the sense that after day 1 of planning, we get nothing else that enters the iteration.  There are usually user stories that sometimes get assigned to the iteration by mistake and then pulled out again.  With this app, it would only show that the user story points were added as unplanned but not show that they got removed, so it shows an "inflated" number of total committed (planned + unplanned) points, and it gets confusing.

    For my needs, which I have yet to find an app that has this simple view:  Something that displays all the points as committed, up to and including day 1 planning, and the total points delivered (showing Planned & Unplanned on the delivered side is fine because it shows the total accepted points).  Everything that happens in the middle with points coming in and out, we don't care because we're measuring what we committed (committed after day 1 planning), vs what actually got accepted.  If I commit to 50 points, including day 1 of iteration planning and throughout the iteration I bring in 10 points, then I remove 10 points because they were either entered into the sprint in error or I thought I could do them as stretch and discovered that I really can't, with this app it shows committed as 60, when in reality, it was always 50.  If I accept 40 points in the iteration, my summary report should say 50 Committed, 40 Accepted, 10 incomplete.  That is what I'm looking for an app to do.  Now, if the same 10 points were added after day 1 of iteration, and I actually worked on them and delivered them, my baseline committed is still 50 points as of day 1 planning, and my accepted would be 60 points, showing that the team exceeded their expectations, showing improvement.

    If this app was not designed to show what I described above, are there any other suggestions that would provide what I'm describing?

    As another thought, is there a way to tweak this app so that it allows me to select if I want to see committed unplanned activity after day 1 of planning (or whatever number of days I set for planning), in my iteration or not?  This would be the ultimate option to address the issue we're encountering with this app.  I really like the app as well but can't use it due to what I described above.

    Thanks for any insight and/or direction.

    ------------------------------
    Tony Soares
    Release Train Engineer
    UnitedHealthcare
    PA
    ------------------------------



  • 38.  RE: Actual Stories Completed versus Committed Stories