When I'm planning a project, as part of the planning process I like to create the tickets or the pieces of work. For me the most important part at this point is specifying the dependencies between these. Every ticketing system I've worked with is horrible at this, and I don't understand why.
What make the most sense is a UI like a diagramming tool. Each ticket is a box that you can drag around, and you can make connections between. You can create new tickets directly on the canvas.
Once you have these connections, you'll want to turn them into a schedule. It seems that most sensible way to do this is to have a set of timelines going from left to right, one for each person working on the project. You assign work by grabbing tickets and dragging them onto the timelines.
In this system, time estimates are marked in t-shirt sizes. The system maps current velocity to available work hours, and then uses this to determine the length of each ticket on the timelines. In addition, the tickets will shift into the future until they follow their pre-requisites' completion, showing blank spaces on the timelines.
The timelines only allow 80% capacity to be scheduled.
And from this we can produce a gantt chart.
Comments
Post a Comment