@der_mit_ph @nathenharvey@trahec If using Github, you can use Github Actions to record the relationship between commits and PRs at various boundaries (e.g new commit added, merge, etc.)
🚀 We just released our plugin for #backstageio , the most popular developer portal platform!
You can now embed your Okay charts in your team/service pages, including DORA Metrics, Incident Dashboards, CI/CD Performance charts, and many more.
#devops#cicd
@beyang Great article - really believe in feedback loops and focusing on unblocking engineers. The set of metrics to use is highly contextual and cannot be forced into e.g. DORA. You might want to check https://t.co/pZ6c1S4Xk3 and our section in the EE handbook: https://t.co/ApwOuwulJh
@utsav_sha@beyang@ediardo Ex-devs turned managers, but @tomasrb and I recently put together the following handbook: https://t.co/KKDyipT1Bm. Contributions are welcome since it's open-source.
What causes developer survey fatigue?
Lack of follow-up by the leadership.
Surveys are not data gathering tools, they are communication channels - from developers to managers.
If managers don't "answer" with actions, surveys get ignored.
TCP >> UDP 😉
@GergelyOrosz Examples of such "developer productivity metrics":
- how long do you have to wait on CI
- how long does it take to receive feedback on your PR
- how many recurring meetings do you have to attend
- latency of code search, hot-reload, etc.
@GergelyOrosz Developer productivity is an outcome of how well the organization functions. It measures manager performance, not developer performance.
The goal of management is to remove blockers such as bad tools or processes, and these problems are measurable
@rhein_wein@dimiterbak I find it easier to measure bottlenecks / things that are getting in the way of being productive. It also puts the accountability on the leadership, and not on the developer. Meeting load, broken processes, slow tools, etc.
@dimiterbak@rhein_wein My co-founder and I recently wrote a handbook about this topic: https://t.co/KKDyipT1Bm, the first chapter tries to answer the "definition" question in detail.
Managing Time & Interruptions is arguably the most important input to create high performing software teams. Read more at https://t.co/xTDQegYNCr
#engineeringleadership#engops#productivity
We raised $4.4M from @kleinerperkins to amplify our momentum and provide engineering effectiveness and visibility to every software company!
https://t.co/uRWAHqrKfg
Teaching people — directly and through cultural norms — that they are powerful, not powerless, to change and fix broken processes is key
https://t.co/7V3G5lr2Kz
@anjuan We follow this approach at @OkayHQ. I shared some examples at https://t.co/5braTUYbsL. The biggest drags we are seeing are: meeting/interview load, code review practices that introduce too much friction, and after-hours interruptions like noisy pages