https://www.pentoz.com/tech/the-agile-scrum-framework/
The Agile Scrum Framework
Scrum is a structure which depends on light-footed standards, a system that handles basic, muddled and complex programming advancement.
Scrum depends on a nonstop change in item and process.
Scrum convey programming much of the time (esteem) and it exhibits the shrouded issues in framework advancement.
In a scrum, venture to push ahead with the arrangement of emphasis called Sprints. Each dash measure is commonly two to a month long.
Scrum Roles :
The accompanying is the parts in Scrum:
Product Owner
Scrum Master
Scrum Group
Product Owner:
Product Owner (PO) is customer’s illustrative.
Characterize highlights of the item.
Choose discharge date and substance.
Needs include as indicated by advertising esteem.
Be in charge of the productivity item.
Acknowledge or reject work things.
Scrum Master:
Mentor for scrum group.
Establishing scrum esteems.
Guarantee group’s efficiency.
Manufacture winning group.
Apply deft standards and make framework successful.
Group:
5-9 Members group (Developer, Tester).
Self-arranging, High-execution group.
Assemble winning item.
Work cooperatively and share duties.
Cross practical group.
Scrum Activities:
Sprint Planning
Daily Scrum
Sprint Review
Sprint Retrospective
Product Backlog Refinement
Sprint Planning:
Goal: Team to plan and agree on backlog items they can complete and confirm the tasks required to support acceptance.
Who: Scrum Team, Scrum Master, Product Owner.
When: Beginning of the Sprint.
Duration: 4 Hours for 2 weeks’ sprint.
How: In 2 parts.
Part 1: Define what needs to be done.
Part 2: How to achieve a goal.
Input: Priority, Product Backlog, Acceptance criteria, Capacity.
Description:
Product owner presents the backlog items in priority order for review.
Review and clarify user Backlog items/stories.
Breakdown larger stories and each story into task and acceptance criteria.
Task are estimated in hours by the team.
Developer and tester assigned to a task.
The process continues until all available hours are used for the sprint.
Daily Scrum:
Goal: Plan for the day, Inspect and Adapt daily towards reaching the sprint goal.
Who: Scrum Team, Scrum Master.
When: Daily throughout the sprint.
Duration: 15 minutes’ maximum.
How: Team members form a group to focus on the daily plan, discuss issues faced yesterday.
Input: Current status, risks, and do work.
Output: Plan for the day, task to work.
Description:
Daily development Team stand-up for 15 minutes in a circle and talk only on three points.
What did I do since last daily scrum meeting?
What am I planning to work on today?
(Issue/blocker) if any?
Scrum master protects the team and facilitates being effective.
Sprint Retrospective:
An Agile retrospective is a meeting that’s held at the end of an iteration in Agile software development (ASD). During the retrospective, the team reflects on what happened in the iteration and identifies actions for improvement going forward.
Goal: To inspect and adapt to become more effective and efficient in the process, people, culture aspect.
Who: Scrum Team (anyone participation is decided by the scrum team on an invite basis only).
When: Last day of the sprint.
Duration: 2 hours for a 2-week sprint.
How: Close room discussion of observer pattern and desire results/improvements.
Input: Observation, issues, experience, the pattern of behavior, recommendations, feedback, and information.
Output: List of activities/steps/suggestions that help to make more effective and efficient. Action items on the team
Product Backlog Refinement: Description:
Product owner provides clarity on each product backlog item (All uncertainty clarified into certainty).
Product owner update product backlog. 100% be present and involve all team members.
The team understands, carefully listen to the need of product owner, understand the acceptance criteria. Help product owner to order the backlog.
Scrum Information Radiators: Task boards:
Task boards allow transparency, display what is the live status of the teams work and focus area
Simple task board has a backlog, To-do, in progress and done status.
There is a various format.
Team design their best “Information Radiators” that helps them in self-organizing.
Burn down Chart For a current sprint, it shows the total estimated work remaining for the entire forecasted sprint backlog against time:
Updated by a team, regularly and continuously.
Independent of the work, it represents total remaining estimated time to market to achieve sprint goal.
This is how sprint and Scrum works.
