Developer Dashboards

( I already had some thoughts on that topic ). Goal Get a better overview of future/pending/past work and keep it. “If you want a developer to do something, e.g. establish a high test coverage, make it easy with sane reasons” What? Pre-Deployment Feature Branches, consisting of PRs Build (Test) Reports Static Code Analysis (Report?) Build Status green/yellow/red Human Code Analysis (Code Reviews) Post-Deployment Monitoring Active (Alerts) Passive Configuration Feature Flags?...

February 22, 2018 · 1 min · Markus Ruepp

Engineering Dashboard

Whats the goal? see urgent problems in an critical area that triggers immediate action What to show? problems that endanger the product problems that usually gets missed critical problem that does not have a clear owner (otherwise notify directly) that affects many What not to show? information that can be transferred more efficient things that don’t require immediate action How to show it? color codes How to react?...

August 26, 2017 · 1 min · Markus Ruepp