AGILE-scrum
Scrum:
When you use scrum for project management you form a team that will work together to quickly
develop and test a deliverable, the work is completed in short cycles and the teams meet daily to
discuss current tasks and clear up anything that’s blocking their progress.
The main idea behind Scrum and, ultimately, Agile is to continuously deliver value to customers.
Empiricism: The idea that true knowledge comes from actual, lived experience.
Product Backlog: The central artifact in Scrum, where all possible ideas, deliverables, features, or
tasks are captured for the team to work on.
Sprint: A time-boxed iteration in Scrum where work is done.
Daily Scrum: A meeting of 15 or fewer minutes every day of the Sprint.
Scrum ceremonies (Events):
 Sprint Planning: A scrum event where the backlog and sprint goal are established.
 Daily Scrum: A daily forum for team members to share progress and elaborate on what they are
working on for the day.
 Sprint review: A session where team reviews the work that was completed.
 Sprint retrospective: A meeting where the team reflects on progresses identifies areas for
improvements.
In Scrum, a Sprint Planning meeting is a key event that marks the beginning of a new Sprint. The
purpose of this meeting is to set the direction, goals, and plan for the upcoming Sprint. It typically
occurs on the first day of a Sprint and involves the entire Scrum Team, which includes the Product
Owner, Scrum Master, and the Development Team.
Here's an outline of what happens in a Sprint Planning meeting:
1. Time Frame: The meeting is time-boxed, meaning it has a predefined duration. ex: a 2-week
Sprint might have a Sprint Planning meeting scheduled for 4 hours.
2. Attendees:
- Product Owner: They present the prioritized Product Backlog items and answer any questions the
team may have about them.
- Scrum Master: Facilitates the meeting, ensures it stays on track, and helps resolve any
impediments or issues.
- Development Team: They are responsible for selecting the Product Backlog items they believe
they can complete in the upcoming Sprint.
3. Agenda:
- Review of the Previous Sprint: The Scrum Team discusses the outcomes of the previous Sprint,
including the completed and uncompleted Product Backlog items. This helps in understanding the
team's velocity and any lessons learned.
-Review of the Product Backlog: The Product Owner presents the top-priority items from the
Product Backlog.
- Clarifications and Questions: The Development Team can ask questions to clarify any aspects of
the backlog items. This is an important part of ensuring everyone understands what needs to be
done.
- Selecting Backlog Items: The Development Team, based on their capacity and velocity from
previous Sprints, collectively decides which items they can commit to completing in the upcoming
Sprint.
- Defining Tasks: For each selected backlog item, the Development Team may break them down
into smaller tasks or subtasks. This helps in detailed planning and tracking progress during the
Sprint.
- Estimations: The Development Team estimates the effort required for each task. Common
estimation techniques include story points, hours, or relative sizing.
- Commitment: Once the team has a clear plan and understands the work ahead, they make a
commitment to deliver the selected backlog items by the end of the Sprint.
4. Outcome: - At the end of the Sprint Planning meeting, the Development Team should have a
clear plan for the upcoming Sprint, including the selected Product Backlog items, tasks breakdown,
and estimates.
Remember, while the Development Team commits to delivering the selected items, this
commitment is not a guarantee. If unforeseen circumstances arise during the Sprint, the
Scrum Team can adjust their plan in the Sprint Review meeting or through a formal process
called "Sprint Cancelation."