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 […]
What Happened to the Beautiful Plans? (They Became Experiments) Tim, a senior manager, loved seeing plans for work and roadmaps. Then, the organization decided to Embrace, Not Manage Change. Tim wasn’t sure how to track the work. This image helps me frame the need for an agile approach. (See the blog series: Where I Think “Agile” is
Many people in the agile community promote a product orientation over a project orientation. That’s possible because an organization has product or feature teams. That works until you have more products than teams. That’s when you might still need projects to accomplish everything. If you keep teams together, you can still use projects in a
In an ideal agile world, the team would work directly with a customer. When you have a small product that serves maybe three types of customer (new, expert, admin for example), and that customer is down the figurative hall, you might not need any product people. You can create short feedback loops with your customer.
We have many words for people who shepherd the business value of a product. The many words aren’t a problem, as long as we can all agree on what these various people are and they take responsibility for. When we don’t agree, we run the risk of not managing our strategy, not thinking in terms
As I work with people to use agile approaches, I see many organizational constraints. I’ve been trying to find a visualization for what I see. I don’t know if I’ve got it yet, but here is my sum-of-the-parts image. The organization’s culture drives decisions (or not!) about the strategy. Strategy, with any luck, creates clarity
You’re working on a project or a series of tasks for some deliverable. Do you know why? The reason behind the project explains the value of your work. You might work on something just for the fun of it. Back before I had children, I bicycled, crocheted, and needlepointed. I made time for these hobbies
I was thinking about the automakers, and how they want many billions of $ from Washington (please, noooo). I don’t know what their strategic planning is, but it seems not to have changed from the 1960’s. Certainly, when I started buying cars in the 1970’s, I could not afford the low quality/high price/low gas mileage.
Steve Smith challenged me in a comment to the cowardly layoff/no feedback posting: “What would you have done if you were the manager who layed off these people?” I’ve written about layoffs in a previous Software Development column, but let me address the specific problem Steve described: The manager needs the paycheck. The manager (or