We’ve all seen the news about tech layoffs. If you’re an engineering manager, are you having to squeeze more out of existing teams, because adding staff anytime soon is unlikely? Maybe you’re tempted to micromanage your developers, thinking that if you know every aspect of their work, it’ll boost productivity. But, that approach doesn’t feel right, and you know your devs would hate you for it. What’s an engineering manager to do?
If you're a DevOps team looking for ways to improve your performance, you've probably heard of the Accelerate and DORA metrics. Tracking your performance with these metrics is a challenge, requiring good tooling. You might be tempted to build your own tracking solution, but you don’t need to! Due to the growing popularity of DORA metrics, several tracker tools are available on the market. But how do you choose the best DORA metrics tracker for you? This handy comparison guide will help!
Sleuth’s product team is pleased to announce an exciting new feature that provides early and actionable visibility into emerging work-in-progress risk! With this release, Sleuth provides customers even more actionable visibility into their engineering efficiency. It extends Sleuth's deploy-centric tracking capabilities upstream in the developer workflow to provide real-time visibility into in-flight work and its emerging risks. Here's how it works.
Sleuth is pleased to announce a new option to start your Change Lead Time clock based on state transitions in your issue tracker! In our ongoing effort to meet customers where they are, we heard from many of you that you’d like Sleuth to account for and provide visibility into your pre-commit coding time. We’re pleased to offer this this new option to tell Sleuth which specific state transitions in your issue tracker should start your Change Lead Time clock!
