ITIL - Good Practices - Database Development

27/09/2015 15:07

Basically, this method was used to sort the deficiencies out in my team to organize the tasks and become the processes more efficient.

Even though this process become harder to implement the documentation, it is very important to be clear for the team, reduce some doubts that can happen during the development and prevent any problems after
roll up.


Simply we have to follow these procedures:

1º - TRELLO WORKFLOW: This clouded software is essential to organize the tasks required by users

For further information: www.trello.com


2º - FUNCTIONAL REQUIREMENTS: Gathering the functional and business information about the
new solution and functionalities, this process has to be filled up with
information that were collected after interview with the users that requested
the changes or tweaks.   

This is a questionnaire that has to be done with the user that required the task, Usually this FR is implemented on Trello, as far as the scripts, emails , images... keeping the information centralized, clear and with whole  historical.This is a questionnaire that has to done with the user that required the taskThis is a reserch that has to done with the requirer. Usually this FR is implemented on Trello, as far as the scripts, emails , images... keeping the information centralized and with whole process and historical. 


3º - TECHNICAL REQUIREMENTS: ACTION PLAN:  This process will give to internal technical team enough information and technically to follow the development.


This Action Plan was created in Share Point.

4º  - CHANGE REQUEST: After the development be
tested and approved by peer, the change request will be filled up with details
that will provide the date to be applied, relatives process that will ensure in
live to be successfully done and roll back in case of problem.


This Action Plan was created in Share Point.