I’ve been working with a new-to-the-organization senior leader, Steve, who struggles with this challenge: He wants to capitalize some operational expenses. (That’s a move from OpEx to CapEx.) He is convinced that will give him some freedom to change things while everyone is still working hard. So they’ve asked all the technical people to fill […]
Every day, I hear more stories of agile coaches or Scrum Masters losing their jobs. Why? Several reasons: No manager cares about “agile” even if they care about agility. So, selling “agile” into the organization doesn’t create any traction for change. Agile coaches and Scrum Masters are staff positions, not “line” jobs. Worse, many agile
Collecting data isn’t free. There’s a cost to every piece of data. There’s also value. How do we balance the cost and value of data? As with all juicy questions, it depends. And, in general, the easier the data is to collect, the less value there is in the data. Examples of Useless and Cheap
I’ve been working with several managers at organizations large and small, who want to capitalize their software “earlier.” These managers have some strongly-held beliefs about the people: People are resources Resources can multitask on several projects at a time If “headquarters” does the difficult work, you can move the “grunt” work to lower wage areas
Several recent clients want help with these problems: Estimation isn’t accurate. Because the estimation isn’t accurate, management can’t predict when they can release anything. Managers can’t manage the capitalization (a way to move from expensing software to capitalizing it). Teams can’t seem to ever deliver a finished feature. The work in progress everywhere is quite large.