Skill Development: Simplify Agile Scrum Methodology

Agile Scrum Methodology / framework is more disciplinary way of working

My Notes: by Kishor Kumar Bhatia
working in this document

Agile Vs Waterfall Method

http://developmentengineering.blogspot.in/2017/07/agile-vs-waterfall-method.html

Agile Scrum is a popular framework for agile project management that emphasizes collaboration, flexibility, and iterative development. It is widely used in software development but can also be applied to various other industries and projects. Agile Scrum is known for its structured approach to delivering high-value increments of work within short time frames, known as "sprints."

Key components of Agile Scrum include:

Scrum Team:
- Product Owner: Represents the stakeholders, defines the product backlog, and prioritizes user stories.
- Scrum Master: Facilitates the Scrum process, ensures the team follows Scrum principles, and removes impediments.
- Development Team: Cross-functional group responsible for designing, developing, testing, and delivering increments of work.
Product Backlog: A prioritized list of user stories, features, and requirements that represent the work to be completed.
User Stories: Brief descriptions of functionality from the perspective of an end-user. User stories capture the what and why of a feature.
Sprint Planning: At the beginning of each sprint, the team selects items from the product backlog to work on during the sprint. The team breaks down the selected items into smaller tasks.
Sprint: A time-boxed period (usually 2-4 weeks) during which the team works on completing the selected items from the product backlog.
Daily Standup (Daily Scrum): A short daily meeting where team members provide updates on their progress, discuss any obstacles, and plan their work for the day.
Sprint Review: At the end of a sprint, the team demonstrates the completed work to stakeholders and receives feedback.
Sprint Retrospective: A meeting held after the sprint review where the team reflects on what went well and what could be improved. Changes are made for the next sprint.
Increment: The sum of all work completed during a sprint, including all features, user stories, and tasks.
Definition of Done: A set of criteria that must be met for a product increment to be considered complete and ready for release.
Burndown Chart: A visual representation of the remaining work in the sprint backlog. It helps the team track progress and adjust their efforts accordingly.

Agile Scrum's iterative approach allows teams to adapt to changing requirements, deliver value early and frequently, and gather feedback from stakeholders to refine the product. It promotes collaboration, self-organization, and a focus on delivering the highest priority items first.

It's important to note that Scrum is just one of many agile methodologies. While it's widely used and effective, organizations may also consider other agile frameworks like Kanban, Extreme Programming (XP), or Lean to best suit their specific needs and project characteristics.

What is Agile

Definition of Agile

Agile development methodology is an Iterative, Incremental and flexible approach to software development with a potentially shippable Product ‘developed every sprint/Iteration

Iterative & Incremental

Iteration = sprint

Iteration and sprint mean is same word iteration is come from xp framework and sprint word come from scrum

Iterative

· Develop Through repeated cycles

· Start simple, expecting to change

Incremental

· Develop smaller portions at a time

· Gradually Build up Functionality

Where AGILE

Agile is not restricted to any ISV independent software industries.

Agile Scrum way of working

Three Pillars of Scrum

Shortcut to remember - VIA
V- Visible = Transparency
I- Inspection
A- Adoption

Five Scrum Values

Tricks to remember - C-FORC

C- Commitment
F- Focus
O- Openness
R- Respect
C- Courage

Scrum Roles

Scrum Team – Scrum master + Product Owner + Development Team they are called as PIG and other are chicken

Scrum Roles

Trick to Remember scrum Roles - TPM

T- Team (Development Team)
P- Product Owner (PO)
M- Master (Scrum Master) (SM)

Scrum Team = T+P+M

Scrum Event

Event are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum.

The Sprint

a time-box of one month or less during which a “Done”, useable, and potentially releasable product Increment is created.

Cancelling a Sprint

Only the Product Owner has the authority to cancel the Sprint, A Sprint would be cancelled if the Sprint Goal becomes obsolete.

Sprint Planning

Plan is created by the collaborative work of the entire Scrum Team. Sprint Planning is time-boxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.

Daily Scrum

The Daily Scrum is a 15-minute time-boxed event for the Development Team to synchronize activities and create a plan for the next 24 hours.

Daily Stand-up Meeting

Sprint Review

Held at the end of the Sprint, This is a four-hour time-boxed meeting for one-month Sprints. For shorter Sprints, the event is usually shorter.

Sprint Retrospective

The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning. This is a three-hour time-boxed meeting for one-month Sprints.