I frequently find myself in conversations about Scaled Agile Framework (SAFe) and its utility or lack thereof. My opinions are based on both direct experiences in an organization that started using it and from comparing notes with colleagues in other large organizations, including many who are SAFe certified.
A “deepity” is a statement that sounds profound but isn’t. “To the extent that it’s true, it doesn’t have to matter.
When starting on the journey to agility, the most common path is for an organization to hire a Certified Agile Consultant™ and learn about the Manifesto for Agile Software Development followed by Scrum.
I’ve been a developer for a while. I’ve delivered using every industry fad that management has bought into. In 2003, the organization I worked for wanted to bring some discipline to our ad hoc processes so they sent senior developers and team managers to PMI training to become certified project managers.
Whenever we want to solve a problem or build something useful, we have decisions to make about the tools we choose.
Should we use Scrum? Kanban? Is Kanban for support and Scrum for development? Is Scrum for newbs and Kanban for elites?
The following is fantasy. Any resemblance to persons living or dead is coincidental. However, too many people live this. ScrummerFall Jackie is a buyer who needs better tools for forecasting demand so she can make better-informed decisions.
One of the most common pain points to anyone moving to modern delivery is, “how do we know we are doing it correctly?
In my last 5 Minute DevOps, I attempted to define user stories in a testable way. Real developers should test, after all.
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.