In which Joey lightly discusses current plans to revamp the schedule for his project.
In another transitional period for the project right now. The senior staff are looking for 2-3 months of projected scheduling AND team rate of burn over a period of about a month. I'm trying to figure out exactly how to do burndown in an agile/waterfall hybrid situation, and I'm still not entirely sure how to go about it.
Burndown is basically just rate of task completion. I don't have to do it on an individual basis (although I probably will so that the production team can determine where we're getting leads and lags) so I'm thinking that I'll get ideal day estimates for tasks/stories and schedule out monthly... sprints? I don't think I can call them sprints per se... is there another word for a work period after which you reasses?
The ideal day estimates provide a baseline velocity. Any deviation from that baseline becomes an adjusted velocity, and hopefully after another month or so we'll be able to do better projections.
Again, it's too bad we didn't have the opportunity to develop a production plan at the get-go. All of our data so far is scattered and we're going to have to make do with what we've got.
You May Also Like
