4 ms·
it makes a difference because frequently, when you have (say) several hundred teams of 10-15 people, they need to interoperate (so that the fields used, and the
by felixgallo 4y ago
it makes a difference because frequently, when you have (say) several hundred teams of 10-15 people, they need to interoperate (so that the fields used, and the meanings of the fields, are standardized and have a structured lifecycle), and also they need to be able to roll up to larger progress reports/status updates so that the org leaders can understand where everything is. If all the small teams organically choose their own fields/meaning/process (which happens, all the time, everywhere, by default), you can end up with a tower of babel problem.
- djur 4y agoUnder that kind of top-down structure, each team will force their organic processes into the Procrustean bed of what the project management system expects. Aggregating that data heedless of any variation in meaning will result in garbage. Leadership can't do anything with aggregate metrics derived from day-to-day development anyway. That results in fantasy metrics like "velocity". They should be focused on conditions and outcomes.