Scrum Developer Count Estimator

What to Do:
1. Update values, 2. Press Go, 3. See the number of Developers required.

Variable	Entry	Comment:
Velocity:	%	(50% means Devs contribute code 20hrs/wk, and 20hrs is overhead like meetings, research, etc...
Hrs:	hrs	(hours of work you need to build features. Ex. it will take 80hrs to make X, and 16hrs for Y, so the Total = 96hrs)
Start Date:		Includes this day as a work day.
End Date:		Desired end date. Includes this day as a work day.
Developers you will need:		0

Notes:

Calculator rounds the start date to the following Monday, if weekend day was chosen.
Calculator rounds the end date to the previous Friday, if weekend day was chosen.
"Velocity" is also called "Capacity"
70% (28 productive hrs/week) Velocity is a good estimate, if your team is senior, and they just have a few meetings each week.
50% (20 productive hrs/week) Velocity is a good estimate, if this is the first time the team is working together, they're on a significant learning curve, or they get randomized regularly.
Remember your Sprint demo and retrospective date is the day after the End Date listed above. Don't sell yourself short one day.
Need to calculate the End Date with a fixed number of Devs instead? go here