C1: Requirements Gathering

Challenge Info

⏱️ 30 min · 🏆 20 pts · 🤖 02-Requirements · 📄 agent-output/freshconnect/01-requirements.md

Objective

• Do now: Turn the FreshConnect scenario into an Azure-ready requirements document.
• Input: Scenario brief from Workshop Prep.
• Output: agent-output/freshconnect/01-requirements.md.
• Required to move on: Scope, NFRs, compliance needs, and budget constraints.
• Decisions now: SLA target, RTO/RPO, authentication model, EU data handling.
• Next: C2 uses this file to choose services and justify architecture trade-offs.

This challenge creates the decision baseline for the entire workshop. If C1 is vague, every later challenge becomes guesswork.

The Business Challenge

Nordic Fresh Foods needs cloud infrastructure for FreshConnect, a Stockholm-based farm-to-table delivery platform serving 500+ restaurant partners and 10,000 consumers. Peak seasons can hit 3x normal load, the MVP budget is about €500 per month, launch is in 3 months, GDPR keeps customer data in the EU, and the small team needs managed services they can actually operate.

Out of Scope

API Management (APIM) is out of scope for this POC due to time constraints.

Your Tasks

1. Review the scenario and write down the business constraints you cannot ignore: scale, budget, timeline, compliance, and team capacity.
2. Prompt the 02-Requirements agent with that context and let it surface gaps, trade-offs, and open questions.
3. Refine the output until the document clearly separates functional requirements, non-functional requirements, operational expectations, and compliance needs.
4. Save the final document at agent-output/freshconnect/01-requirements.md.

Key Decisions

• What level of downtime can FreshConnect accept before orders, partners, or brand trust are affected?
• What data loss window is acceptable if a failure happens during peak ordering?
• Which users need different authentication or access controls: internal staff, restaurant partners, and consumers?
• What must stay in EU regions from day one, and what can wait for a later phase?

Deliverables

• agent-output/freshconnect/01-requirements.md
• Project overview with business purpose, timeline, and budget.
• Functional requirements for the platform capabilities that must exist at MVP.
• Non-functional requirements covering SLA, performance, scalability, RTO, and RPO.
• Compliance and operational expectations, including GDPR, monitoring, backup, and support assumptions.

Success Criteria

Focus	What good looks like	Evidence
Business context	The document reflects the real FreshConnect constraints instead of generic cloud goals	Purpose, users, scale, budget, and launch timing are stated clearly
Functional scope	The MVP capabilities are concrete enough for architecture decisions	Required capabilities are listed without mixing in phase-2 ideas
Operational targets	Reliability and recovery expectations are explicit	SLA, RTO, RPO, and support expectations are documented
Compliance and cost	Non-negotiable boundaries are visible early	EU residency, GDPR impact, and budget guardrails appear in the final doc

Watch Out

• Do not let the agent fill the page with generic requirements that are not tied to FreshConnect.
• Do not skip budget or operational assumptions just because the business brief feels incomplete.
• Do not turn unresolved questions into fake certainty; mark them as assumptions if needed.
• Do not optimize for technical preference over business need.

Artifact Handoff

Item	Value
Input from	Scenario brief (Workshop Prep)
Your output	agent-output/freshconnect/01-requirements.md
Next challenge uses	C2 reads this file to choose services, assess trade-offs, and build the architecture diagram

Next Step

Challenge 2 uses this requirements document as its source of truth. If a later design choice is hard to defend, the first place to check is whether C1 captured the right business constraint.