This week’s podcast is from the Writing Secrets book. My plans have changed for this book. Instead of being part of a bundle, I’ll be launching a Kickstarter for this book. (Why not practice my Kickstartering?) So keep an eye out for that. (Yes, I will learn how to share a link before next week’s […]
Many of my management clients tell me, “time is money.” That is only partially correct. Once you decide to invest a dollar, that dollar has the same value as any other dollar. Instead of focusing on the expense of a dollar, look for the value that dollar can return. (Because no one ever knows how
This week’s podcast is from the Writing Secrets book, specifically, part of the Preface. A funny thing happened on the way to this recording. I felt as if the words were not quite right. They didn’t sound like me. So I cycled until they did sound like me. Then I realized what had happened. I
I said earlier in this series that no one cares about how “agile” your team is. Or the kind of “agile” your team professess to be. Managers do care about agility: the ability to respond quickly to a changing or changed environment. And that depends on where your team has delays. That’s why value stream
In Part 1, I wrote about what the value stream map looked like for expert-focused “cross-functional” teams. In Part 2, I discussed cooperative teams that have working agreements on when to do code review or make other decisions as a team. While those teams exhibit somewhat more agility, cooperative teams are still not collaborative. So
This week’s podcast is from the Writing Secrets book. While I did collect all the writing secrets, I did not “just” collect them and stuff them into this book. Instead, I cycled, writing forward for more clarification so they make more sense as a book. Then, I edited them. Yes, I practice what I preach.
In Part 1, I wrote about what the value stream map looked like for expert-focused “cross-functional” teams. While those teams are cross-functional, they are not collaborative. However, these expertise-focused “teams” are not the only type of non-collaborative agile teams. There are also cooperative teams. Cooperative teams still tend to work sequentially, focused on each person’s
We talk about cross-functional agile “teams” as if they are the norm. That’s what I show in this image: some responsible person creates a ranked backlog that the cross-functional, collaborative team works on. That team delivers increments of value on a regular basis. At some point, the team will demo their work and retrospect on
My podcast this week is from the Writing Secrets book. (I think this is the last secret, but we will see.) Enjoy! Note: If you read these posts in an RSS reader or via my Feedblitz feed, you might not see the player below the heading “The Podcast.” In that case, please either navigate to
This week’s podcast is from a new book: Nonfiction Writing Secrets: How to Write Better, Finish Faster, and Publish More Often. I had an opportunity to offer an exclusive book in a Storybundle later this spring. Because I use continual planning for my business, I realized I could offer this book. That means I have