Hacker News new | past | comments | ask | show | jobs | submit login

That's a solid approach. I may try it with my teams too.

I always try to be very conscious of anything that will create / remove future interruptions in the decisions that we make around our work but haven't yet made a point to get "automate something" in regularly.




I've found it's far easier to build this into sprints/backlogs/whatever than rely on the team to automate on their own. Benefits include: better understanding of the problem, testing (is the automation robust, etc), and making time for formal sharing with other teams. Also, some developers want to automate, but might not feel enabled - they want to stick to the rules (sprint plan, etc).




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: