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
------------------------------
Original Message:
Sent: 05-12-2020 12:23 PM
From: Terry Ginzburg
Subject: Actual Stories Completed versus Committed Stories
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
Original Message:
Sent: 05-12-2020 11:22 AM
From: Nik Antonelli
Subject: Actual Stories Completed versus Committed Stories
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
Original Message:
Sent: 05-11-2020 04:45 PM
From: Erin Vargas
Subject: Actual Stories Completed versus Committed Stories
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
Original Message:
Sent: 04-30-2020 04:42 AM
From: Nik Antonelli
Subject: Actual Stories Completed versus Committed Stories
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
Original Message:
Sent: 04-29-2020 04:11 PM
From: Chris Kennedy
Subject: Actual Stories Completed versus Committed Stories
Nik,
I just copy/pasted in the March 27th version of the code you pointed me to: https://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
Original Message:
Sent: 02-25-2020 01:48 AM
From: Nik Antonelli
Subject: Actual Stories Completed versus Committed Stories
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
Original Message:
Sent: 02-24-2020 10:30 PM
From: Chris Kennedy
Subject: Actual Stories Completed versus Committed Stories
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
Original Message:
Sent: 01-28-2020 10:48 AM
From: Nik Antonelli
Subject: Actual Stories Completed versus Committed Stories
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
Original Message:
Sent: 01-28-2020 09:03 AM
From: Eda Kuchta
Subject: Actual Stories Completed versus Committed Stories
I totally agree.It will be great if this app also display the story points.
Original Message:
Sent: 01-23-2020 02:49 PM
From: Niveditha Gadamchetty
Subject: Actual Stories Completed versus Committed Stories
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
Original Message:
Sent: 01-17-2020 09:38 AM
From: Nik Antonelli
Subject: Actual Stories Completed versus Committed Stories
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
Original Message:
Sent: 01-17-2020 09:33 AM
From: Stephen Grasso
Subject: Actual Stories Completed versus Committed Stories
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
Original Message:
Sent: 12-08-2015 01:58 PM
From: Skowronek
Subject: Actual Stories Completed versus Committed Stories
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?