You have all the specifications signed-off by your client, you know the deadline and your team is ready to undertake coding, so cool!

It's perhaps a good idea to set up the specifications somewhere in a single place where both client and developers can see it (online platform, website...) as they might change during the development.

Create a road-map

Define "checkpoints" throughout the project and define when they need to happen in a calendar.
Everyone should be able to consult this and so get aware of the influence of their work with the other stakeholder. You might want to use the planning included in your quote.

Set up the environment

  • Create the project in your versioning system (with the usual convention documented in developer documentation) by creating a new case in the Sysadmin bugtracker project or, if you do it yourself, you should have some automatic scripts to do that for you (documented in your internal bugtracker project),
  • Setup a UAT platform (and maybe start the process of production installation as well),
  • Write the project documentation (according to technical project documentation template) in your bugtracker including all information needed by developers with a link to the specifications.

Make the resources working

In a website construction, there is usually four main kind of jobs, sysadmin, development, design and design integration.
Identify and break down the tasks, enter them in your bugtracker and assign developers and designers to it.

  • Priority
  • Status (=new)
  • Due date
  • Invoicing type (for contractor)
  • Estimated time
  • The task and what are the deliverable (documentation, code, tests, how to run the code...)

Publish the specifications.
Set up development environment and include project documentation.
Create & assign the cases in your bugtracker.

Page last modified on Wednesday 11 of August, 2010 12:17:54 UCT

Post new comment

Click for Help
BoldItalicUnderlineStrikethroughExternal Link
Anti-Bot verification code: Random Image
Post new comment