Product Side SCRUM Processes
Scrum Phases (Project Lifecycle)
INITIATE phase should be covered over a 3 - 4 Week time period. (Cheat Sheet)
A project often doesn’t meet the deadline and turns into a failure when this phase is not given proper timelines.
Each Product Owner/Manager is supposed to give 4 Months Plan(Road Map)
Scrum Artifacts
Scrum Core Roles and Responsibilities
Scrum Process Explained
We first need to determine a Product Backlog (a list of product requirements in order of priority), which is the Product Owner's responsibility.
The Scrum Team makes estimates and arrangements for the workload based on the Product Backlog list in the Product Backlog Refinement Meeting.
With the Product Backlog list, we need to hold a Sprint Planning Meeting for defining the sprint goal of this iteration (the period of a Sprint is 2 weeks), then selected a list of user stories to form the Sprint Backlog for the coming sprint which could fulfill the sprint goal.
Sprint Backlog is completed by the Scrum Team, each member is refined into smaller tasks according to the Sprint Backlog (the workload of each task can be completed within a few days)
Within the Sprint, a Daily Scrum Meeting is required and each of the meetings is time-boxed in about 15 minutes. what you did yesterday, and commit what you want to accomplish today, and you can ask questions related to impediments or problems that you can’t solve. Then, update your Sprint burn-down Chart.
When all the user stories are completed, the Sprint Backlog is completed, which means that a Sprint is completed. At that time, we need to conduct a Sprint Review Meeting (also known as a review meeting). The product owner and the customer must participate. Every member of the Scrum Team will demonstrate to them the working software they have completed and this meeting is very important and must not be canceled.
Finally, The Sprint Retrospective is held after the sprint review at the end of each sprint. During the retrospective, the team self-identifies elements of the process that did or did not work during the sprint, along with potential solutions. Retrospectives typically last 60 minutes and are there to help us incorporate continuous improvement into our team culture and our Sprint cadence.
Summary
Scrum is an iterative and incremental framework for managing product development. It defines a flexible, holistic product development strategy where a development team works closely together o reach a common goal. It enables teams to self-organize by encouraging physical co-location or close online collaboration of all team members, as well as daily face-to-face communication among all team members and disciplines involved.
Four Months Plan
(Products only) (Quarterly)
Each Product Owner/Manager must provide a High-level Plan of four months, including the following.
Strategy & Market Roadmap — deals mainly with high-level details and market state.
Visionary Roadmap — outlines the vision of a product instead.
Technology Roadmap — a complete opposite of the previous two, a low-level technical roadmap for the production team.
Technology Across Product Roadmap — the mix between actual technologies/features planned for product/products.
Platform Roadmap — aimed at multiplatform digital products.
Internal & External Product Roadmap — tied to different types of audience.
Time-boxed Meetings
It should not be more than 15 minutes and this should be scheduled between 10 AM to 12 PM.
- Agenda for Daily Standup
~What did you do yesterday?
~What are your goals for today?
~Any blockers?Two Standups can be scheduled Internal Standup(Compulsory - so that the whole team is on the same page) and External Standup with the Clients/Stakeholders.
(Cheat Sheet) (https://shopdev.atlassian.net/wiki/spaces/SPM/pages/1713832692)
Twice a week 1 hour (Monday & Thursday) (Cheat Sheet)
(Tool https://support.appbox.ai/docs/backlog-prioritization-for-jira/)
2 Hours - 2weeks Sprint (Cheat Sheet)
Sprint planning is a recurring, just-in-time activity that takes place at the beginning of each sprint.
Each sprint should be kicked off on Alternative Tuesdays.
30mins to 1hr - 2weeks Sprint (with this new tool it can be reduced to 15 min) (Online tool) (Cheat Sheet) (Retro Sample Template). https://shopdev.atlassian.net/wiki/spaces/SPM/pages/1713832612
When Creating a report search in templates “Sprint End Report and Kickoff Plan”, use that custom template.https://shopdev.atlassian.net/wiki/spaces/SPM/pages/1575288833
After the Sprint planning meeting, and Sprint Retrospective meeting, Sprint End Report, and Kickoff Plan is made & shared. (use Confluence to save each report and document everything)
2Hours - 2weeks Sprint (Cheat Sheet) Sprint End Report and kickoff Plan, Demo Slides are presented
Project Retrospective report is made and shared with the internal and external team. - Project Retro Sample - CheatSheet - Online Tool - https://shopdev.atlassian.net/wiki/spaces/SPM/pages/1713832612
Create a new Project on JIRA
JIRA Project is created as soon as the SCRUM team is formed.
https://shopdev.atlassian.net/l/c/P8u3ZJfU
Create WorkFlow
https://shopdev.atlassian.net/wiki/spaces/PMS/pages/1588101166/How+to+Create+WorkFlows#Products
Confluence setup
https://shopdev.atlassian.net/wiki/spaces/SPM/pages/1505427527 – (All meeting minutes will be saved on confluence)
Create Dashboard
https://shopdev.atlassian.net/l/c/u8ujSkfA
Create JIRA FIlter for Daily Updates
Time Logging Activity
https://shopdev.atlassian.net/l/c/aDgwxrGE
Integrating Slack with JIRA
https://shopdev.atlassian.net/l/c/QLQqyPcN
How-to Articles
https://shopdev.atlassian.net/l/c/o0AWtTsC
Tools
https://shopdev.atlassian.net/wiki/spaces/SPM/pages/1713832599