Thanks for writing them up twice my friend! Sounds like a tech debt Friday each week is really helpful man, nice idea!
Do you do any other side work besides dev? Does each dev only have responsibilities of feature work or are you responsible for different initiatives as well?
We used Kanban at my old team and I absolutely loved it. So much more efficient, less meetings, and still measured :D
We really have two different teams where I work. The firmware team is focused primarily on embedded development (we’re an IoT company). They have a very different process which is more waterfall- esque due to the difficulty associated with testing and updating some of those devices.
My team is the software team, most of our time goes into improving the web applications but we also do all the operations/security, documentation, requirements gathering. Sometimes I’m working on physics problems with the firmware guys or statistics with data science or helping streamline manufacturing.
So really we’re each involved in a lot of different initiatives. But all the work goes into Kanban so it’s easy to visualize what needs to get done and how resources are being utilized.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for writing them up twice my friend! Sounds like a tech debt Friday each week is really helpful man, nice idea!
Do you do any other side work besides dev? Does each dev only have responsibilities of feature work or are you responsible for different initiatives as well?
We used Kanban at my old team and I absolutely loved it. So much more efficient, less meetings, and still measured :D
We really have two different teams where I work. The firmware team is focused primarily on embedded development (we’re an IoT company). They have a very different process which is more waterfall- esque due to the difficulty associated with testing and updating some of those devices.
My team is the software team, most of our time goes into improving the web applications but we also do all the operations/security, documentation, requirements gathering. Sometimes I’m working on physics problems with the firmware guys or statistics with data science or helping streamline manufacturing.
So really we’re each involved in a lot of different initiatives. But all the work goes into Kanban so it’s easy to visualize what needs to get done and how resources are being utilized.