We have the luxury of having a good UX/UI designer on the team so I am happy to defer to her on design questions. These should be spec'd out in the Trello card

We have the luxury of having a good UX/UI designer on the team so I am happy to defer to her on design questions. These should be spec'd out in the Trello card as a checklist and mockups attached in an easily readable format so that any questions can get addressed and hashed out in the grooming meetings. In teams without a designer, I'd recommend picking a well-documented frontend framework like Bootstrap to establish a baseline and make sure there's a functional UAT process in place. As far as getting a process in place, I agree it's challenging. Scrum provides a great foundation. But as the regular threads on scrum in Hacker News show, many orgs adopt it without really appreciating how it all fits together and as a result there's a good amount of well-earned resistance to it. At a previous company, we initially brought in a consultant for three days of in-house training. I believe it was money well spent. But we still managed to screw it up in critical ways. I think establishing and documenting best practices is important, for both process and coding. I'm a big fan of checklists and transparency generally. A lot of my effort goes toward establishing consistency and eliminating surprises. There's also the Joel Test, which is another good way to measure dev team health and smooth out some aspects of the dev process: https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/ https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-s...