Skip to content

[CHI-2025] Fix description of talk #14829

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
toshywoshy merged 1 commit into from
Jan 24, 2025
+1 −1
Merged

[CHI-2025] Fix description of talk #14829

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion content/events/2025-chicago/program/michael-stahnke.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,5 +10,5 @@ sharing_image = "michael-stahnke.png"

The core metrics for measuring team effectiveness with DevOps have been around quite a while now and they’re a great starting point. What measurements matter after those are established? What should software delivery metrics be telling us?

In this ignite talk, I’ll pull out some research from time leading engineering at Puppet, CircleCI and Flox to talk about some different measurements that should help elevate your teams. I'll share insights around measuring time to spin-up for engineers, looking at team and departmental throughput, and measuring the effectiveness of your engineering platform.
In this talk, I’ll pull out some research from time leading engineering at Puppet, CircleCI and Flox to talk about some different measurements that should help elevate your teams. I'll share insights around measuring time to spin-up for engineers, looking at team and departmental throughput, and measuring the effectiveness of your engineering platform.