Today, he doesn’t wait until the handoff to show developers his designs. He includes his counterparts from the beginning. Both he and Mattison agree that the lead developer attends the first round of client meetings. Getting feedback about the user experience directly helps them understand why resources are being prioritized. Plus, the practice of inclusion dismantles elitism in both roles.
Of course, Developers can adapt “rubber ducking” – a debugging method where one explains a problem line by line – when breaking down technical work for a designer. Stand-ups can be an opportunity to identify what needs further explanation.
While designer practices don’t always align with Agile, Loftis america phone number list and Mattison strongly recommend everyone attends stand-ups, sprint reviews, and sprint demos. “That will influence the next iteration of design,” said Mattison. “The whole point of doing Agile is to have a short feedback loop, right? You never get too far.” Working as one creates a different culture than working in kingdoms that can foster elitism.