V3DA hub software development service estimator tool

What's your full name? *

Your role?

Company name? *

Department name?

Company Email *

Phone (if you'd like to receive a follow up call)

Size of target user base (employees+clients if both are users): *

"Blocks of effort". Based on agile, approximately how many stories* or 'blocks' are required? *

Desired no. of months from discovery to launch *

3 - 4 months

5 - 9 months

10 - 16+ months

Budget Estimate (CAD $):

I would like to receive a formal quote? *

Yes

If 'yes', please provide any special procurement details ex. RFP number, RFP submission site, date of expiry etc.

*What is a story?

A user story is the smallest unit of work in an agile framework. It’s an end goal, not a feature, expressed from the software user’s perspective.  The purpose of a user story is to articulate how a piece of work will deliver a particular value back to the customer. Note that "customers" don't have to be external end-users in the traditional sense, they can also be internal customers or colleagues within your organization who depend on your team.  User stories are a few sentences in simple language that outline the desired outcome. They don't go into detail. Requirements are added later, once agreed upon by the team. 

For example, 
'In my form, when I click on the submit button, the fields will be validated, contents submitted, followed by either displaying a confirmation page or a list of errors'. 

A medium to large-sized enterprise wishing to create a corporate portal, intranet or web site could have anywhere from 300 to 1000 stories or more. 300-400 stories would generally be considered a 'minimum viable product' in many cases, whereas the top end number could be closer to a more complete product. 

Again, these are just order of magnitude numbers for estimation purposes only. Your situation could be very different, higher or lower.