This action might not be possible to undo. Are you sure you want to continue?
Development Item Database
A database of development work including bugs, tasks and projects. This should include: • Item Type • Priority • Assigned Developer Assigned Developer • Due Date This database should be populated from business requests, customer requests, bugs, etc.
Environments & Deployment
Requirements Requirements Design & Definition
Development D l t
The Development Environment is where the developers do their coding. This is their place to run their applications and other li ti d th tools.
Regular Dev Regular Dev Meetings
Pl lan & Des sign
Conduct regular meetings with the business mgmt, product development & technology. Items to discuss: • Accomplishments since previous meetings previous meetings • Development Issues • Prioritization of development • Testing & Deployment Schedules
The business and product development needs to work together to develop requirements for the development work. At a high level requirements include level requirements include what the program needs to do, what type of data it needs roughly how it should look.
The Test Environment is where the developers move their code to allow h i d ll for QA testing. This environment should mimic production as much as possible.
Develop & Deplo oy
Deployment of code from Test to Production
Once the deployment to production has been completed all necessary stakeholders should be stakeholders should be alerted that the deployment is tested and completed. Once the testers and business have signed off on the code a deployment time is selected. For non urgent deployments For non urgent deployments this should be at lulls in the product use. Prior to deployment a full backup of production should be made. After the code is deployed test scripts should be completed on production.
QA Testing & Test Scripts
Coding & Development
Once the developers are comfortable their work is done the code is deployed to the test environment. In the test environment In conjunction the product mgr should provide test scripts for the testers. These scripts are very detailed directions on what to test and how to do it. If issues are found report back to developers and repeat previous step and this step till correct.
Once the teams have agreed on development work and provided the requirements to the requirements to the developers, the development team is off to the races to get the project done..
The Production Environment is your live technology, where your customers access your tools and products. Prior to moving code from to moving code from Test to Production, a full backup should be made of production and rollback plans in place.
The Backup Th B k Environment is where you keep copies of production code, data, etc. Keep multiple copies at all times. Make sure you know Make sure you know how to use backup is production has an error.
© 2009 Zelkova Ventures