Mohamed Ali DHAOUEDI

• Designed a baseline of relevant feature assumptions by reviewing comparable solutions (TaskRabbit, Thumbtack, Houzz...) ✓ Designed 2 early MVP hypotheses : Service Catalog & On-Demand Services ✓ Facilitated collaborating with the CTO on delivery schedule based on addressable market constraints : speed & budget-friendliness • Narrowed prospect consumers into 3 segments : Small (mostly same-day) Fixes, Renovations (longer than 2 weeks), and Full Construction by conducting prospect interviews (≈30 interviews) ✓ Deprioritized Renovations and Full Construction segments from MVP (only about 5 prospects showed willingness to use a system) • Defined system boundaries by decomposing interactions across consumer mobile app, contractor mobile app, partner web portal, and administration web app via Interaction Overview diagrams ✓ Increased clarity & alignment across engineering perspectives reflected by shorter spike sessions • Proceeded with and refined the On-Demand MVP backlog around addressing the Small Fixes segment using ICE scoring ✓ ICE impact factor eliminated priority related ambiguities from refinement sessions • Prioritized ACL implementation over Saga workflow logic persistence for the MVP stage while designing Sagas (using State-Transition diagrams) in parallel to minimize later stages rework when accommodating business logic by workflow logic ✓ Enabled clearer estimation of later rework at around a 3 sprint timebox, deemed acceptable technical debt by the CTO • Designed and tested a 4 step GEMINI-assisted static test generation workflow enabling more focus on running thorough end-to-end tests ✓ Decreased static tests writing timebox from 5 days to 2 days per sprint (3 week sprints) • Adopted Sequence diagrams to define a fall-back policy per user story to emphasize an informative UX thus keeping users engaged, especially for the mobile UI layer ✓ Replaced all error indications on consumer-facing tool tips with guiding messages within a 3 sprint timebox

• Conducted interviews with end users & compliance representatives to structure my hypotheses ✓Distilled workshops’ notes into : User Experience as the main painpoint or Manual Reconciliation as the main painpoint • Leaned towards deferring User Experience in favor of Manual Reconciliation during Business Management workshops ✓Influenced stakeholders to deprioritize their early commitments, postponing the front-end layer during the early stages • Identified 3 systemic gaps in the client’s overpayment recovery flow : Traceability, Visibility, and Fragmentation ✓Defined addressing the Traceability and Fragmentation gaps as upstream to the Visibility gap • Prevented post-PI Planning scope changes by decomposing domain capabilities using UML Component diagrams ✓Confined post-PI Planning change requests to front-end enhancements within a 2 PI timebox, preventing structural rework • Remidiated Traceability gaps by separating feature’s Core Business Logic from Integration tasks using BPMN diagrams • Opted for and committed to Configuration-Driven Design (CDD) to enable full user control over grouping and classifying fragmented records ✓Product Leadership reported an expansion in addressable market segments to previously uneconomical European actors • Explicitly prioritized Traceability and Fragmentation over Visibility gaps using MoSCoW to orchestrate critical priorities • De-risked integration failures by defining inter-module exchange contracts & rules using MSON at user story level • Defined Business Entities lifelines and interactions by modeling UML Sequence diagrams per back-end user story ✓Reduced automated back-end services’ efforts from 5 days to 3 days, within a 2 PI timebox, per service • Addressed the delayed adoption by introducing Staggered Sprint Model, decoupling UI Design from Implementation • Continuously secured user approval by stressing each sprint increment against real-world end-user scenarios, during sprint reviews, as of the 2nd PI

• Anchored the solution vision by aligning market research to customer’s guidelines via an Opportunity Solution Tree ✓Identified the UI/UX layer of the existing application as a major bottleneck for user adoption ✓Reduced the period of Product Discovery and Scoping Phase from 3 months(estimated) to 2 months • Pipelined feature concepts into DoR-compliant backlog items by defining API request schemas in Acceptance Criteria ✓Decreased sprint planning timebox from 1.5 days to 4 hours (3-week sprints) within a 3 sprint timebox ✓Reduced post-sprint planning quality engineering spikes to 1 end-to-end scenarii workshop • Resolved conflicting stakeholders’ feedback via structuring competing inputs using Service Blueprint diagrams ✓Eliminated all orphan implementation issues (reduced to zero) within a 2 sprint timebox

• Built and managed 3 backlogs based on insights gathered during workshops with Sales & Marketing teams ✓Enabled consecutively publishing 3 add-ons on Microsoft Marketplace within a 6 month timebox ✓Increase in Marketplace visibility, thus brand credibility, reported by sales & Marketing teams

• Identified gaps in the Product Requirements Document (PRD) by designing an Excel-based analysis workbook ✓Enabled prioritizing gap agnostic Use Cases for updating the Software Requirements Document (SRD) and Test Suit