Project Management Methodology
Chosen Methodology: Agile (Scrum Framework)
Section titled “Chosen Methodology: Agile (Scrum Framework)”We use the Agile methodology, following the Scrum framework, to ensure flexibility, collaboration, and continuous delivery of working software.
Why Agile for Sport Live Feeds?
Section titled “Why Agile for Sport Live Feeds?”- Requirements may evolve after stakeholder feedback.
- Frequent delivery allows us to adapt quickly.
- Encourages transparency, communication, and accountability.
- Short iterations keep progress measurable and visible.
Why Scrum Instead of Alternatives?
Section titled “Why Scrum Instead of Alternatives?”- Waterfall: Sequential and rigid, not ideal since requirements evolved after stakeholder reviews.
- Scrum: Balanced approach—short sprints, clear roles, structured reviews, and room for continuous improvement.
Scrum therefore enabled us to deliver incremental value while adapting quickly to evolving feedback.
We work in two-week sprints, providing enough time for meaningful progress while maintaining rapid feedback loops
Section titled “We work in two-week sprints, providing enough time for meaningful progress while maintaining rapid feedback loops”Scrum Process
Section titled “Scrum Process”- Product Owner – Represents stakeholder interests and prioritizes backlog.
- Scrum Master – Facilitates ceremonies, removes blockers.
- Development Team – Builds, tests, and delivers product increments.
Ceremonies
Section titled “Ceremonies”- Sprint Planning – Define sprint goals, select backlog items, estimate work.
- Daily Standups – Quick syncs to report progress and highlight blockers.
- Sprint Review – Demo completed features to stakeholders and gather feedback.
- Sprint Retrospective – Identify improvements for the next sprint.
Stakeholder Interaction
Section titled “Stakeholder Interaction”- Tutor Reviews: At the end of each sprint, we demoed progress to our tutor.
- Example: After Sprint 2, tutor feedback suggested enhancing database schema for better player/team linking. We adapted in Sprint 3.
- Transparency: Regular updates through Whatsapp messages,Discord Meetings and shared Notion boards ensured the tutor was always aware of project status.
Workflow Diagram
Section titled “Workflow Diagram”Backlog → Sprint Planning → Development → Daily Standups → Sprint Review → Retrospective → Next Sprint
Tools Used
Section titled “Tools Used”- Notion – Central hub for sprint boards, backlog, and documentation.
- Discord – Async communication, quick updates, and stakeholder coordination.
- Whatsapp – for easy and more frequent communication and updates
Workflow Structure
Section titled “Workflow Structure”Sprint Length
Section titled “Sprint Length”- Each sprint runs for 2 weeks.
Planning and Meetings
Section titled “Planning and Meetings”| Meeting | Frequency | Format | Purpose |
|---|---|---|---|
| Sprint Planning | Every second Tuesday | In-person | Plan the sprint, estimate tasks |
| Sprint Check-ins | 3x per week | Discord | Review progress, unblock teammates |
| Sprint Review | Every Day | In-person/Discord/Whatsapp | Discuss features, collect feedback |
| Retrospective | End of sprint | In-Person on Sprint Marking | Reflect on process, define improvements |
Proof of Agile in Action
Section titled “Proof of Agile in Action”Below are real examples of how Agile was applied in our project:
1. We maintain our project board in Notion:
Section titled “1. We maintain our project board in Notion:”- Shows user stories, priorities, and tasks awaiting scheduling.
2. Sprint Planning
Section titled “2. Sprint Planning”- Estimate work, assign tasks, define sprint goals
3. Daily Standups
Section titled “3. Daily Standups”- Our Daily check ins to report progress and make sure everyone is up to date with work
4. Sprint Review(Stakeholder Interaction)
Section titled “4. Sprint Review(Stakeholder Interaction)”- Demo completed features to stakeholder(tutor) and gather feedback.
5. Retrospective
Section titled “5. Retrospective”- Identify what went well for this sprint and improvements for the next sprint
Definition of Done (DoD)
Section titled “Definition of Done (DoD)”- Code reviewed and merged.
- Feature tested and passes QA.
- Documentation updated.
- Stakeholder acceptance obtained.
Continuous Improvement
Section titled “Continuous Improvement”- Retrospective action items applied in next sprint.
- Regular evaluation of workflow and tools.
- Experimentation with new practices for efficiency.
Review of Methodology
Section titled “Review of Methodology”What Worked Well
Section titled “What Worked Well”- Short sprints kept progress visible and manageable.
- Notion and Discord made task tracking and communication effective.
- Regular reviews gave the tutor confidence in progress.
Challenges Faced
Section titled “Challenges Faced”- Team sometimes struggled with sprint deadlines.
- Daily standups were occasionally missed due to scheduling conflicts.
- Scope creep when new features were suggested mid-sprint.
Improvements for Future
Section titled “Improvements for Future”- Stronger sprint planning with clearer task estimates.
- Automating testing and deployments earlier.
References
Section titled “References”- Agile Manifesto: https://agilemanifesto.org/
- Scrum Guide: https://scrumguides.org/
- Astro Docs: https://docs.astro.build/
- Atlassian Agile: https://www.atlassian.com/agile