1. Monitoring and error reporting tools
At SeeD we implement a set of tools that allow monitoring of development and the final product from various areas:
1.1. Development
-
Coder (Módulo de Drupal)
-
W3C Validator
-
Devel (Módulo de Drupal)
-
Page Speed / YSlow / Firebug / Web Developer Extension
-
Drush / Drupal Console
1.2. Performance
-
http://pingdomtools.com
-
XHProf
-
Jmeter
-
Apache Bench
1.3. Version control and DevOps
-
Git + Github
-
Jenkins
-
Docker
1.4. Security
-
Hacked (Módulo de Drupal)
-
Security Review (Drupal Module)
-
DPScan : Drupal Vulnerability Scanner
-
Vuln
2. Code documentation
At Seed we follow drupal.org's recommendation to document inline code using the standard.
3. Request for version control of deliverables.
We perform version control using GIT as a tool, to keep track of each change made to the tool in the development process.
4. Work schedules, deliverables and delivery dates.
The project is managed with a schedule whose timeline will be negotiated at the beginning of the project; it will have clearly defined iterations with equally clear deliverables and a change control document is managed that reflects the client's additional requests, whether or not these have an impact on costs with the respective impact on the previously agreed times. To ensure proper monitoring, we propose weekly meetings with the project team.
5. Communication channel
The communication channel will be defined at the start of the project. Below we name the positions and their levels of relationship with the project:
-
Project Manager - Primer Nivel.
-
Production Director - Second Level.
-
Commercial Director - Second Level.
-
IT Director - Third Level.
-
Development Director - Third Level.
-
Design Director - Third Level.
6. Change control
The change control procedure will be done through a document that we will share with the client to keep track of developments that go out of scope and with this generate the process of additions to the contract.