Introduction
As the team grew, so did the number of meetings and repetitive tasks. We used to have two sync meetings a day, one in the morning and one in the afternoon, which felt like a waste of time because we'd have to sync up again before we had even finished our work. After a discussion with my boss, we decided to adopt Scrum.
Purpose of Adopting Scrum
- To reduce repetitive meetings.
- To have the team focus on bi-weekly deliverables. When users see updates every two weeks, they won't feel the need to constantly chase us for progress.
- Continuously receiving feedback from customers or stakeholders helps the team understand requirements and make corresponding adjustments.
- To identify problems sooner. Issues can be raised and resolved during daily meetings (e.g., progress, incorrect work item estimates).
- To help everyone understand the purpose and value of their work, not just focus on the task at hand.
- To make team operations smoother.
- To increase transparency.
Adjustments to Meetings
1. Morning Sync with US Colleagues
This meeting is optional. We don't discuss the specifics of our work, only matters that require coordination or assistance with our US colleagues.
2. Planning Meeting (Bi-weekly): To decide which items to complete in the upcoming sprint (led by the PM).
(Held on the first day of every two-week cycle. Considering that the current members are all new, we will temporarily skip story point estimation to avoid spending too much time on it.)
3. Daily Stand-up Meeting: Daily Scrum
A 10–15 minute meeting each day that must not run over time. The goal is to keep the team in sync. (Please update your Jira ticket statuses beforehand.)
- What did I complete yesterday?
- What will I do today?
- Are there any impediments in my way? What are they?
4. Bi-weekly Review Meeting: To demonstrate the results of the current sprint and gather feedback and new requirements.
(Held on the first day of every two-week cycle. We use a rotating system for demos. Everyone is expected to learn how to integrate the work, as this is when we often discover blind spots in our code design.)
P.S. Agile methodologies are often adapted to fit a company's specific situation; they are rarely applied directly out of the box. Due to the current high number of meetings, we are temporarily skipping the retrospective meeting.
Comments