Skip to Main Content
Status Future consideration
Created by Guest
Created on Mar 13, 2020

Control change to definition of a release

Control who can change a release definition. a. At all. b. Per release.

Minimum need - ability to lock a Release scope.

I'd love to be in that space where this tool is central to everyone's perspective, and the tool provides all the ways necessary to control the view people work with, but neither is ever going to be true.

What I don't want and can't afford is to spend time 'monitoring' and then fixing things people do that they shouldn't.

This has come up in other areas too, but more generally, discriminated changes that impact scope of a release, or the identification of a release are really obviously key things that investor stakeholders see, they are external not internal descriptors, and these should change only under control. This is the case whatever the condition of the release - whether scoping or finalised. It's chaos if things are changed at any point in development of a release scope, it's disaster if it gets changed after without being seen.

Given that it seems not to be possible either to lock a release scope, I need to control who can change the release definition.

This is not the same as controlling the status of features, although really I'd also like to see it highlighted where things have changed since a benchmark on a release - which is a separate distinct issue. So I don't mind if this scope is not to include who changes the fields within a Feature.

Change control, change visibility and management are serious flaws in the product right now. These are well established key concerns of Systems Engineering, and are right in front of key stakeholders. The entire premise of the product approach is 'optimistic', in a world where that generally doesn't work out.

This is reflected in the category list below - there's nothing appropriate to pick. Check out Configuration Management and Control maybe.

This is such a serious omission that despite the positives of the product, this has to be an included concern in making recommendation to others. I'd just look like an idiot for not mentioning it.

  • Attach files