[Syed.Atyab@Codeline.rihal.om] Contact Clarifier: One-Page Team & Sprint Cheat-Sheet

[CodelineAtyab]

User Story: “Team Contact & Agile Cycle” Web Page

As a Product Owner, I want a lightweight “Team Contact & Agile Cycle” web page so that business stakeholders and new team members can quickly understand who to talk to, when to talk to them, and how our 2-week sprint cadence flows—thereby reinforcing clear role boundaries and reducing random requests to developers.

---

🎯 Acceptance Criteria

#	Requirement
1	Technology Stack: Single-page, responsive web app built with HTML, CSS, vanilla JavaScript (no frameworks).
2	Visual Sections (clearly separated):   a. “Who to Contact” diagram (SVG/PNG).     • Flow: Business ➜ Product Owner ➜ Project Manager ➜ Core Team.     • One-sentence role description under each node.   b. “Sprint Timeline”: horizontal timeline of the five ceremonies with brief tooltips.
3	Editable Sprint Data: Small input form to change sprint length (default = 2 weeks) and current sprint start date. Updates auto-recalculate ceremony dates.
4	Assets & CI/CD: All images/CSS/JS stored in repo. Push to main triggers a CI job (GitHub Pages / Netlify) that deploys to a public URL.
5	Responsive Design: Renders correctly on • Desktop ≥ 1024 px • Mobile ≤ 480 px (no horizontal scroll).
6	Accessibility: Semantic HTML, alt text, tabbable interactive elements.
7	Documentation: README.md covering local run instructions, sprint parameter changes, and stakeholder usage guidelines.
8	Cross-Browser QA: Verified in Chrome, Edge, Firefox that inputs update dates correctly and all links/tooltips function.

---

📊 Section Details

1. “Who to Contact” Diagram

Role	One-Sentence Responsibility
Business Stakeholder	Articulates business goals & outcomes.
Product Owner	Translates goals into product backlog & priorities.
Project Manager	Aligns resources, timelines, and risk management.
Core Team (Dev, QA, UX)	Delivers increment that meets Definition of Done.

2. “Sprint Timeline” (Default 2-Week Cadence)

Day	Ceremony	Tooltip (example)
−3	Backlog Refinement	Groom items for next sprint.
0	Sprint Planning	Commit to sprint goal & stories.
1-9	Execution	Build, test, and review daily.
10	Sprint Review	Demo increment & gather feedback.
11	Sprint Retrospective	Inspect & adapt team process.

(Dates auto-update when sprint parameters change.)

---

✅ Deliverables Checklist

• Fully responsive single HTML file with embedded or linked CSS & JS.
• SVG/PNG “Who to Contact” diagram.
• Dynamic timeline with editable inputs.
• Accessibility audit passed.
• CI/CD pipeline configured (GitHub Pages / Netlify).
• Comprehensive README.md.
• QA sign-off in Chrome, Edge, Firefox.

---

End of User Story