Completely agree. This is very much needed. My company has THOUSANDS of
fields, many that are nearly identical, but can't be re-used because of
existing limitations. Each instance of a form should be able to mask the
display label and values for existing fields appropriate to the work
group. In addition to a Unique Display label, each instance of a radio
button or multi-select fields should have its own masked list of values
to display. For example, the admin might need an existing "Region"
Great to now have agile work options, but to actually manage agile teams
we need improved reporting. For example, a Cumulative Flow Diagram (CFD)
will help measure lead time (time from request to completion), cycle
time (actual start to completion) as well as the number of
work-in-progress items in various statuses. This way we can visualize
the stability of our workflow and find where improvement is needed.
Here's a CFD chart borrowed from the web: Other types of valuable agile
reports can be: ...
Totally agree. Very limiting. Each groups should be able to have its own
custom agile statuses. Doesn't make any sense that this would limited.
Frustrating that there's no apparent reason to have it this way.
Agreed.Depending on how a business operates, the business case and
collected custom data should also be convertible into a PROGRAM. In my
use case, projects are tactical executions that are more or less
pre-approved once the larger program is authorized. The current way
Business Case is deployed prevents me from making use of an excellent