I totally agree that the 2016 update resulted in changes that are not understood, were communicated without enough notice, and likely results in incomplete projects being changed. To that end we are working on a few issues.
When we made the 2016 updates, we made a number of scope changes, that were:[list]
[*]changes in scope names
[*]changes in scope groupings
[*]and a limited number of new scope items.
[/list]We had not anticipated in the tool, the nature of these changes, and the impact they would have on maintaining the capacity to calculate multiple releases of the software with different Scope items and efforts.
At the same time as this release, we made a number of changes that resulted in efforts being calculated at a reduced level, to overcome the claim by management that we are doing BOZO quotes. We had looked carefully at efforts to see where we could reduce them by default. A major area was in the Data Load and CRP Testing Areas where after the first CRP we assumed that the Customer could do the work, and unless we adjusted the Assumptions (also updated) state that the customer will do the work.
A communication went out to all users to this affect, but not with much warning, since we were two months behind schedule. THE BIGGEST ISSUE HERE is that since changes could not be version specific, if anyone updated the calculation, it would use the new rules and result in slightly different calculations In effect, being updated using the lower efforts to address BOZO quotes.
CURRENTLY: Projects with IT are in place to change the calculator to allow multiple versions so that when a project was started on Version 2015, when 2016 is released, it should not change the 2015 project calculations.