Copyright: cthoman - 123RF Stock Photo |
First, to measure these things. Work with the teams to
figure out what makes sense, but an example to maybe start with is:
- Defect fixing
- Code Integration
- Planning
- Branching/Merging
- Manual Testing
- Creating/maintaining automated tests
- Innovation
- Other?
Copyright: 123RF Stock Photo |
One other thing, be fairly aggressive on these goals. For example, improving automated testing by 1% is pretty weak, try for a higher
number that seems challenging but still reachable. If you don’t make that number, that’s ok, you will learn much more about what is keeping you from those targets, and
these newly discovered impediments can be addressed as new objectives in the
next planning event.
If this sounds like a lot of work, it is. But it’s
well worth it. If you say that you don’t have time to add this to your
plate, look closely at what’s on your plate. This measurement practice is
the protein and vegetables you need, a lot of the other stuff is just empty
carbs and should be prioritized out or delegated to someone else. Your true value as an RTE is in helping the
train improve, using Activity Accounting is one significant way to do so.
(Much credit for these concepts go to Humble, Molesky and O’Reilly
in their excellent book “Lean Enterprise”.
I recommend every train engineer have a well-read copy at hand)
No comments:
Post a Comment