Prathima's Miles & Milestones

For Product & Project Teams

• Agile is an umbrella of principles for both the Project & Product teams to adhere to in line with one another in delivering a successful product in a bi-weekly sprint (here in this context)
• By default, Product teams are always 1–2 sprints ahead as the roadmap, planning, and ruthless prioritisation are done with the stakeholders of various divisions & agreed upon.
• The prioritisation of EPICS in AHA is usually done at a higher level of stakeholders, with the PMs, which is usually called a BRP (Big Room Planning)
• The result of BRP consists of a prioritised epic for a 120-day release timeline.
• Before BRP, each team internally works with the Program Manager to ensure that the epics have all details/requirements in AHA, dependencies wrt various teams, major blockers, etc. This session is called SRP (Small Room Planning)

Mission Mondays 
Set the tone, align on sprint goals and direction, & kickstart sprint energy

• Tech — Daily Standup: Quick sync for the tech team to share progress, blockers, and plans for the day.
• Product & Design Standup: Short check-in to align product and design priorities, clarify requirements, and plan next steps.
• Design Updates & Reviews: Dedicated time for walkthroughs, feedback, and reviews of ongoing design work to ensure consistency with sprint goals.

Teamwork Tuesdays 
Focus on collaboration and cross-pod sync

• Tech — Daily Standup → Quick sync to share progress, blockers, and next steps.
• Sprint Demo → The team showcases completed work to stakeholders, gathers feedback, and ensures delivered features meet expectations.
• Production Release / Sprint End → Wrap up the sprint, release planned work, and review what was delivered.
• Mobile Team Refinement – 1 → Break down upcoming stories, clarify requirements, and get backlog items sprint-ready.

Workflow Wednesdays 
Focus on process check-ins, cross-team dependencies

• Tech — Daily Standup → Quick check-in for engineers to share progress, blockers, and coordinate work.
• Product & Design Standup → Sync on design updates, product priorities, and align on sprint goals.
• Bi-weekly Sprint Planning → Plan upcoming sprint, refine backlog items, and commit to prioritised work.

A sample agenda of a Bi-weekly Sprint Planning Meeting
 — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —
Hello,

Subject: Welcome to the Mobile Team Sprint Planning Session

Agenda:
1. Discuss achievements and carry over from the previous Sprint
2. Plan commitment for the next Sprint (assign, estimate)
3. Agree on a Sprint Goal
4. Discuss risks and the team’s availability(Eg: Days off, holidays)

Outcomes:
– Updated Sprint Backlog

Thanks,
Jane Doe

— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —

Task Thursdays 
Break down, estimate, and align on sprint tasks

• Tech — Daily Standup → Quick sync on progress, blockers, and priorities.
• Bi-weekly Sprint Retrospective → A reflection session where the team shares appreciations, discusses what didn’t go well, suggests improvements, debates on those suggestions, agrees on final decisions, and notes actionable items to be implemented in the next sprint.
• Thinking Thursday → Space for innovation, knowledge sharing, or exploring new ideas that can add value to the product.

A sample agenda of a Bi-weekly Sprint Retrospective Meeting
 — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — —

Hello,

Agenda: Let’s meet and reflect on what went well and what could be improved in the next Sprint.

Please add retro and actions here — Miro Board link

All notes and actions from the meeting will be saved here

Thanks, 
Jane Doe

— — — — — — — — — — — — — — — — — — — — — — — — — — — — — —

Focus Fridays
Reserved for deep work, spikes, estimates, closing stories, or backlog cleanup

Mobile Team Refinement — 2 → The mobile team reviews upcoming backlog items, clarifies requirements, estimates effort, and ensures stories are well-defined and ready for future sprints.