Software Development Policy
Policy Statement
This policy provides employees with the guidelines regarding the processes and procedures involved in development of software (web based or desktop based) for use by the company employees in direct relation to the business purposes of the company. Employees who need specific software developed to assist in execution of duties are personally responsible to ensure that these guidelines are followed.
Application
This policy applies to all [Company name] employees who wish to have software developed to support them in the course of executing their duties on behalf of the Company.
Procedure
1. Any employee (hereinafter referred to as "client") who requires development of software will be required to complete a Software Requirements Specifications (SRS) Form. 2. In situations where a client needs changes done to a specific module, a Change Request Form will need to be filled, reviewed and approved. 3. The client is required to state and validate need for such development in regards to existing business processes. 4. For new Software development, the client requesting for development of the same will become the owner of the system in question and will be responsible for managing the system once developed. 5. The owner of the system thus developed will become responsible for the content to be availed in the completed system. 6. Accuracy of the content thus created is the responsibility of the owner of the system. 7. A great deal of effort will be undertaken to ensure that system owners are empowered to manage their own content through use of Content Management Systems (CMS). 8. Upon submission of requirements, a developer will be assigned to handle the system thus requested. This will be based on several factors including but not limited to current projects being undertaken, availability of developers, availability of resources, prioritization of new and existing development, satisfactory submission of requirements, signoff for start of project development (electronic or otherwise). 9. In circumstances where the client needs assistance in creation of requirements, assistance will be provided depending on availability of resources. 10. Requirements should be stated to specific details and in all clarity possible. Failure to fully detail requirements will slow down project completion. Clients are strongly advised to make use of existing material that closely or fully describes the problem to be solved. This does not however negate the need to fill out the SRS form. 11. The SRS form will be the benchmark to gauge project tracking status and completion. 12. The client will be charged with the responsibility of tracking project status through a web based tool - To be provided upon project acceptance. 13. Upon a project reaching beta phase stage, the client will be charged with the responsibility of beta testing and either approving the development as complete or filling out a Change Request Form where necessary prior to release of the finalized software. 14. Upon project completion, the client is required to fill out a Software Acceptance Form (SAF). 15. Please note that the minimum turnaround time for project completion is pegged at 72 hours upon acceptance of satisfactory SRS. Please submit your requirements early enough to avoid disappointments.
16. Only in "extremely urgent" situations will the previously mentioned procedure (15) be overridden. This will be upon critical analysis of the existing problem. 17. In situations where a request for submission of software development requirements has been placed, a specified deadline for submission of the same shall be strictly adhered to. Any late submissions shall not be considered for the specified development cycle. 18. The Software Development manager reserves the right to decline uptake of a project that does not conform to the spelt out procedures or is in conflict with existing business processes and policies.