{"entity":"Acme Supplies SRL","reference":"WMS-2026 --- Phase 3 (Build and configure) retrospective","retro_type":"phase","retro_date":"2026-08-18","facilitator":"Sophie Dubois","participants":[{"name":"Sophie Dubois","role":"Programme Manager"},{"name":"Paolo Bianchi","role":"IT Lead"},{"name":"Anouk Jansen","role":"Business Analyst"},{"name":"Mark De Vos","role":"Warehouse Manager"},{"name":"Julie Leroy","role":"Procurement Lead"},{"name":"Nordstrand Fulfilment BV PM","role":"Vendor lead"},{"name":"Elena Rossi","role":"Head of IT"}],"what_went_well":["Carrier adapter abstraction absorbed the CR-007 (GLS) integration without schedule impact on the critical path --- a clear architectural win.","Master-data migration completed 3 days ahead of plan thanks to early fixture work from the business analyst team.","Vendor responsiveness was high: no change requests waited more than 48 hours for a technical response.","The warehouse change-champion network engaged operators early and absorbed most of the pilot-run feedback before formal training.","Weekly PM-to-PM syncs with the vendor kept defects from leaking into the test phase."],"what_didnt":["Sage ERP load-test readiness slipped by 10 days (T3.3 variant) because of a late environment provisioning in Sage.","Specification of the returns-module edge case was ambiguous and produced rework in weeks 11 and 12.","Hand-held hardware delivery was split across two batches, causing a temporary training-room shortage.","UAT scenario library was drafted late in the phase; we should have reused the vendor's baseline library from day one.","Daily stand-ups drifted into 45-minute status meetings by week 14 --- lost their purpose as a blocker-clearing forum."],"lessons_learned":["Provision non-functional test environments (ERP, DC network) two weeks before the first integration is needed; add this to the next project's planning checklist.","Reuse the vendor's UAT baseline and then extend it, rather than write from scratch; saves about two weeks.","Hard-timebox the daily stand-up to 15 minutes; anything longer is a working session booked separately.","Split returns-flow specification into a dedicated decision document with one accountable owner before any build starts.","Publish a 'carrier integration pattern' one-pager; it proved highly reusable and will save time on future carrier onboardings."],"action_items":[{"id":"RA-001","action":"Add 'non-functional environment provisioning +2 weeks' to the default project checklist template.","owner":"Sophie Dubois","due":"2026-08-29"},{"id":"RA-002","action":"Publish the 'carrier integration pattern' one-pager to the engineering handbook.","owner":"Paolo Bianchi","due":"2026-09-05"},{"id":"RA-003","action":"Hard-reset the stand-up format: 15-minute timebox, separate clinic time for working sessions.","owner":"Sophie Dubois","due":"2026-08-25"},{"id":"RA-004","action":"Draft a decision document for the returns-flow edge case and assign a single owner.","owner":"Anouk Jansen","due":"2026-09-10"},{"id":"RA-005","action":"Request the vendor's UAT baseline library up front for every future integration project.","owner":"Julie Leroy","due":"2026-09-15"}],"keep_doing":["Weekly PM-to-PM syncs with the vendor.","Carrier adapter architectural pattern.","Change-champion network inside the warehouse."],"stop_doing":["Allowing stand-ups to drift past the 15-minute timebox.","Starting specification of edge cases inside build sprints rather than before them."],"start_doing":["Provisioning non-functional environments ahead of the first integration need.","Reusing vendor UAT baselines rather than writing from scratch.","Publishing reusable architectural patterns to the handbook as soon as they prove out."],"overall_sentiment":"mixed","next_review":"2026-10-20"}