Islam Magdy

The team I lead at Nationale-Nederlanden is seven people: four engineers, a UX designer, and customer-journey specialists, sharing one backlog and one roadmap. It is cross-functional by design, and the design only works if you resist rebuilding the silos inside the team.

Three things change when the team is not all engineers:

• The backlog speaks in outcomes, not tickets. A customer-journey specialist brings problems ("mortgage customers abandon the redemption flow at step three"), not solutions. An engineer-owned backlog would have turned their input into feature requests; a shared one keeps it as evidence.
• The roadmap conversation has a translator built in. Trade-offs get argued in customer impact and engineering cost at the same table, in the same meeting — not over a wall between two backlogs that never quite line up.
• Quality includes the journey. When the people who mapped the journey sit in the stand-up, "works as built" and "works for the customer" stop being different definitions of done.

The cost is real: shared context takes longer to build, and estimation across disciplines is harder to compare. The return is that the team owns a problem end to end — which is the only unit that can modernize something as tangled as a mortgage-servicing platform without dropping the seam between disciplines.