...
You may have one or many delivery systems in your organisation. A delivery system may have one or many teams participating in it. You could start to measure work when a request is received from a customer, or perhaps you reduce the scope of your measurements and start once development begins. Regardless of your decisions, there are some factors you should consider.
Include all of the work in the system
Deciding whether to initiate measurements at the first or fifth step of your value stream hinges on the objectives of your measurements and your team's comfort level with flow concepts. Ultimately, the decision rests with you. The same principle applies when determining whether to analyze a month's worth of data or six months' worth. The choice is yours.
...
| Info |
|---|
When gathering data about your delivery system, it is crucial to ensure that you capture all the work that has been executed within the system. |
Don’t double count
By default, Jira includes issue types that serve as parent issues for other issue types. For instance, an Epic typically represents a substantial body of work that is divided into Stories or Tasks. An Epic will have both a start date and an end date; however, it does not directly represent work itself. Instead, it acts as a placeholder for its child issues, which provide a more accurate depiction of the actual work involved.
...