4 ms·
This has flicked a lightbulb on for me. If your teams are fairly self-organising, if you are small-a agile and building your process as you discover more, you
by the_other 6y ago
This has flicked a lightbulb on for me.
If your teams are fairly self-organising, if you are small-a agile and building your process as you discover more, you can plan in things like “dev A will spend 50% of this sprint learning dev-ops, without doing feature work or tech debt; and 10% shadowing dev B who already does Ops”.
That seems actionable, and measurable. Over two or three sprints/iterations/retrospectives, you’ll probably be able to measure the impact of the training (more successful releases, higher uptime, or more story points covered because ops is less a bottleneck etc).