"Feelings versus facts: why metrics are more important than intuition", Igor Drozd .pptx

QUALITY AND TESTING
Do you actually know how effective your testing is?
 What percentage of bugs slips into production after testing?
 What percentage of business-critical scenarios is covered by automated tests?
 Who finds more defects — your QA team or your customers?
 Are your products becoming more reliable with each release or sprint?
PRODUCTIVITY, PROCESSES AND AI
Do you know how effective your teams and processes really are?
 What is your technical debt level, and how fast is it growing?
 How many sprint goals does your team actually complete — and how many get carried
over?
 How do your key metrics change after adopting AI-powered tools?
 Is your productivity increasing? Are bug rates dropping? Are releases getting faster?

LET'S GET ACQUAINTED
 CTO at Silpo for over 4+ years
 More than 18 years in IT
 Progressed from developer and architect to CTO
 20+ launched products in the E-commerce sector
 I’ve spent the last 8+ years analyzing software
development quality

Offline Shops
Silpo E-commerce
and Ecosystem
TODAY WE’LL TALK ABOUT…

STOREFRONT APPLICATIONS
SuperAPP LOKO SuperWEB

 10+ million orders during this last 3 years
 6+ million unique Guests
 IT Engineers: 400+
 Teams: 40
 Products: 25+
SILPO E-COMMERCE IN NUMBERS

OUR TEAM*
*the part that somehow fit on the screen )

A CTO IS ACCOUNTABLE FOR
 Production stability
 Predictable and safe releases
 Code discipline and technical debt management
 DevOps efficiency and delivery flow
 Mature and reliable testing processes
 Team productivity and delivery consistency
 Security and vulnerability control
 Continuous improvement of processes through tools and AI

TYPICAL ACTIVITIES OF CTO
Weekly CTO Routines
 Production stability review — 1–2h
 Technical debt & code quality check — 1h
 CI/CD & release analysis — 1–1.5h
 Team performance & sprint progress review — 2h
 QA quality check (escaped bugs, tests) — 1h
 Security overview — 40m
Total: ~8–10h/week
Monthly CTO Routines
 Monthly Quality Review — 2h
 Technical debt overview (all teams) — 2–3h
 Delivery & release process assessment — 1–2h
 Team Performance Review — 3–4h
 AI impact review — 1h
 Security & compliance check — 1h
Total: ~10–14h/month

PROBLEM
~30% of a CTO’s working time is spent on
quality routines
That CTO’s time
can and should be freed for
STRATEGIC INITIATIVES

👉 I invest only 2% of my monthly time to
regularly review quality, technical debt, and
development processes across the entire
organization.
👉 And the 28% of time I saved is invested into
strategic initiatives - developing AI capabilities,
scaling automation, strengthening our platform,
and driving long-term technological evolution.

We can hire a team of Engineering Managers, train
them, onboard them — an additional cost of
10 × $4,000 = $40,000 per month.
But that’s not our path.

Ownership of teams and engineering forums over
standards, metrics, and product performance in
production
+
Quality Analytics Tool as the navigation compass —
the single source of truth for quality, stability, and
engineering discipline.

 CUSTOMER SATISFACTION
 BUSINESS REPUTATION
 COST EFFICIENCY
 COMPETITIVE ADVANTAGE
 PRODUCTIVITY AND EFFICIENCY
 COMPLIANCE AND SECURITY
PRODUCT SUCCESS METRICS

QUALITY STRUCTURE
ENGINEERING OPERATIONAL QA
PROCESS
● Code Quality
● Test Coverage
● Complexity
● Architecture
Quality
● Performance
● Stability
● Customer
Support
Response Time
● Mean Time to
Repair
● Uptime
● Error rate
● Development
Cycle Time
● Rework Rate
● Innovation Rate
● Planning
efficiency
● Feature
Completeness
● Defect Density
● Bug Fixing Time
● Defect Leak Rate
● Test Coverage
● Automation Test
Coverage
● Releases Success
Rate
● VCS adoption
Rate
● Releases
frequency
DELIVERY
● Vulnerability
Count
● Security Incident
Response Time
SECURITY

VARIETY OF TOOLS
Software Quality
Analytics Tool

For whom…
Stakeholders
Engineers CPO, POs
Stakeholders - a holistic view of the software's quality and performance.
They provide transparency, allowing stakeholders to make informed
decisions, understand potential risks, and align their expectations with
the development team.
Scrum Masters - valuable insights into the team's performance,
productivity, and adherence to quality standards. They enable Scrum
Masters to identify bottlenecks, track progress, and make data-driven
decisions to improve the development process.
Engineers - the metrics and analysis provided to optimize their coding
practices, identify areas for improvement, and address potential defects.
These tools help engineers streamline their workflows, enhance code
quality, and deliver robust software solutions.
Product Owners assess the quality and reliability of the software being
developed. They provide insights into the product's performance, and
adherence to quality standards. PO can make informed decisions,
prioritize feature enhancements, and ensure customer satisfaction.
SM, PM

SUMMARY
 Empowers technical leadership to stay focused on strategy.
 Gives teams clarity on where they are and what to improve.
 Ensures alignment with defined standards and engineering practices.
 Helps translate business OKRs into technical and process-level initiatives.
 Keeps teams focused on what truly matters.
 Enables self-organized, accountable engineering teams.
 Drives scalable growth of the entire organization.

"Feelings versus facts: why metrics are more important than intuition", Igor Drozd .pptx

More Related Content

Similar to "Feelings versus facts: why metrics are more important than intuition", Igor Drozd .pptx

More from Fwdays

Recently uploaded

"Feelings versus facts: why metrics are more important than intuition", Igor Drozd .pptx