Scaling improvement is the siren song of every enterprise. Once we have a team that is able to deliver the outcomes we are looking for, the obvious next step is to define those best practices for the rest of the teams.
As organizations attempt to transform, they often focus on tooling or hiring “transformation consultants” as a silver bullet.
One of the most common pain points to anyone moving to modern delivery is, “how do we know we are doing it correctly?
So, you hired an “Agile Transformation” consulting company to advise executive leadership and you’re “Agile” now.
Has this ever happened to you or have you ever seen a support request like this?
Protecting the Business Developer driven software testing is not new.
I was asked recently about the best practice for using GitFlow with continuous integration.
What does a product team really looks like? You’ll hear lots of DevOps-y buzz words: “T-shaped people”, “cross-functional”, or “Two Pizza Team”.
In my last 5 Minute DevOps, I attempted to define user stories in a testable way.
What is Pragmatic DevOps? It’s just a catchy way of saying we deliver with Minimum Viable Process using lean techniques to drive waste out of the system.