border

History: Closing development

Preview of version: 6

First Version Prev VersionVersion Next Version Last Version

Chase bugs

Of course, get a website bug free will be a miracle.

  • Run the unit test if they are.
  • Use Website QA checklist to check website features. If too many refinements you may not want to create a case for each of them and use the issue sheet in the Website QA checklist document.

Check scope

  • Review the specifications and check step by step that everything has been done.

Push the project in production

  • Get client to sign-off on the UAT
  • Check production environment, report UAT configuration to production, install needed modules
  • Freeze the development and database changes
  • Migrate the website
  • Get client to sign-off to production

Until advanced development stage, client should not enter production data in the website as it will be difficult to proceed to an eventual change.

Provide deliverable

  • Technical documentation (to facilitate further developments)
  • User documentation
  • Training
  • website source code

Actions
Check bugs and scope with Website QA checklist
Get the client sign-off on UAT
Push project in production
Deliver the deliverable
Send closing project email template to client
Thanks your project team!


History

Advanced
Legend: v=view , s=source
Date User Edit Comment Version Action
Thu 12 of Aug., 2010 20:42 UCT System Administrator   9
Current
 v  s
Wed 11 of Aug., 2010 17:30 UCT System Administrator   8  v  s  
Wed 11 of Aug., 2010 17:12 UCT System Administrator   7  v  s  
Wed 11 of Aug., 2010 17:11 UCT System Administrator   6  v  s  
Wed 11 of Aug., 2010 17:11 UCT System Administrator   5  v  s  
Wed 11 of Aug., 2010 17:10 UCT System Administrator   4  v  s  
Wed 11 of Aug., 2010 03:03 UCT System Administrator   3  v  s  
Tue 10 of Aug., 2010 05:01 UCT System Administrator   2  v  s  
Thu 05 of Aug., 2010 11:35 UCT system created from structure 1  v  s  
border