Forums: Discussions for entrepreneurs and small business.

Hi Manuel

I recommend adding two sections to your project plan in addition to your layout:

1.  A list of user requirements.   Describe your requirements in detail in order to ensure that you get what you need on the first pass.  Rework is no fun.
   
2. A list of tests.  For your testing, convert your user requirements to specific tests.  For instance, let`s say one user requirement is that only members of a given role are allowed to access a page.  In the test plan you design a test where a user meeting the requirement is granted access, and another user not meeting the requirement is denied access.
   

By documenting the expected results of the test, and linking those tests to specific user requirements, you set clear expectations for your developers.  This helps ensure that you get what you need, helps them scope the project correctly, keeps you on budget, and reduces schedule impact due to rework.

As for the turn over package, I would require that the package be tested in a development environment and then specific tests be executed to prove that it works correctly in production.

As for ownership of intellectual property, set up a work for hire contract and require it to be signed to start the project.

Be very careful about who you hire to create your website. There are many web developers out their claiming to be "professionals" From experience (I`m sorry to say) I can tell you that hiring  unprofessional web developers will cost you a lot of headaches, frustration, time & extra money to fix their half completed sloppy job. So be careful. Ask to see their work, contact some of their past clients and put everything in writing.  

 

 

But if you’re looking for a referral to a good web developer i could point you in the right direction send me a PM 

 

 

Sergio

-------------------------

Kansas Direct mail Service & Kansas Business Netwok