Planning through the lifecycle

Question 1

Planning Pre-project

Answer 1

Planned at Programme/portfolio level and will determine whether it’s feasibility will be assessed

Question 2

Feasibility phase

Answer 2

• High level investigation
• Small number of requirements highlighted, solution is only an outline
• Guess approx size and duration of the project
• Delivery plan will describe the Foundations Phase, high level of the first increment and possibly dates for future project increments

Question 3

Foundations phase

Answer 3

• high level requirements are agreed and prioritised using MoSCoW
• Delivery plan estimates are more accurate
• timeboxes for the first project increment are created
• resources agreed
• define the approaches to be used for developing and controlling the development of the solution
• agree strategy for deployment
• plan is baselined at end foundations and first project increment end date agreed
• Foundations can be revisited at the end of each project increment to check project viability, firm up plans for that increment

Question 4

Evolutionary development - Timeboxes

Answer 4

• SDT produce timebox plans based on objectives and outcomes agreed at the Timebox kickoff
• Timebox duration is agreed at kickoff
• Structured Timebox: schedule control points, kick off, three review sand close out
• review objectives, timelines, acceptance criteria and resource availability
• highlight known dependencies
• phases: investigation, refinement, consolidation
• Timebox review record: can be an email of what was agreed

Question 5

Evolutionary development - planning for deployment

Answer 5

• planning involves everything needed to transition the solution into live operational use
• Delivery plan updated as these items become clear
• eg: training, rooms, resources etc