Typical Project Engagement

Each Project is different, but here’s what you might expect form a typical engagement.

Project Initiation

  • Understand customer requirements
  • Understand predicted capacity and availability requirements
  • Scope out the project
  • Agree project time lines, requirements and expectations.
  • Provide design documents, recommended tooling and architecture
  • Provide requirements, such as source code access

Infrastructure

  • Write build scripts to create infrastructure and hosts
  • Build out infrastructure in a development/test environment
  • Share environment with team and discuss, modifying or clarifying the design as required

Hosts and Services

  • Create scripts to configure hosts
  • Create any scripts requirement to synchronise code, build out packages and backup data
  • Integrate services into the development/test environment and show end-to-end functionality
  • Share environment with team and discuss, modifying or clarifying the design as required
  • Build out pipeline as required for automated deployments

Development and Test Phase

  • Create the development/test environments for the development teams, making changes as required
  • Document usage of build pipeline and tools sets so that developers and operations staff can manage the deployment pipeline as required
  • Help teams produce and run testing
  • Integrate testing into the deployment pipeline

Build Environments

  • Create further environments, such as staging and production
  • Expand the deployment pipeline to manage the new environments
  • Hand over the management of the environments as required

Application Hardening and Tuning

  • Work with the teams to run non-functional tests (such as performance and security testing)
  • Tune the application to meet non-functional requirements
  • Create suitable monitoring and alerts, agreeing escalation policies and testing these out

Handover

  • Work with internal teams to ensure they are able to use and maintain the system
  • Run internal training as required
  • Clarify and test the support model, either hand-over or managed by Zenly

 

 

 

 

 

 

 

Comments are closed