jbrunton / agileplanning-io-forecasting-legacy Goto Github PK

• Form at the top
• Backlog on left
• Forecasts on right

Plot:

• Story points
• Issues closed
• Epics closed

Some/all of these will require computing a rolling average, potentially derived by Little's Law (Th = WIP/CT).

• Errors
• Simulator needs to respect filter

Sync all issues including key and summary.

Mark epics as completed based on "Epic Status" field:

• Completed date should be set IFF Epic Status is Done and all stories are completed.

See:
http://blog.scottlogic.com/2014/08/26/two-line-components-for-d3-charts.html
http://blog.scottlogic.com/2014/08/28/bollinger.html

Below the point if the point is in top half of graph, above otherwise.

Simplest model: merely divide time by two (assumes smooth flow of work; that as many are almost completed as almost started).

More sophisticated: monte carlo simulation picking issues from those with cycle times >= those in progress, forecasting based on expected time remaining.

Likely best implementation:

• If cursor within X pixels of data point, show details for that
• Otherwise, show rolling mean and stddev for both WIP and cycle time

For outliers. Example query:

completed: 16 Jun 2014 - 20 Dec 2014, 5 Jan 2015 - 16 Jun 2015; cycle_time: 0 - 150d

Display target dates based on this

For issues and epics

• Add filter field
• Filter dates on server

Below the point if the point is in top half of graph, above otherwise.

• List epics in cycle time details
• Show date, averages and std devs in WIP details

With fields for: domain, board_id, name.

• find nearest WIP point according to bisector
• display unless closest CT point within given (eg 10px) radius

Try inserting issues in a single transaction.

Add profiling to determine performance % increase.

• only size those with a specified size
• make it easy to view those without a size

Update forecasts with ajax call on input change events.

• Make it a .md file
• Add a description of the project
• Add CI and code quality badges

E.g. MOB-1160

• round cycle time to 2 sig figs
• display ticket summary for CT

This affects the simulator and the wip endpoint.

Create a method on WipHistory to return histories by date, including for dates with none.

This is a chance to fix the fact that wip histories are currently only available between started/completed events (i.e. exclusive of in-progress but unfinished epics).

• modal tip
• all in-progress epics for WIP points
• epic details (incl start, complete dates) for CT

Pick from all epic cycle times for unsized epics