I especially liked the part about friction - as a manager/director, reducing friction for our teams is also a great way to choose hands-on tasks.
During a retro a few months ago, engineers raised again how difficult it is to clone objects from the production to QA buckets, based on specific requiremen…
I especially liked the part about friction - as a manager/director, reducing friction for our teams is also a great way to choose hands-on tasks.
During a retro a few months ago, engineers raised again how difficult it is to clone objects from the production to QA buckets, based on specific requirements. There was some Jenkins job, but it copied tons of not needed shit and took hours each time.
This is a task that involves multiple teams - the QA, DevOps, and another engineering team. I could have asked someone to do it, but I felt it’s a good choice of a task for myself, to feel the process. Took me a couple of weeks, I learned a lot, and made the life of my team (and the whole R&D) a bit easier.
Terrific article Jordan and Chaitali!
I especially liked the part about friction - as a manager/director, reducing friction for our teams is also a great way to choose hands-on tasks.
During a retro a few months ago, engineers raised again how difficult it is to clone objects from the production to QA buckets, based on specific requirements. There was some Jenkins job, but it copied tons of not needed shit and took hours each time.
This is a task that involves multiple teams - the QA, DevOps, and another engineering team. I could have asked someone to do it, but I felt it’s a good choice of a task for myself, to feel the process. Took me a couple of weeks, I learned a lot, and made the life of my team (and the whole R&D) a bit easier.
That's a great example of friction and how to reduce it!