A "story" is not a code word for some random bit of work. Thinking of it as such is a classic example of Larman's Law in action. People cannot imagine a new way of doing things, so they twist the new approach into something that looks like what they do now. It's a complete lack of imagination coupled with the mindless belief that there is one true way to do things.
People who cannot imagine anything other than working from a detailed up-front waterfall specification will turn everything into a detailed up-front waterfall specification.
A story is not a specification. Period. It is a description of the users/customer's work. It does not describe any aspect of a computer program. It describes the domain. The point is that, when we focus on the story, we build things that provide direct value to the users/customers. When people turn "story" into a code word for a mere task, they lose the value focus, and thus the entire point of using an actual story.
@RailMinIndia@GMSRailway Train no 07189 currently running late by 5hrs. No one knows what exactly is the reason. Delay like this is causing inconvenience the next planned onward journey. Need action on this immediately.
@RailMinIndia@GMSRailway Train no 07189 currently running late by 5hrs. No one knows what exactly is the reason. Delay like this is causing inconvenience the next planned onward journey. Need action on this immediately.
@HondaCarIndia one of the worst road side assistance service from Honda. I made the worst decision of buying the RSA program from you. I am trying for the past one hr still unable to reach your RSA people. Is this the way you have your RSA services. Worst🤯😡
On Measurement:
"What gets measured gets managed - even when it’s pointless to measure and manage it, and even if it harms the purpose of the organization to do so." —Drucker 1/4
Agile is NOT a management technique.
Just saw yet another snake-oil cert, this one for "Agile Programme Managment," whatever _that_ is. If you ever see "Agile" and "Management" together, it’s a sham. Run.
Stakeholders are not customers.
Pleasing the stakeholders at the expense of the customers is politically expedient, but rarely works out well for the company.
If you have "sequentially related" dependencies between stories, you have probably split a single story horizontally. Instead, you need to split by narrowing scope. In other words, dependencies are a sign that you don’t know how to specify vertical-slice narrow-scope stories.
If you always grab so many stories off the product backlog that you can’t finish them all, do bear in mind that you’re preventing another team from working on that story, forcing them to work on something that’s lower value. Better to have slack time than delay high-value work.
Solving problems for a team is hierarchical command/control thinking.
Helping the team solve its own problems (by providing resources [e.g. books, classes, time], alternatives, choices, is agile thinking.