I’ve spoken professionally at conferences for 25 years. I enjoy it. And, several people—all men, so far—have suggested I should “make room” for other voices. To me, that’s a solution in search of a problem. I ask them what problems they want to solve. They want speakers who are: More diverse in gender More diverse […]
Your team says they use Scrum in two-week iterations. And, in order to “finish” everything inside the timebox, you don’t do any of these things: Refactor to simplify the code or the tests. Create automated tests. Use formal acceptance criteria on a story or for the iteration or the project. That means you have work
Several weeks ago, I posted my innovation principles, based on Modern Management Made Easy, book 3. I developed them because I was discovering the user journey through the book. I needed a way to link the ideas together. Of course, I also created principles for managing yourself (Book 1) and for leading and serving others
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
I’m rewriting/reorganizing the Lead an Innovative Organization book. I realized I have 7 innovation principles: Clarify the organization’s purpose. Manage for effectiveness. Seek outcomes, not outputs. Flow efficiency at all levels. Encourage small-world networks of relationships. Organizational integrity. Encourage change and experiments. Anytime I’ve seen a successful innovation culture, I’ve seen these principles. (I’m trying
I wrote a number of posts and newsletters over the past few weeks to help you see alternatives in this age of uncertainty. I hope you use these ideas to generate other ideas or ask more questions and create more experiments. The posts on this blog: 7 Tool Tips for Your Newly Distributed or Remote
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
In my experience, too many projects are under too much pressure. The sponsors want all of the features, completed in too-short time, with no defects. And, if possible, the sponsors think the project should cost nothing, the team should not need any training, and the team can work in any way, regardless of the desired
I wrote about how to pick a driver in Part 1. In Part 2, I wrote about how you might finesse some of the constraints and floats if you can release frequently. What if you’re like this organization, Acme? Acme has been working towards agility for the last couple of years. However, they still have
In Part 1, I wrote about the origins of drivers, constraints, and floats. I needed them when we only could release the project once to the customers. You saw the questions that help people choose the project driver. What about the constraints and floats? I think of constraints as bounding the project inside the driver,