Your managers want to measure all kinds of interesting pieces of data to run the company well. Much of that is reflected in your organization’s Profit and Loss (P&L) statement. (There’s a great site with an explanation of a P&L statement.) Notice any organization’s three big numbers: Revenue, all the operating expenses, and net earnings. […]
I use many apps on my Mac, iPad, and iPhone. There is clearly something in the air because, during the past three weeks, most of them broke. Here’s a partial list: The password manager (on all three devices, with at least 4 failure modes) Two different health-based apps Various kinds of email-based apps What do
When I wrote Manage It!, I included an idea called a Hudson Bay Start. I wrote an article about that later, in How to Use Iteration Zero—Or Not. Hudson Bay Starts are not a new idea. However, you might not know what they are. Here’s the idea: the team chooses one item from their backlog.
I discussed how to calculate the Costs of Delay in the previous three posts, and then offered an example in Part 3. Notice that the example uses cycle time or how the team feels about the remaining time to think about the value in order to rank the work. (The links to all the posts
Ranking work, whether it’s for the backlog, a roadmap, or the portfolio, sometimes feels like throwing darts and hoping for the best. But especially if there’s too much work and a lot of WIP, we have a tool for clarifying that ranking—the Cost of Delay. It does require counting the number of people and easy
In Part 1, I explained the various Costs of Delays with this image: I explained how to calculate the salary costs in Part 1. Now, it’s time to calculate/assess Costs 2, 3, and 4 to decide on the most valuable work. (If you have Manage Your Project Portfolio, there’s an entire section about calculating and
If you’re like my clients (or me!), you have too much work to do. (I’m beginning to think “too much work” is the norm.) But how do you decide what to do first, second, and third? And never? I use Cost of Delay. (I’ve written about how to see the various Costs of Delay, especially
When I wrote Manage It! Your Guide to Modern, Pragmatic Project Management, I included this chart, the Iterations Content Chart as part of a possible dashboard. I created that chart to clarify the challenges a specific team faced. They had problems with multitasking and the inevitable changes. The first way to use an iteration contents
Are you trying to use story points for estimation? If so, you might have encountered these problems: Story points reflect the ideal thinking of the team, not the actual experience of the team. Your managers don’t want story points—they want durations and dates. In the absence of sufficient information, everyone makes up fiction (human stories)
Susan, an experienced senior leader, wondered what to do. Her company’s market was on a roller coaster. Increased revenue meant a lot more customers, who clamored for more features. So, the product leaders pressured the teams to deliver faster. But she’d been in a roller coaster situation before. After two years of stupendous growth, revenue leveled off in just one