You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We know when Features should be completed according to the forecast, thus we could visualize this in a "timeline".
We can show this together with the uncertainty (e.g. color the time from 70-95 differently) in a chart.
Milestones can be visualized as vertical lines too.
This could be useful if we need to produce some charts for things like Release Planning and we don't want to rely on spreadsheets.
Question is: When should the "line" start for a feature. Is everything already started or how do we figure this out.
An extension (a separate issue, just here as food for thought) would be that we include the teams Feature WIP, and then we know when the teams get started with the work based on this. This would be great because it would allow you to see when you should be ready with the feature to not block the flow of feature delivery. It might also be a bit of work to get the data in place, as right now we just store a single forecast per feature (the one of the team that takes "the longest" for this to complete). If we store both we probably could create such a chart. --> Handled in #52
We know when Features should be completed according to the forecast, thus we could visualize this in a "timeline".
We can show this together with the uncertainty (e.g. color the time from 70-95 differently) in a chart.
Milestones can be visualized as vertical lines too.
This could be useful if we need to produce some charts for things like Release Planning and we don't want to rely on spreadsheets.
Question is: When should the "line" start for a feature. Is everything already started or how do we figure this out.
An extension (a separate issue, just here as food for thought) would be that we include the teams Feature WIP, and then we know when the teams get started with the work based on this. This would be great because it would allow you to see when you should be ready with the feature to not block the flow of feature delivery. It might also be a bit of work to get the data in place, as right now we just store a single forecast per feature (the one of the team that takes "the longest" for this to complete). If we store both we probably could create such a chart. --> Handled in #52
Potential Chart Libs:
The text was updated successfully, but these errors were encountered: