Decades of web development projects have taught us that best practices are key to ensure project success and facilitate support in the long run. Here are the processes and tools that we have developed over the years:

Our Project Management Approach

  • A dedicated project manager facilitates collaboration between all parties
  • A Living SpecBook or requirement repository is automatically and continuously kept up-to-date
  • A multi-directional Traceability Matrix is at the heart of our engineering operations so we can check progress in real-time
  • Frequent “show and shares” are scheduled with project stakeholders
  • Weekly Pulse Meetings™ take place with project stakeholders to review budget and overall progress as well as “blockers”

Thoughtful Software Development:

  • Source control management and configuration management are used in all development projects
  • A Code Review is scheduled weekly within the Engineering group
  • A consistent series of tools and platforms is used across the team
  • Testing and Continuous Integration is part of the process
  • Code Consistency is maintained via CI
  • Engineering standup meetings take place daily
  • Development documentation is continuously updated
  • Code comments are used effectively

Coordinated Deployment:

Releases are first performed on a sandbox environment to which our clients have access. When parallel work needs to happen, several branches can be set up and multiple instances are available for testing. Once the deliverables have been approved in a Staging/UAT environment, we  coordinate a release/deployment of the code and content to the live Production environment.

Comprehensive Testing:

Additional testing protocols are leveraged to develop the project and report defects:

Structured Testing: As a team member completes a task on the project, the QA team verifies that the task is implemented correctly per specification and defect-free. The structured testing is delivered to the QA team in the form of tickets. Test Cases are documented for future reference. Traceability is ensured by linking each issue found to a related technical and/or functional requirement.

Exploratory Testing: As structured test cases are developed, members of the QA team are given freedom to report defects and questions that go against specifications. In this method, when changes are introduced, the QA team has well-rounded knowledge of the product and is alert to impacts/consequences of changes.

Infrastructure Management:

  • Source control management and configuration management are used in all DevOps orchestration projects
  • Data Center Infrastructure Management (DCIM) is part of our infrastructure management approach
  • Analytics (Grafana/Kibana) is run diligently
  • Alerting is set up with intelligent filtering and escalation thresholds

Strong Security Standards

We maintain an internal Security Policy document which engineers and all other employees are required to review periodically and abide by at all times. This includes the engineering team’s approach to common security vulnerabilities in software and infrastructure such as the OWASP Top 10. A full copy of our Security Policy can be provided upon request in conjunction with an executed NDA.

Thanks for filling out the form! A Six Feet Up representative will be in contact with you soon.

Have a question? Want to connect with us?