Technology Leadership

Topics

Technology Mentoring
Setting up standards
Working on architecture
Being a “filter” in front of the team from the stakeholders and the board and any dispersion

Chief Technology Officer (CTO)

Long term technology Strategy
Choosing main Technologies
Leading Innovation
Coordinating suppliers
Integrating tech with business needs

Involvement balance

Between full autonomy vs 100% control

Architectural Drivers

Always quantify drivers - so that there is one single goal.

Types of drivers

Functional requirements
Quality requirements (security, scalability)
Limitations (time, money, tech)

Each driver should have it’s metrics - and should be analysed against it.

Concepts

DevOps - culture for cooperation between Development and Operations and bringing together the code
CI/CD - tests and deployment automation, bringing value securely and quickly

Business Continuity

Securing key functions during crisis - examples: circuit breaker & fallback.

More advanced:

War gaming - simulating crisis situation
Chaos Engineering - creation of crisis situation in the system

How to mitigate

Playbooks - ensure that they work, keep testing them

SLA - Service Level Agreement

Describes what is the guaranteed level of service.

Availability of the functionalities
Uptime percentage
Frequency of service breaks
Ways of communication during the downtime
Performance metrics

PoT, PoC, PoV

Proof of Technology
Proof of Concept
Proof of Value

Risk Management

Murphy’s Law
Postmortems
Playbooks

SDLC

Every sprint should be actually mini SDLC

Analysis
Design phase
Development phases
Support
Decommissioning (if happens)

Agile / Waterfall / Spiral Model / V-Model

Deployment

Deployment - pushing code to production

Release

“Business side” of deployment, so sharing the function to the client, documentation, communication, kind of like business DoD. Needs to be also synchronized with marketing.