Skip to content
Ameen Abozaid
Englishالعربية
STF-009

Engineering productivity

  • 8 Lessons
  • 4 h practice (estimate)
Start module
On this page 9 topics

Overview

Topics

  • Build pipelines
  • developer tooling
  • feedback loops

Learn first

4 h of practice (estimate)

Learning outcomes

  1. Measure developer productivity with balanced indicators (delivery metrics, developer experience surveys, cognitive load) without ranking people.
  2. Find the biggest feedback-loop delays (build, test, review, deploy, onboarding).
  3. Improve build pipelines and developer tooling where the gains compound across teams.
  4. Justify productivity investments in time saved and delivery outcomes.

Lessons

  1. 01What productivity means for engineers
  2. 02Measuring without surveillance
  3. 03Feedback loops: where time goes
  4. 04Build and test pipelines at scale
  5. 05Onboarding as a product
  6. 06Making the business case
  7. 07Demo: cutting a 40-minute CI pipeline to 8 minutes
  8. 08Demo: running a developer-experience survey and acting on it

Lab and exercises

Lab

STF-009-LAB1 · Productivity baseline

Outcomes: 1–4 · Time: ~3 h

  1. Measure Platform 2.0 feedback loops: build, test, review, deploy, onboarding (case data).
  2. Run or analyze a developer-experience survey and cluster themes.
  3. Pick the top two improvements where gains compound across teams.
  4. Estimate engineer-hours saved per month with stated assumptions and quality counter-metrics.
  5. Record the baseline for later comparison in the capstone.

Acceptance: baseline recorded so the improvement can be measured in the capstone.

Exercises (case-based; six exercises)

IDOutcomeTask
STF-009-EX011A VP wants a leaderboard of commits per engineer. Write a short reply proposing balanced indicators instead.
STF-009-EX021Choose eight indicators across delivery, experience, and cognitive load; name the source and level of each.
STF-009-EX032From a commit-to-production timeline with waits, find the three biggest delays and rank by total hours across teams.
STF-009-EX043A CI pipeline takes 40 minutes with 12% flaky failures. Propose a stepwise plan and how you would measure each step.
STF-009-EX054Estimate hours saved per month for a 10-minute pipeline reduction for 160 engineers and state the assumptions.
STF-009-EX062, 4Design an onboarding improvement with a metric, and write the case in three sentences for the VP.
Show solutions
  • EX01 Explain gaming and trust damage; offer team-level lead time, change failure rate, experience survey; keep individual data out of reports.
  • EX02 Examples: lead time, deployment frequency, change failure rate, time to restore, survey on tooling satisfaction, time to first production change, review wait, cognitive load score.
  • EX03 Typical: review wait, CI queue, deploy approvals; rank by hours x teams affected.
  • EX04 Baseline; cache; parallel shards; quarantine flaky tests; one change per run; compare duration and flake rate.
  • EX05 Example: 160 x 3 runs x 10 min = 80 hours per day if each engineer waits, but not all wait fully; state a discount factor (for example 30%) and show the range per month.
  • EX06 Metric: time to first production change (target in days); one-command setup, buddy, starter task; payback from faster ramp-up.

Outcome coverage: all four outcomes appear in exercises and lab.

Workplace evidence: a productivity improvement you led with before/after data.

Quiz

Outcomes: O1 balanced measurement · O2 feedback-loop delays · O3 pipelines and tooling · O4 business case.

A self-check for you: nothing is graded, saved or sent anywhere. Choose an answer, then check it. You can try again as often as you like.

  1. 1A balanced view of productivity includes:O1
  2. 2Individual leaderboards are avoided because they:O1
  3. 3Which is a delivery metric?O1
  4. 4Which measurement often reveals the biggest delay?O2
  5. 5Prioritize delays by:O2
  6. 6When changing a slow pipeline, you should:O3
  7. 7Why improve the shared pipeline template before one team's pipeline?O3
  8. 8A good onboarding metric is:O3
  9. 9A productivity business case should state:O4
  10. 10A survey without published actions:O4

Practical part

Six case exercises STF-009-EX01 to EX06 plus the lab, reviewed as a baseline and business case. Pass: at least five of six exercises correct, quiz at least 8/10, and a recorded baseline that the capstone can measure improvement against.

Common mistakes

Lines of code or story points as productivity; optimizing one team's pipeline when the bottleneck is shared.

Assessment

Baseline and business-case review.

Workplace evidence

A productivity improvement you led with before/after data.

Career relevance

Success metrics in STF-CAP; measuring impact (STF-019).

Type to search levels, phases, modules and lessons.