Agile and Scrum
1. What is the relation between Agile and Scrum>
2. Scrum Roles
3. Scrum Events
4. Scrum Artifacts
5. Symptoms of Waterfall + Agile
6. Scrum Process
-----------------------------------------------------------------------------------------------------------------------------
1. What is the relation between Agile and Scrum
Scrum is one of the strategy by which we can implement Agile methodology.
Scrum: A framework within which people address complex adaptive problem to deliver product of its highest possible value.
Sprint backlog items - Task
Product Backlog items - Features/ User stories
-----------------------------------------------------------------------------------------------------------------------------
2. Scrum Roles
1. Product Owner
2. Scrum Master
3. Development Team
Product Owner -
Sole responsible for managing product backlog and prioritize it.
One person, not a group
Scrum Master -
Ensure the scrum is understood and enacted.
Provide service to Product Owner, Development Team and Organization.
Supports transparency
Eliminates that can make team underperform.
Development Team -
Estimates the complexity and work estimates.
2 hours per week for refine stories, planning and estimates.
Manages Sprint backlog and tracks sprint progress.
Include QA, UX, backend etc..
Ideal size 3-9
-----------------------------------------------------------------------------------------------------------------------------
3. Scrum Event
1. Sprint Planning
2. Daily Scrum
3. Backlog Refinement
4. Sprint Review
5. Sprint Retrospective
6. Product Backlog
Sprint Planning
• Purpose:
– To create a list of work for the sprint where no additional items shall be
added to the list during the sprint
• Format of the meeting:
– Populate the sprint backlog for your team(s) from a prioritized product
backlog per team’s capacity
– Decompose the user stories into actionable tasks; seek clarifications and
more information from the PO, if required
– Finalize acceptance criteria for selected/picked user stories
• Outcome:
– Everyone on the Scrum team understands and agrees what the team is
going to work on during the sprint and deliver at the end; define a sprint goal
• Attendees:
– PO, Scrum Master, and team
• Time-box: 4 hours for 2-weeks sprint
Daily Scrum
Purpose:
– For the team to know what it has accomplished for the sprint goal – not a
status meeting
• Format of the meeting:
– Each team member says what they did the previous day, what they plan to
do today (towards the sprint goal), and if they have any impediments(obstacles)
– It is okay to say you could not accomplish anything towards the goal, you
plan to do nothing towards the goal today because you have a lot of
impediments (obstacles)!
• Outcome:
– Everyone on the team understands where the team is in terms of delivering
the sprint goal; Scrum Master can optionally populate impediments in a list
and get on to resolve them
• Attendees:
– Team, Scrum Master (optional)
• Time-box: 15 minutes
Backlog Refinement
Purpose:
– For PO to announce any changes or reprioritization to the product backlog
and have top-priority items ready for discussion in the next sprint planning
meeting
• Format of the meeting:
– Product Owner goes through the user stories required to be delivered in the
next sprint
– Team provides an estimate for those user stories – at this point, it is not a
commitment from the team to deliver all user stories estimated
– Current workflow and sprint are not changed – this meeting is to ensure that
we have an emergent product backlog
• Outcome:
– Updated, prioritized, and estimated product backlog
• Attendees:
– PO, team, Scrum Master
• Time-box: Not more than 10% of Development team’s capacity
Sprint Review
Purpose:
– For Scrum team and stakeholders to collaborate on what was done during the sprint
• Format of the meeting:
– No presentation meeting
– Not exactly a “sign-off” meeting; presentation of the Increment is intended to elicit feedback and foster collaboration
• Outcome:
– PO and other stakeholders’ inputs on the work done during the sprint helps them determine next course of action to optimize value
• Attendees:
– PO, team, Scrum Master, other stakeholders, business owners
• Time-box: 2 hours for 2-weeks sprint
Sprint Retrospective
• Purpose:
– For team to voice their opinions on what is working, what is not working, and what they want to change – purely on people, relationships, process, and tools
• Format of the meeting:
– Every member gets to say what is working for them, what is not working, and what they want to change next sprint onwards
– Formal opportunity to inspect and adapt
• Outcome:
– List of improvements the team will start implementing next sprint onwards
• Attendees:
– PO, team, Scrum Master (as a member)
• Time-box: 1.5 hours for 2-weeks sprint
-----------------------------------------------------------------------------------------------------------------------------
4. Scrum Artifacts
Product Backlog
• A list of all desired work on the project
• Ideally expressed such that each item has value to the users or customers of the product
• Ordered/prioritized by the Product Owner
• Sole accountability lies with the Product Owner
• Can be changed anytime at the discretion of Product Owner
Sprint Backlog
• Owned by Development team
• Technical in nature
• Emerges during the sprint
• Estimated in hours, not Story Points
• Team members sign up for work and add in sprint backlog
• Work is never assigned
• Estimated work is updated daily
-----------------------------------------------------------------------------------------------------------------------------
5. Symptoms of Waterfall + Agile = Wagile
1. Your Scrum team consists of 20 people
2. Your sprints have “phases” such as Requirements or Design
3. Your project manager uses a Gannt Chart
4. Your team is assigned work and is asked for daily status rather than being allowed to
manage themselves
5. You never push back - “This is what the product owner wants in this sprint, so we have
to get it done”
6. Velocity is simply the speed you achieve when you are late to work
7. Your daily standups (if you have them) consist of Chickens, Pigs, Lions, Tigers and
Bears
8. You are still required to produce a large BRD to communicate requirements rather than
“just enough” to get the point across. This is managed in a tool with traceability and
simulation to help in the communication process
9. You are pulled off your current sprint to work on that ‘other project’ you used to be on
10. It’s 1:00am and you have a new release being implemented and the whole team isn’t
involved
-----------------------------------------------------------------------------------------------------------------------------
6. Scrum process
-----------------------------------------------------------------------------------------------------------------------------
Epic - Business came and want to deliver something. Here entry is made by product owner or product manager. Let say we want to create a Commercial website.
Feature – Card functionality, product page, search engine, wallet etc. Will be created by product owner or the project managers.
User Story – As a part of feature we will create stories. Like for search service, we can have 3 user stories. One for having data in DB. One for API layer which can fetch information from db and show it to users.
Task – With in that user story we create tasks.
EPIC
|_ Feature 1 …
|_ User story 1 …
|_ Tasks …
|_ Bug 1 …
e-FUTBall (e-futball)
From <https://himanshugoel2018learninghabbit.blogspot.com/search/label/Agile%20and%20Scrum>
