Discussion Locked

Quoting for system development projects

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I have been asked to assess a quote for a system development project and there's not much to go on:
- project management $x
- system development $y

I would expect to see at least a breakdown of number of resources at $ per unit of time and probably split across:
- project management
- requirements analysis
- system design
- database design
- development
- validation
- implementation

What sort of detail do others give/expect out there?

6 replies

by dbe10

Terry I would add to your list the following:
Under Development add Testing

Under Implementation add User Training,
Setup in Production Environment, Pilot Run Support, Post Implementation Support and Project Closure

by realgem

As well as breaking down by unit of time, you should consider a breakdown by deliverable. That way, you'll know what exactly all that Requirements Analysis is in aid of. How can you assess a quote if you don't know what they're going to produce? Knowing the deliverables also makes it easier to deal with contract administration and billing.

These should be covered in other sections, but the quote should also cover billing periods, change management, dispute resolution, etc.

By the way, if it's a fixed price contract you might not get a lot of response in requesting more detail.

This discussion is closed to new replies.