Budget & Timeline Meeting
Verify Budget and Timeline
Discuss the available budget for the project. This is going to dictate how many story points you can complete.
Discuss the timeline for the project. This is going to dictate how many man hours you are going to need to complete the project. The more stories and less time the more people are going to be needed to complete it.
A starting rule of thumb I use is one full time employee can complete 20 story points in a two week sprint. This number can go up or down based on the worker, and the average can go up and down based on the teams ability to complete story points.
Review "Out of Scope" Items
Take a little time to call out any specifics that a worker might assume is part of this project or infer from a user story that is not within the scope of the project.
Review User Stories, Estimates, and Epics
Review the items you have selected for this project and make sure you have the expertise, manpower, and money to complete them.
If you do not, you may need to remove an epic or number of user stories that will need to be completed at a later date.
Propose Sprint Size and Lengths
Based on your user stories, plan out how many and what size sprints you are going to conduct.
- Small Sprint - 1 FTE for 2 Weeks (Can do 20 story points)
- Medium Sprint - 2 FTE for 2 Weeks (Can do 40 story points)
- Large Sprint - 3 FTE for 2 Weeks (Can do 60 story points)
Example Work Schedule:
- Design - 1 Small Sprint
- Development - 2 Medium Sprints
- Content Migration - 1 Small Sprint
- Hardening Sprint - 1 Small Sprint
So in total the project will take you 10 weeks, and just for example purposes let's say an FTE costs you $2,000/wk, and will run you $28,000.
Get It On the Calendar and Go