Requirements

Return to Class 2

Requirements Gathering

  • Set design goals for yourself. These are the general problems that needs to be solved (such as "explain the company's business model").
  • Solidify the primary objectives of the project.
  • Understand which departments or business units may (or should) be involved as gather business requirements.
  • Determine best methods for incorporating user research.
  • Ask questions about which technologies may be involved.

Determining a project's scope

  • What is the goal of the website
  • How will the success of the site be determined?
  • Is the work done on a new site or an existing one?
  • Who will you contact with technical questions, internet provider, domain host, etc
  • Does the site need backend programming, i.e. a database, credit card processing, etc
  • Differences between Front-end Work and Back-end work
  • Do you need to collaborate with anyone on the site
  • Is the timeline realistic to get the work done?
  • Scope of Work document
  • Scope creep

Statement of Work

A statement of work (SOW) is a formal document that captures and defines your new project. All too often contractors and clients belive their is a meeting of the minds at the beginning of their relationship, when in fact ambiguities are just lying in wait.

A comprehensive SOW is your best defense and smartest way to ensure that you do not later find yourself in a courtroom arguing about the terms of your relationship.

A proposal allows you to define terms that protect both side sin the event that something changes. If the client doe snot provide you with timely access to their resources, your timeline may slip; you need to make them aware of their obligations to the project's success. If a client loses funding and kills the project—and you do not have a proposal or other form of contract in place—then you run the risk of not getting paid for the work you've already completed.

Include the following:

  • Title page
  • Revision history
  • Project overview
  • Project approach
  • Scope of work (What will be done by both parties)
  • Assumptions (Client provided)
  • Deliverables (Contractor provided)
  • Ownership and Rights
  • Additional Costs and Fees
  • Project pricing
  • Payment schedule
  • Acknowledgement and Sign off

When the client signs your proposal, they are agreeing to this arrangement, and you have a paper trail to back you up in the event of any misunderstanding.

Additional Resources: