We have budget changing per Date though the Features, Bug, PBI and Task are scheduled, obviously, per Iteration / Sprint.
Though your support to change a budget per Work Item and even Work Log record is excellent, we have to take some effort to do this.
We have Features assigned to Iterations. Our best practice is to assign Budget per Feature
Since Features may not be complete per Date, but per Iteration, we would need to Duplicate the Feature and it Children and make sure Dev and QA stop working on Feature 1 - Iteration 1 + Budget 1 and start working on Feature 2 - Iteration 1 - Budget 2.
Of course, this is doable. But labor intensive.
Why not change Budget to new Budget? A: all previously entered Work Logs are moved over to new Budget. - also a valid use case, I understand.
Preferred method:
When Assigning Budget 2 to Work Item:
[x] keep older work logs to Budget 1 (or something like until date dd.mmm.yy)
almost similar to this post but different https://support.7pace.com/hc/en-us/community/posts/360005373426-Feature-Request-for-Budget-over-Dates-instead-of-Iterations?input_string=Budget%20changes%20per%20CutOver%20date
Our ADO ref: HELP TICKET 610514
-
Hi Hubert,
thank you for your message!
I would love to understand a bit more about your use-case. Often companies tie budgets to product initiatives which means that they are also tied to releases, and therefore iterations. I am assuming that this is not the case for you. The customer in the other thread you linked explained that he buys monthly contracts of developer hours and as a result his Iteration dates do not follow his contract dates. Is this the same scenario you are facing?
Also, could you confirm if the following statement is correct - currently you 'artificially' close a budget at a given date by closing the associated feature, and then you duplicate all work items and assign them to a new feature / and budget to track remaining work. Correct?
Regards,
Andrea
Product Owner - www.7pace.com -
Hi Andrea, thanks for your reply
1. We have those scenarios too. And this is not our main issue though
2. I can best explain with some example data below (hoping the table ends up nicely):
Batch 1
- Budgets 2101 2102 2103 applicable for month 1-4
-- Batch 1-Features are not fully complete yet
-- Iteration does not End April/30 - Start May/1
Batch 2
- Budgets 2111 2112 2113 applicable for month 5-8
-- Batch 1-Features to be completed on these budgets
-- as well as Batch 2-features
These are R&D projects running for 3 years now and some almost complete and near to be published.
Most likely we will have new projects with same budget characteristics next year and after as wellBudget Month 1 2 3 4 5 [Budget 2101] 730 749 900 896 239 [Budget 2102] 437 348 353 172 9 [Budget 2103] 225 186 299 334 11 [Budget 2111] 0 0 0 0 140 [Budget 2112] 0 0 0 0 21 [Budget 2113] 0 0 0 0 5 Current WoW: manually change Budget coder per PBI or Task while completing
Work around could be to create distinctive Iterations for these projects, but that would really complicate setting up Sprints boards for our 4 teams working on these Sprints and the 25 or more features we are working on ...
Regards Hubert
DevOps and QA
Please sign in to leave a comment.
Comments
2 comments