I spoke with another writer, Sam, earlier this week. He’s pretty sure a colleague, John, is plagiarizing his blog posts. Not in writing, but in conversation. Yes, John is using Sam’s original words and phrases and passing those words off as John’s ideas. In videos, podcasts, all kinds of “thought leader” work. This happens. All […]
When Mark Kilby and I wrote From Chaos to Successful Distributed Agile Teams, we suggested teams add a text backchannel. Even when the backchannel is asynchronous, the information in it increases the value of all the team’s communication. The backchannel helps everyone see all the information. That helps all the team’s communication. Some of my
Several of my clients want to use some sort of maturity assessment for their agile transformations. Often, the maturity levels demand adherence to specific practices or processes. Some of those practices and processes work for my clients now. (I’m not so sure about others.) As my clients evolve, will what they do now continue to
I’ve had the pleasure—and displeasure—of many remote meetings over the past few weeks. The difficult meetings had a common root cause: the meeting leaders attempted to do a direct transfer of how they lead an in-person meeting to remote/WFH meetings. When that occurs, they miss the ability to optimize on our separation by choosing how
Three Tips for Coping when Change Might Make You Nuts (Support Others) We’re still living in substantial uncertainty and chaos. We don’t know when we might be able to return to work. The kids are home from school for the foreseeable future. Where I live, in Massachusetts, all “non-essential” businesses are closed. (I did not
Especially when we use agile approaches, we want to be close to our customer. If you’ve ever had a chance to sit with a customer, you’ve learned how effectively (and fast!) the team and the customer learn from each other. And, too few teams have any access to any customers. Most of their customer information
I’m a monthly contributor to the Gurock blog. This month’s article is Feedback & Feedforward for Continuous Improvement: Using Double-Loop Learning Challenges Our Assumptions. Single-loop learning is when you “Plan the work and work the plan.” Double-loop learning is when you challenge assumptions during the project. Agile approaches allow us to do so. This is the
Let me summarize what I’ve been talking about in these posts. The problem I’m seeing is that too many teams and organizations plan too much in too much detail too soon. Instead of architectural BDUF (Big Design Up Front), it’s project planning as BDUF. They expect one single person (a product manager or a product
You’ve started thinking in feature sets. Maybe you’ve experimented with rolling wave plans inside one quarter, so you can change and replan as you need to support your project or program. You’ve discussed flow-based roadmapping as a way to create MVPs and MVEs, release smaller value more often so you can make better decisions. You
If you need to plan more often than once a quarter, how do you know how to replan? Instead of incurring the time and cost when you bring everyone together, consider the Product Value Team. (In past writing and presentations, I’ve called this the Product Owner Value Team. I am trying to change my term