at ThoughtWorks ▸ Head of Technology at ThoughtWorks Singapore, 2012 - 2015 ▸ Technology strategy and leadership at product companies ▸ Practicing and teaching Continuous Delivery for ~ 10 years ▸ Languages that I find interesting: Clojure and Rust (watch this space)
DEVELOPMENT TESTING INTEGRATION UAT QA RELEASE AND OPERATIONS CENTRALISED QA IT OPERATIONS ‘AGILE’ TEAMS PMO + FINANCE The fuzzy front end The last mile
ADDRESS CUSTOMER - ADDRESS ORDER - ADDRESS CUSTOMER - ADDRESS CUSTOMER - ADDRESS USE ORDER.ADRESS USE ORDER.ADRESS USE CUSTOMER. ADDRESS USE CUSTOMER. ADDRESS
& compliance Testing Data management Level 3 (Optimising) Continual improvement and optimisation of IaC based on evolving industry standards Continuous improvement of tests at various levels Zero-downtime provisioning of infrastructure Ability to automatically roll back Changes Infrastructure is self-healing, self- configurable, and self-optimising Metrics are regularly reviewed Level 2 (Quantitatively managed) All changes tracked in an Application Lifecycle Management (ALM) tool Builds not left broken Changes promoted through a consistent path to production Ability to manually roll back changes quickly and efficiently Infrastructure is highly available and fault-tolerant Automated alerting based on active monitoring IaC processes and practices are documented and available Level 1 (Consistent) All infrastructure defined as code Industry standard tooling is used to write code declaratively CI server to build, test and public IaC artifacts Automated tests run for every check in Provisioned infrastructure the result of an automated delivery pipeline Provisioning is idempotent Immutable infrastructure (no SSHing into boxes) Infrastructure is reliable and performs predictably Metrics calculated automatically, but not regularly reviewed. Centralised infrastructure monitoring and logging Level 0 (Repeatable) Infrastructure partly automated using scripts. Automation tooling is ad-hoc Some IaC tests Tests are run locally Provisioning is scripted but executed ad-hoc Patching and upgrades are done through provisioning processes Metrics are defined, but no way to collect and consistently measure Level -1 (Regressive) Nothing stored in version control Scripts stored on infrastructure No Continuous Integration server No written IaC tests No way to test infrastructure before provisioning Infrastructure is built manually from command line or GUI Existing infrastructure cannot be rebuilt Provisioning new infra is slow, inconsistent and painful Existing infrastructure is brittle and unreliable. Patching and upgrades done directly on running infrastructure. Trouble shooting on running infrastructure No defined infrastructure metrics: SLAs, KPIs, CSFs Monitoring and logging done directly on running infrastructure No automated alerting Practice Development Continuous Integration Provisioning and Configuration Management Observability
& compliance Testing Data management Configuration management Level 3 (Optimising) Teams meet to discuss integration problems resolve via automation, visibility, feedback All environments managed effectively. Provisioning fully automated. DevOps culture, collaboration to reduce risks, cycle time Production rollbacks rare. Defects found and fixed immediately Release to release feedback loop of database performance & deployment process Zero downtime provisioning of infrastructure. Automatic rollback, self service Level 2 (Quantitatively managed) Build metrics gathered, made visible and acted on. Builds are not left broken. Orchestrated deployments managed. Release and rollback processes tested. Environment and application health proactively managed. Cycle time monitored Quality metrics and trends tracked. Non-functional requirements defined, measured Database upgrades & rollbacks tested with deployment. Database performance monitored, optimised Ability to manually roll back changes quickly and safely Level 1 (Consistent) Automated build and test cycle when a change is committed. Artifacts managed Fully automated, push-button deployment. Same artifact, process for each environment. Change management and approval processes defined, enforced. Automated unit and acceptance tests. Testing part of development. Database changes performed automatically as part of deployment Provisioned infrastructure result of an automated delivery pipeline. Idempotent. Level 0 (Repeatable) Regular automated build and testing. Any build can be recreated from source Automated deploys to some environments. Configuration versioned Painful, infrequent, but reliable releases. Limited traceability from requirements Automated tests written as part of story development Changes to databases done with version controlled scripts. Provisioning scripted but executed ad-hoc Level -1 (Regressive) Manual processes for building software. No management of artifacts and reports Manual deployment. Environment-specific binaries. Manual environment creation Infrequent and unreliable releases Manual testing after development Data migrations unversioned and performed manually Infrastructure built manually, existing infrastructure cannot be rebuilt. Provision painful. Practice Build management & CI Environments & Deployment Release management & compliance Testing Data management Configuration management
SiteGround - Reliable hosting with speed, security, and support you can count on.
vivekprahlad
daitak
hamukazu
tosho
yuyatakeyama
ninomiya_ii
kinunori
kozy4324
sonic
rlifchitz
whisaiyo
elmodev09
kazzpapa3
frankvandijk
maltzj
sstephenson
tapps
smashingmag
axbom
aleyda
stephenakadiri
jdejongh
soudai
watany
