We have a charter to build a product in 6 months. I'll preface this by saying that my manager wants us to use waterfall, even though our development process is agile.
With that said, I have been asked to create a 6 month project plan that outlines milestone dates and a list of tasks & dates to monitor project progress. I've never done a detailed project plan for more than 2 months in Agile, so I need everyone's help :)
Approach 1: List out all the project tasks and use guesstimates on work effort per task and present a linear path to completion. This is obviously risky since our estimates can be completely off and risk the timeline. I suppose we can de-risk by doubling our estimate #s?
Approach 2: Group tasks into sprints, and follow an 'x' week sprint cadence. Each sprint will have a breakdown of all the tasks we have to do until we get to 6 months. Unfortunately this still suffers risk of missing the deadline if our estimates our off...