No Agile team needs an up-front UI/UX design. A proper cross-functional team has UI/UX skills on the team. The team sketches out the UI by collaborating with your customer as part of your iteration planning, just before you start implementing. 1/5
You flush out details by getting customer feedback as you're coding. ("Hey Fred, come over and look at this! What should I change?") 2/5
Same approach applies to the data model. You don't do it up front. The data model supports exactly what it needs to to get the current story working. No futureproofing to support mythical ad-hoc queries. 3/5
I'll add that you really need an architecture that supports an incremental way of working, or you'll be fighting your architecture all the time. In DDD systems (like microservices), each entity (service) is in control of its own data. There is no shared database. 4/5
So, the "model" is easily modified as you develop. There are no inter-module dependencies at the data level. OTOH, N-tier will be fighting you every step of the way. 5/5
