{"id":469,"date":"2024-06-18T22:34:13","date_gmt":"2024-06-18T21:34:13","guid":{"rendered":"http:\/\/localhost:8082\/?p=469"},"modified":"2024-09-18T11:08:07","modified_gmt":"2024-09-18T10:08:07","slug":"how-agile-product-teams-can-adopt-a-ux-centric-approach","status":"publish","type":"post","link":"http:\/\/localhost:8082\/2024\/06\/18\/how-agile-product-teams-can-adopt-a-ux-centric-approach\/","title":{"rendered":"How agile product teams can adopt a UX centric approach"},"content":{"rendered":"\n

Cross-functional product teams can be very confusing places to work, particularly as a Business Analyst.<\/p>\n\n\n\n

You are expected to collaborate with customer experience, user experience and service design; whilst also being the primary point of contact for the agile development team, sometimes filling in as the Scrum Master too.<\/p>\n\n\n\n

It’s demanding work for the Business Analyst, and that’s when everything is going well. Unfortunately, the situation is also ripe for dysfunction and the personal cost can be very high indeed.<\/p>\n\n\n\n

Customer experience, user experience and service design are a confluence of new disciplines that weren’t around when agile first appeared, and this explains some of the difficulties we see in contemporary agile teams.<\/p>\n\n\n\n

Agile product development that follows a UX centric approach can be tricky to get right, however, you can significantly improve your chances by following a few best practice guidelines.<\/p>\n\n\n\n

These include:<\/p>\n\n\n\n