agile

management, MPD

Process Agility: An Impossibility?

I’ve seen several cases of process standardization recently. Those processes don’t translate to the current context. The processes don’t have sufficient agility to deliver the necessary results. Yet, people who want to use agile approaches don’t want to apply agile thinking to their processes. Some clients want to create their custom agile process— and then […]

newsletter

Three Tips for Coping When You’re Supposed to Lead

Three Tips for Coping When You’re Supposed to Lead We’re several weeks into the COVID-19 crisis, and we still don’t know much about the future. We have some data about the present. But the future? Nope. You might have a title with “lead” or “manager.” And, you might not be sure about what to do

management, MPD

We Won’t Return to Normal; We Will Discover Normal

Many people talk about “going back to normal.” We aren’t going to return to normal. That old normal is gone, at least for a year, if not longer. (I suspect we will cycle between remote work and office work for the foreseeable future.) What we can do is discover a new normal. Discovery requires different

newsletter

Three New Year’s Tips to Ease Your Team’s Agility

Three New Year’s Tips to Ease Your Team’s Agility I hope you are all having a terrific holiday season. A reader asked me about tips I had to ease her project’s transition from waterfall to an agile approach. Woo! I have plenty, so I decided to select three tips I have seen work. Tip 1:

newsletter

Three Collaboration Secrets to Create Your Agile Culture

Three Collaboration Secrets to Create Your Agile Culture I’ve been working with managers and technical leaders on a big problem: How to create an agile culture. The managers and leaders want to create a successful agile culture. The people on the teams—they often want to be “left alone” to do their work. That’s not horrible.

management, MPD

Component Teams Create Coupling in Products and Organizations

Many of my clients feel stuck with their component teams. They feel they must implement across the architecture, not through it. That’s because the people are organized in component teams. As the organization grows, so does the number of component teams. The more component teams they have, the more complexity they create in the teams, in

Scroll to Top