The class visited the customer site, Engestofte Gods. I could not attend, so I will be straight about that rather than reconstruct a day I was not part of.
Building for a context I knew second-hand#
The team came back with a feel for the setting: the scale of the market, the kind of stall-holders who apply, practical constraints that do not show up in a requirements document. My job was to turn that into software without the first-hand impression, which meant leaning harder on the written material and the user stories, and asking the team the questions a site visit would have answered for me directly.
What the trip fed in#
The visit is where the framing came from: a real organiser, a real overload of email applications, a real need for a public approved-list and segmented communication. Even second-hand, that grounding is why Standflow solved an actual problem rather than an imagined one.
Where the project stands#
All seven user stories are built and merged, the backend suite passes, and the app is deployed and reachable at standflow.roneu.dk. Since the excursion the work has been integration and polish rather than new features: the admin control panel now has a per-application detail view, search, filtering, sorting and CSV export, and there is an internal stall-holder overview alongside the public one. What remains on the list is file upload for stall photos and site plans, which needs the type and size validation described in the security post before it goes anywhere near production.
Takeaway#
Not being there made me more dependent on good specs and good team communication, which, given that half this course is about exactly that, turned out to be a useful constraint rather than only a missed day.