how 2 scope a project
- Started
- Last post
- 4 Responses
- trooperbill
anyone got any tips or a checklist of how to technically scope a project when sat in front of a client? weve been burned for the last 12 months for not hammering down a spec and want to remedy this in 06
- honest0
what kind of project? web? print?
- trooperbill0
web development
- t3chn0ph0b30
Depends on the size of the project, and the size of your company etc.
you don't want to spend 3 weeks writing a functional spec for a project thats only going to bring in 2k
essentially you need to
* Define Functionality
* Define Technical Structure
* Define Dependancies
* Define Deliverables
* Define any Legal Requirements
* Define Deadlines
* Define Penalties
* Define ChargesGet everything signed by both parties
Are you going to commit to say 2 weeks of requirements capture if there's a chance the client could walk away?
Do you include a consultancy fee so they can take your req/cap analysis to another developer or is it 'not for disclosure to third party'...
...good luck!
- tkmeister0
also, you may find this useful.