SlideShare una empresa de Scribd logo
1 de 2
Agile
SCRUM– Roles, Artifacts, Meetings, Tools, Glossary
Quick Reference Cards
+9122 4015 5175 +9122 2570 2772 +9122 2857 4960
http://www.techcanvass.com/
Copyrights @ Techcanvass | all rights reserved
Owns the Software
Scrum Team figures out how to turn the Product Backlog into an
increment of functionality within a Sprint. Each team member is
jointly responsible for the success of each iteration and of the
project as a whole.
• Team is cross functional ( Business Analyst, developer tester)
• Team consists of 3-12 full time members ( Exceptions : Specific
roles DBA)
• Self-organizing and self-managing team
• Maintains the Sprint Backlog
• Conducts the Sprint Review
• Technical implementation of User Stories
• Delivers a “potentially shippable” product increment at every
Sprint
Manifesto for Agile
Roles - Product Owner (PO)
Owns the Product Backlog
Product Owner represents the interests of project Stakeholders
and is responsible for the final product
• Elicitation of product requirements and features
• Responsible for prioritizing of requirements
• Owns the Product Backlog
• Manage the Release Plan
• Manage the Return on Investment
• Accountable for product success
Individuals and interactions
over processes and tools
Working software
over comprehensive documentation
Customer collaboration
over contract negotiation
Responding to change
over following a plan
Dynamic prioritized list of requirements
• Product backlog is dynamically prioritized list of requirements
ordered by Business Value
• Requirements can be added by anyone at anytime
• PBL can contain bugs and non-functional items
• Requirements are broken down into User Stories by Product
Owner
• Prioritize the requirements based on Business Value
Artifacts - Product Backlog (PBL)
Owns the Scrum process
Scrum Master is responsible for the Scrum process. He ensures
everybody plays by the rules. The Scrum Master is not part of the
Team.
• Manage the Scrum process
• Remove impediments for the Team
• Facilitate communication
• Is a facilitator and not a manager
• Shields the team from external interference
Roles – Scrum Team
1. Satisfy the customer through early and continuous delivery
2. Welcome changing requirements, even late in development
3. Deliver working software frequently
4. Business people and developers work together daily
5. Build projects around motivated individuals
6. Convey information via face-to-face conversation
7. Working software is the primary measure of progress
8. Maintain a constant pace indefinitely
9. Give continuous attention to technical excellence
10. Simplify: maximize the amount of work not done
11. Teams self-organize
12. Teams retrospect and tune their behaviors
Meetings – Sprint Planning
To commit the deliverable(s) to the PO
PBL prepared prior to meeting. It’s a two part meeting:
• PO presents the User Stories
• Team selects items committing to complete
• Discussion on PBI for clarifications
• Creation of Sprint Backlog from PBL
• Team solely responsible for deciding how to build
• Breakdown of user stories in Tasks to fill the SBL (normally 3 to 4
days of work, than inspect & adapt)
• PO available for questions
Timebox: 4 hours
Owner: Product Owner
Participants: Scrum Master, Scrum Team
Displays the remaining work
• Burndown chart shows the amount of work remaining per Sprint
• It is a very useful way of visualizing the correlation between work
remaining at any point in time and the progress of the Team(s)
• Use a tool e.g. JIRA for auto creation of the Burndown Chart
To Inspect and Adapt the progress
In this standup meeting the Team daily inspects their progress in
relation to the Planning by using the Burndown Chart, and makes
adaptation as necessary.
• Held every day during a Sprint (same time & place)
• Team members report to each other and not to SM
• Ask 3 questions during meeting:
"What have you done since last daily scrum?"
"What will you do before the next daily scrum?"
"What obstacles are impeding your work?“
Timebox: 15 minutes
Owner: Scrum Master
Participants: Team, all interested parties may silently attend
To maintain the good, get rid of the bad
At the end of a Sprint, the Team evaluates the finished Sprint.
• What went well and what can be improved
• Capture positive ways as a best practice, identify challenges and
develop strategies for improvements.
• SM helps team in discovery & not provide answers
Timebox: 3 hours
Owner: Scrum Master
Participants: Team, (Product Owner)
To demonstrate the achievements
The team present product owner the result on the developed
product of the Sprint. Product owner can accept or reject features
depending on the agreed acceptance criteria.
Timebox: 4 hours
Owner: Team
Participants: Scrum Master, Product Owner, optionally the PO can
invite other Stakeholders
Meetings - Daily Scrum
Meetings - Sprint Review
Artifact - Burndown Chart
Visibility + Flexibility = “Scrum”
“Done” = Potentially Shippable
Scrum requires at the end of each Sprint that the product is
production ready. That means the increment is:
• Thoroughly tested and stable
• Well-structured
• Well-written code
• User operation of the functionality is documented
Artifacts - Potentially Shippable Product
List of Tasks to fulfill the Sprint Goal
• Sprint Backlog contains all the committed User Stories for the
current Sprint broken down into Tasks by the Team
• All items on the Sprint Backlog should be developed, tested,
documented and integrated in order to fulfill the Sprint Goal.
• Estimate Story complexity using Planning Poker
Artifacts - Sprint Backlog (SBL)
12 Principles of Agile Development
Roles - Scrum Master (SM)
Meetings – Retrospective
Agile
SCRUM– Roles, Artifacts, Meetings, Tools, Glossary +9122 4015 5175 +9122 2570 2772 +9122 2857 4960
http://www.techcanvass.com/
Copyrights @ Techcanvass | all rights reservedQuick Reference Cards
Set of values as the foundation for the team's processes and
interactions
Commitment towards team and Sprint Goal
Focus being focused on the sprint and its goal
Openness to highlighting when you have challenges and
problems that are stopping you from success
Respect helping people to learn the things that you are good at
and not judging situations and people
Courage to being transparent, but willing to change even if that
means accepting that you are wrong
Scrum / Task Board
• Board containing teams Sprint goals, backlog items, tasks, tasks
in progress, "DONE" items and daily Sprint Burndown chart
• Scrum meetings best held around task board
• Visible to everyone
Free online Agile tools: Icescrum , Taiga , Scrumpy, Hansoft,
scrumdesk ,YouTrack , JIRA, VersionOne and scrumdo
Tools – Scrum Board
5 Scrum Values
Inspection
Timely checks on the process and artifacts towards Sprint Goal
to detect undesirable variances
Adaptation
Adjusting a process as soon as possible to minimize any further
deviation or issues
3 pillars in SCRUM
SCRUM uses an empirical approach
in order to adapt to the changing
requirements of the customer
Transparency
Viewed in the form of Product
Backlog, Task Boards and Burndown
charts, Daily Stand-ups,
Retrospectives, Sprint Reviews
Empirical Process in SCRUM
Make SMART Requirements: Simple, Measurable, Achievable,
Realistic, Traceable.
User Stories
A very high level definition of what the customer wants the
system to do. Each story is captured as a separate item on the
PBL
User Story Template:
As a <user> I want <function> So that <desired result>
INVEST in User Stores:
• Independent
• Negotiable
• Valuable
• Estimable
• Small
• Testable
Tasks
Make sure a Task is TECH. Time boxed, Everybody (can pick it up),
Complete and Human-readable
Requirements – User Stories & Tasks
Epic: A very large user story that is eventually split up into
multiple related user stories
Timebox: Fixed time period which cannot be exceeded
Scrum: Most widely used agile framework comprising of short
iterations, called sprints. Actual work is done within sprints
Sprint: Sprint is the scrum term for an iteration
Task: A completely broken down form of a user story
Spike: A short, time-boxed piece of research, usually technical,
on a single story that is intended to provide just enough
information that team can estimate the size of story
Definition of “Done” (DoD): List of development activities
required to consider an increment of functionality as “Done”.
Velocity: Rate at which team converts items to “DONE” in a
single Sprint. It is usually calculated in Story Points
Poker Planning: Consensus based approach for estimating
the efforts for a task. Generally involves team members and POs
proposing estimation values using poker cards and then finally
everyone agreeing to one value
Impediment: Anything which slows the team down or
prevents someone from working
Technical Debt: A consequence of poor engineering practices
which make a program difficult to modify. Technical bankruptcy
follows: Throw the program away and write a new one
Is Scrum agile?
Yes. Scrum is agile, but agile is more than Scrum.
Scrum signs up to all of the values and principles in the Agile
Manifesto and so is one member of the agile family along with
eXtreme Programming (XP), Kanban, Lean software
development, Crystal, and even hybrids such as Scrumban.
Who is responsible for managing the teams?
Teams are responsible for managing themselves
What is the effort/duration of a task?
Tasks should take no longer than 16 hours. If longer then the
task should be broken down further
Who manages obstacles?
Primary responsibility of managing obstacles is on the Scrum
Master. However, teams must learn to resolve their own issues.
Two of the biggest challenges in Scrum?
• Teams not self-managing
• Scrum Master managing not leading
Agile Process
Glossary
FAQ
Story points are estimates of effort as influenced by the amount
of work, complexity, risk and uncertainty
• Most popular way of estimation in Agile
• Relative sizing technique
• Entire team irrespective of specialty has to provide a single
estimate and not sum of individual estimates
• Usually scored on a scale of 1 to 10 (in order of difficulty)
Estimation - Story Point (SP)
Technique for Normalizing Story sizing:
• Find a small story and assign it one Story Point
• Estimate every other story relative to this story
• Points to consider while doing relative sizing:
Complexity, Knowledge and experience in the domain,
technology, Uncertainly, Volume, Repetition and Risk

Más contenido relacionado

La actualidad más candente

La actualidad más candente (20)

Scrum 101: Introduction to Scrum
Scrum 101: Introduction to ScrumScrum 101: Introduction to Scrum
Scrum 101: Introduction to Scrum
 
Agile Introduction - Scrum Framework
Agile Introduction - Scrum FrameworkAgile Introduction - Scrum Framework
Agile Introduction - Scrum Framework
 
Scrum In Ten Slides (v2.0) 2018
Scrum In Ten Slides (v2.0) 2018Scrum In Ten Slides (v2.0) 2018
Scrum In Ten Slides (v2.0) 2018
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrum
 
2017 Scrum by Picture
2017 Scrum by Picture2017 Scrum by Picture
2017 Scrum by Picture
 
What is scrum in Agile methodology?
What is scrum in Agile methodology?What is scrum in Agile methodology?
What is scrum in Agile methodology?
 
Scrum Cheat Sheet
Scrum Cheat SheetScrum Cheat Sheet
Scrum Cheat Sheet
 
Scrum in a page
Scrum in a pageScrum in a page
Scrum in a page
 
Scrum cheat sheet
Scrum cheat sheetScrum cheat sheet
Scrum cheat sheet
 
Basic Scrum Framework
Basic Scrum FrameworkBasic Scrum Framework
Basic Scrum Framework
 
SCRUM on a page - by Axon Active Vietnam
SCRUM on a page - by Axon Active VietnamSCRUM on a page - by Axon Active Vietnam
SCRUM on a page - by Axon Active Vietnam
 
Scrum in 15 Minutes
Scrum in 15 MinutesScrum in 15 Minutes
Scrum in 15 Minutes
 
What Is Agile Scrum
What Is Agile ScrumWhat Is Agile Scrum
What Is Agile Scrum
 
Agile (Scrum)
Agile (Scrum)Agile (Scrum)
Agile (Scrum)
 
Scrum
ScrumScrum
Scrum
 
Agile Methodology(SCRUM)
Agile Methodology(SCRUM)Agile Methodology(SCRUM)
Agile Methodology(SCRUM)
 
AGILE METHODOLOGY
AGILE METHODOLOGYAGILE METHODOLOGY
AGILE METHODOLOGY
 
Scrum in a nutshell
Scrum in a nutshellScrum in a nutshell
Scrum in a nutshell
 
Scrum Agile Methodlogy
Scrum Agile MethodlogyScrum Agile Methodlogy
Scrum Agile Methodlogy
 
Scrum In 15 Minutes
Scrum In 15 MinutesScrum In 15 Minutes
Scrum In 15 Minutes
 

Similar a Agile Scrum Quick Reference Card

FALLSEM2022-23_SWE2029_TH_VL2022230101289_Reference_Material_I_26-09-2022_Scr...
FALLSEM2022-23_SWE2029_TH_VL2022230101289_Reference_Material_I_26-09-2022_Scr...FALLSEM2022-23_SWE2029_TH_VL2022230101289_Reference_Material_I_26-09-2022_Scr...
FALLSEM2022-23_SWE2029_TH_VL2022230101289_Reference_Material_I_26-09-2022_Scr...duhitha2
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptMujeebMohammed18
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptAnuriJoshi
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptGustavoDelaEspriella2
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptNarendraKumar521662
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptMANYAGOEL14
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptssuser436c47
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptssuserf8c57f
 
Agile Processes-Scrum.ppt
 Agile Processes-Scrum.ppt Agile Processes-Scrum.ppt
Agile Processes-Scrum.pptYunusKhan90
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptgauravarora931329
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptssuser4f2477
 
Lecture 5 -6(CSC205).pptx jsksnxbbxjxksnsnz
Lecture 5 -6(CSC205).pptx jsksnxbbxjxksnsnzLecture 5 -6(CSC205).pptx jsksnxbbxjxksnsnz
Lecture 5 -6(CSC205).pptx jsksnxbbxjxksnsnzAhmadSajjad34
 
Agile Processes - Scrum
Agile Processes - ScrumAgile Processes - Scrum
Agile Processes - ScrumSoumya De
 
PSPO(Scrum Product Owner) Preparation Quick Guide.pdf
PSPO(Scrum Product Owner) Preparation Quick Guide.pdfPSPO(Scrum Product Owner) Preparation Quick Guide.pdf
PSPO(Scrum Product Owner) Preparation Quick Guide.pdfSwadesh Bhushan, PMP®
 
Agile Modeling & Scrum Development.pptx
Agile Modeling & Scrum Development.pptxAgile Modeling & Scrum Development.pptx
Agile Modeling & Scrum Development.pptxSamira AlShahrani
 

Similar a Agile Scrum Quick Reference Card (20)

Agile processes scrum
Agile processes scrumAgile processes scrum
Agile processes scrum
 
Agile Methodology
Agile MethodologyAgile Methodology
Agile Methodology
 
Agile methodology
Agile methodologyAgile methodology
Agile methodology
 
FALLSEM2022-23_SWE2029_TH_VL2022230101289_Reference_Material_I_26-09-2022_Scr...
FALLSEM2022-23_SWE2029_TH_VL2022230101289_Reference_Material_I_26-09-2022_Scr...FALLSEM2022-23_SWE2029_TH_VL2022230101289_Reference_Material_I_26-09-2022_Scr...
FALLSEM2022-23_SWE2029_TH_VL2022230101289_Reference_Material_I_26-09-2022_Scr...
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 
Agile Processes-Scrum.ppt
 Agile Processes-Scrum.ppt Agile Processes-Scrum.ppt
Agile Processes-Scrum.ppt
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 
Lecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.pptLecture 12 - Agile Processes-Scrum.ppt
Lecture 12 - Agile Processes-Scrum.ppt
 
professional scrum master
professional scrum master professional scrum master
professional scrum master
 
Lecture 5 -6(CSC205).pptx jsksnxbbxjxksnsnz
Lecture 5 -6(CSC205).pptx jsksnxbbxjxksnsnzLecture 5 -6(CSC205).pptx jsksnxbbxjxksnsnz
Lecture 5 -6(CSC205).pptx jsksnxbbxjxksnsnz
 
Scrum
ScrumScrum
Scrum
 
Agile Processes - Scrum
Agile Processes - ScrumAgile Processes - Scrum
Agile Processes - Scrum
 
PSPO(Scrum Product Owner) Preparation Quick Guide.pdf
PSPO(Scrum Product Owner) Preparation Quick Guide.pdfPSPO(Scrum Product Owner) Preparation Quick Guide.pdf
PSPO(Scrum Product Owner) Preparation Quick Guide.pdf
 
Agile Modeling & Scrum Development.pptx
Agile Modeling & Scrum Development.pptxAgile Modeling & Scrum Development.pptx
Agile Modeling & Scrum Development.pptx
 

Más de Techcanvass

ECBA Exam Questions PDF | ECBA Sample Questions PDF | Techcanvass
ECBA Exam Questions PDF | ECBA Sample Questions PDF | TechcanvassECBA Exam Questions PDF | ECBA Sample Questions PDF | Techcanvass
ECBA Exam Questions PDF | ECBA Sample Questions PDF | TechcanvassTechcanvass
 
Free CCBA exam questions PDF
Free CCBA exam questions PDFFree CCBA exam questions PDF
Free CCBA exam questions PDFTechcanvass
 
Selenium web element commands cheat sheet
Selenium web element commands   cheat sheetSelenium web element commands   cheat sheet
Selenium web element commands cheat sheetTechcanvass
 
CBAP Certification Overview
CBAP Certification OverviewCBAP Certification Overview
CBAP Certification OverviewTechcanvass
 
CCBA Certification Overview
CCBA Certification OverviewCCBA Certification Overview
CCBA Certification OverviewTechcanvass
 
5 things to do to become a Business Analyst
5 things to do to become a Business Analyst5 things to do to become a Business Analyst
5 things to do to become a Business AnalystTechcanvass
 
Business analysis Fundamentals | Fundamentals of business analysis
Business analysis Fundamentals | Fundamentals of business analysisBusiness analysis Fundamentals | Fundamentals of business analysis
Business analysis Fundamentals | Fundamentals of business analysisTechcanvass
 
What is Data Dictionary - BABOK technique
What is Data Dictionary - BABOK techniqueWhat is Data Dictionary - BABOK technique
What is Data Dictionary - BABOK techniqueTechcanvass
 
SQL Quick Reference Card
SQL Quick Reference CardSQL Quick Reference Card
SQL Quick Reference CardTechcanvass
 
Selenium Interview Questions & Answers
Selenium Interview Questions & AnswersSelenium Interview Questions & Answers
Selenium Interview Questions & AnswersTechcanvass
 
IIBA ECBA Certification Exam preparation Strategy
IIBA ECBA Certification Exam preparation StrategyIIBA ECBA Certification Exam preparation Strategy
IIBA ECBA Certification Exam preparation StrategyTechcanvass
 
User stories basics
User stories basicsUser stories basics
User stories basicsTechcanvass
 
Business analyst certifications
Business analyst certificationsBusiness analyst certifications
Business analyst certificationsTechcanvass
 
CBAP sample questions
CBAP sample questionsCBAP sample questions
CBAP sample questionsTechcanvass
 
Selenium Tutorial for Beginners | Automation framework Basics
Selenium Tutorial for Beginners | Automation framework BasicsSelenium Tutorial for Beginners | Automation framework Basics
Selenium Tutorial for Beginners | Automation framework BasicsTechcanvass
 
Agile business analyst
Agile business analystAgile business analyst
Agile business analystTechcanvass
 
CBAP Certification Basics
CBAP Certification BasicsCBAP Certification Basics
CBAP Certification BasicsTechcanvass
 
IIBA BABOK version 3 - What's inside
IIBA BABOK version 3 - What's insideIIBA BABOK version 3 - What's inside
IIBA BABOK version 3 - What's insideTechcanvass
 
Business Analysis Core Concepts Model (BACCM)
Business Analysis Core Concepts Model (BACCM)Business Analysis Core Concepts Model (BACCM)
Business Analysis Core Concepts Model (BACCM)Techcanvass
 
Function point analysis introduction
Function point analysis introductionFunction point analysis introduction
Function point analysis introductionTechcanvass
 

Más de Techcanvass (20)

ECBA Exam Questions PDF | ECBA Sample Questions PDF | Techcanvass
ECBA Exam Questions PDF | ECBA Sample Questions PDF | TechcanvassECBA Exam Questions PDF | ECBA Sample Questions PDF | Techcanvass
ECBA Exam Questions PDF | ECBA Sample Questions PDF | Techcanvass
 
Free CCBA exam questions PDF
Free CCBA exam questions PDFFree CCBA exam questions PDF
Free CCBA exam questions PDF
 
Selenium web element commands cheat sheet
Selenium web element commands   cheat sheetSelenium web element commands   cheat sheet
Selenium web element commands cheat sheet
 
CBAP Certification Overview
CBAP Certification OverviewCBAP Certification Overview
CBAP Certification Overview
 
CCBA Certification Overview
CCBA Certification OverviewCCBA Certification Overview
CCBA Certification Overview
 
5 things to do to become a Business Analyst
5 things to do to become a Business Analyst5 things to do to become a Business Analyst
5 things to do to become a Business Analyst
 
Business analysis Fundamentals | Fundamentals of business analysis
Business analysis Fundamentals | Fundamentals of business analysisBusiness analysis Fundamentals | Fundamentals of business analysis
Business analysis Fundamentals | Fundamentals of business analysis
 
What is Data Dictionary - BABOK technique
What is Data Dictionary - BABOK techniqueWhat is Data Dictionary - BABOK technique
What is Data Dictionary - BABOK technique
 
SQL Quick Reference Card
SQL Quick Reference CardSQL Quick Reference Card
SQL Quick Reference Card
 
Selenium Interview Questions & Answers
Selenium Interview Questions & AnswersSelenium Interview Questions & Answers
Selenium Interview Questions & Answers
 
IIBA ECBA Certification Exam preparation Strategy
IIBA ECBA Certification Exam preparation StrategyIIBA ECBA Certification Exam preparation Strategy
IIBA ECBA Certification Exam preparation Strategy
 
User stories basics
User stories basicsUser stories basics
User stories basics
 
Business analyst certifications
Business analyst certificationsBusiness analyst certifications
Business analyst certifications
 
CBAP sample questions
CBAP sample questionsCBAP sample questions
CBAP sample questions
 
Selenium Tutorial for Beginners | Automation framework Basics
Selenium Tutorial for Beginners | Automation framework BasicsSelenium Tutorial for Beginners | Automation framework Basics
Selenium Tutorial for Beginners | Automation framework Basics
 
Agile business analyst
Agile business analystAgile business analyst
Agile business analyst
 
CBAP Certification Basics
CBAP Certification BasicsCBAP Certification Basics
CBAP Certification Basics
 
IIBA BABOK version 3 - What's inside
IIBA BABOK version 3 - What's insideIIBA BABOK version 3 - What's inside
IIBA BABOK version 3 - What's inside
 
Business Analysis Core Concepts Model (BACCM)
Business Analysis Core Concepts Model (BACCM)Business Analysis Core Concepts Model (BACCM)
Business Analysis Core Concepts Model (BACCM)
 
Function point analysis introduction
Function point analysis introductionFunction point analysis introduction
Function point analysis introduction
 

Último

THYROID HORMONE.pptx by Subham Panja,Asst. Professor, Department of B.Sc MLT,...
THYROID HORMONE.pptx by Subham Panja,Asst. Professor, Department of B.Sc MLT,...THYROID HORMONE.pptx by Subham Panja,Asst. Professor, Department of B.Sc MLT,...
THYROID HORMONE.pptx by Subham Panja,Asst. Professor, Department of B.Sc MLT,...Subham Panja
 
LEAD5623 The Economics of Community Coll
LEAD5623 The Economics of Community CollLEAD5623 The Economics of Community Coll
LEAD5623 The Economics of Community CollDr. Bruce A. Johnson
 
Awards Presentation 2024 - March 12 2024
Awards Presentation 2024 - March 12 2024Awards Presentation 2024 - March 12 2024
Awards Presentation 2024 - March 12 2024bsellato
 
Plant Tissue culture., Plasticity, Totipotency, pptx
Plant Tissue culture., Plasticity, Totipotency, pptxPlant Tissue culture., Plasticity, Totipotency, pptx
Plant Tissue culture., Plasticity, Totipotency, pptxHimansu10
 
BBA 205 BUSINESS ENVIRONMENT UNIT I.pptx
BBA 205 BUSINESS ENVIRONMENT UNIT I.pptxBBA 205 BUSINESS ENVIRONMENT UNIT I.pptx
BBA 205 BUSINESS ENVIRONMENT UNIT I.pptxProf. Kanchan Kumari
 
25 CHUYÊN ĐỀ ÔN THI TỐT NGHIỆP THPT 2023 – BÀI TẬP PHÁT TRIỂN TỪ ĐỀ MINH HỌA...
25 CHUYÊN ĐỀ ÔN THI TỐT NGHIỆP THPT 2023 – BÀI TẬP PHÁT TRIỂN TỪ ĐỀ MINH HỌA...25 CHUYÊN ĐỀ ÔN THI TỐT NGHIỆP THPT 2023 – BÀI TẬP PHÁT TRIỂN TỪ ĐỀ MINH HỌA...
25 CHUYÊN ĐỀ ÔN THI TỐT NGHIỆP THPT 2023 – BÀI TẬP PHÁT TRIỂN TỪ ĐỀ MINH HỌA...Nguyen Thanh Tu Collection
 
3.14.24 The Selma March and the Voting Rights Act.pptx
3.14.24 The Selma March and the Voting Rights Act.pptx3.14.24 The Selma March and the Voting Rights Act.pptx
3.14.24 The Selma March and the Voting Rights Act.pptxmary850239
 
How to Customise Quotation's Appearance Using PDF Quote Builder in Odoo 17
How to Customise Quotation's Appearance Using PDF Quote Builder in Odoo 17How to Customise Quotation's Appearance Using PDF Quote Builder in Odoo 17
How to Customise Quotation's Appearance Using PDF Quote Builder in Odoo 17Celine George
 
Alamkara theory by Bhamaha Indian Poetics (1).pptx
Alamkara theory by Bhamaha Indian Poetics (1).pptxAlamkara theory by Bhamaha Indian Poetics (1).pptx
Alamkara theory by Bhamaha Indian Poetics (1).pptxDhatriParmar
 
DNA and RNA , Structure, Functions, Types, difference, Similarities, Protein ...
DNA and RNA , Structure, Functions, Types, difference, Similarities, Protein ...DNA and RNA , Structure, Functions, Types, difference, Similarities, Protein ...
DNA and RNA , Structure, Functions, Types, difference, Similarities, Protein ...AKSHAYMAGAR17
 
VIT336 – Recommender System - Unit 3.pdf
VIT336 – Recommender System - Unit 3.pdfVIT336 – Recommender System - Unit 3.pdf
VIT336 – Recommender System - Unit 3.pdfArthyR3
 
AUDIENCE THEORY - PARTICIPATORY - JENKINS.pptx
AUDIENCE THEORY - PARTICIPATORY - JENKINS.pptxAUDIENCE THEORY - PARTICIPATORY - JENKINS.pptx
AUDIENCE THEORY - PARTICIPATORY - JENKINS.pptxiammrhaywood
 
3.12.24 The Social Construction of Gender.pptx
3.12.24 The Social Construction of Gender.pptx3.12.24 The Social Construction of Gender.pptx
3.12.24 The Social Construction of Gender.pptxmary850239
 
DLL Catch Up Friday March 22.docx CATCH UP FRIDAYS
DLL Catch Up Friday March 22.docx CATCH UP FRIDAYSDLL Catch Up Friday March 22.docx CATCH UP FRIDAYS
DLL Catch Up Friday March 22.docx CATCH UP FRIDAYSTeacherNicaPrintable
 
UNIT I Design Thinking and Explore.pptx
UNIT I  Design Thinking and Explore.pptxUNIT I  Design Thinking and Explore.pptx
UNIT I Design Thinking and Explore.pptxGOWSIKRAJA PALANISAMY
 
The First National K12 TUG March 6 2024.pdf
The First National K12 TUG March 6 2024.pdfThe First National K12 TUG March 6 2024.pdf
The First National K12 TUG March 6 2024.pdfdogden2
 
LEAD6001 - Introduction to Advanced Stud
LEAD6001 - Introduction to Advanced StudLEAD6001 - Introduction to Advanced Stud
LEAD6001 - Introduction to Advanced StudDr. Bruce A. Johnson
 
Pharmacology chapter No 7 full notes.pdf
Pharmacology chapter No 7 full notes.pdfPharmacology chapter No 7 full notes.pdf
Pharmacology chapter No 7 full notes.pdfSumit Tiwari
 

Último (20)

THYROID HORMONE.pptx by Subham Panja,Asst. Professor, Department of B.Sc MLT,...
THYROID HORMONE.pptx by Subham Panja,Asst. Professor, Department of B.Sc MLT,...THYROID HORMONE.pptx by Subham Panja,Asst. Professor, Department of B.Sc MLT,...
THYROID HORMONE.pptx by Subham Panja,Asst. Professor, Department of B.Sc MLT,...
 
LEAD5623 The Economics of Community Coll
LEAD5623 The Economics of Community CollLEAD5623 The Economics of Community Coll
LEAD5623 The Economics of Community Coll
 
Awards Presentation 2024 - March 12 2024
Awards Presentation 2024 - March 12 2024Awards Presentation 2024 - March 12 2024
Awards Presentation 2024 - March 12 2024
 
Plant Tissue culture., Plasticity, Totipotency, pptx
Plant Tissue culture., Plasticity, Totipotency, pptxPlant Tissue culture., Plasticity, Totipotency, pptx
Plant Tissue culture., Plasticity, Totipotency, pptx
 
BBA 205 BUSINESS ENVIRONMENT UNIT I.pptx
BBA 205 BUSINESS ENVIRONMENT UNIT I.pptxBBA 205 BUSINESS ENVIRONMENT UNIT I.pptx
BBA 205 BUSINESS ENVIRONMENT UNIT I.pptx
 
25 CHUYÊN ĐỀ ÔN THI TỐT NGHIỆP THPT 2023 – BÀI TẬP PHÁT TRIỂN TỪ ĐỀ MINH HỌA...
25 CHUYÊN ĐỀ ÔN THI TỐT NGHIỆP THPT 2023 – BÀI TẬP PHÁT TRIỂN TỪ ĐỀ MINH HỌA...25 CHUYÊN ĐỀ ÔN THI TỐT NGHIỆP THPT 2023 – BÀI TẬP PHÁT TRIỂN TỪ ĐỀ MINH HỌA...
25 CHUYÊN ĐỀ ÔN THI TỐT NGHIỆP THPT 2023 – BÀI TẬP PHÁT TRIỂN TỪ ĐỀ MINH HỌA...
 
3.14.24 The Selma March and the Voting Rights Act.pptx
3.14.24 The Selma March and the Voting Rights Act.pptx3.14.24 The Selma March and the Voting Rights Act.pptx
3.14.24 The Selma March and the Voting Rights Act.pptx
 
How to Customise Quotation's Appearance Using PDF Quote Builder in Odoo 17
How to Customise Quotation's Appearance Using PDF Quote Builder in Odoo 17How to Customise Quotation's Appearance Using PDF Quote Builder in Odoo 17
How to Customise Quotation's Appearance Using PDF Quote Builder in Odoo 17
 
Alamkara theory by Bhamaha Indian Poetics (1).pptx
Alamkara theory by Bhamaha Indian Poetics (1).pptxAlamkara theory by Bhamaha Indian Poetics (1).pptx
Alamkara theory by Bhamaha Indian Poetics (1).pptx
 
DNA and RNA , Structure, Functions, Types, difference, Similarities, Protein ...
DNA and RNA , Structure, Functions, Types, difference, Similarities, Protein ...DNA and RNA , Structure, Functions, Types, difference, Similarities, Protein ...
DNA and RNA , Structure, Functions, Types, difference, Similarities, Protein ...
 
VIT336 – Recommender System - Unit 3.pdf
VIT336 – Recommender System - Unit 3.pdfVIT336 – Recommender System - Unit 3.pdf
VIT336 – Recommender System - Unit 3.pdf
 
AUDIENCE THEORY - PARTICIPATORY - JENKINS.pptx
AUDIENCE THEORY - PARTICIPATORY - JENKINS.pptxAUDIENCE THEORY - PARTICIPATORY - JENKINS.pptx
AUDIENCE THEORY - PARTICIPATORY - JENKINS.pptx
 
3.12.24 The Social Construction of Gender.pptx
3.12.24 The Social Construction of Gender.pptx3.12.24 The Social Construction of Gender.pptx
3.12.24 The Social Construction of Gender.pptx
 
DLL Catch Up Friday March 22.docx CATCH UP FRIDAYS
DLL Catch Up Friday March 22.docx CATCH UP FRIDAYSDLL Catch Up Friday March 22.docx CATCH UP FRIDAYS
DLL Catch Up Friday March 22.docx CATCH UP FRIDAYS
 
UNIT I Design Thinking and Explore.pptx
UNIT I  Design Thinking and Explore.pptxUNIT I  Design Thinking and Explore.pptx
UNIT I Design Thinking and Explore.pptx
 
Problems on Mean,Mode,Median Standard Deviation
Problems on Mean,Mode,Median Standard DeviationProblems on Mean,Mode,Median Standard Deviation
Problems on Mean,Mode,Median Standard Deviation
 
The First National K12 TUG March 6 2024.pdf
The First National K12 TUG March 6 2024.pdfThe First National K12 TUG March 6 2024.pdf
The First National K12 TUG March 6 2024.pdf
 
ANOVA Parametric test: Biostatics and Research Methodology
ANOVA Parametric test: Biostatics and Research MethodologyANOVA Parametric test: Biostatics and Research Methodology
ANOVA Parametric test: Biostatics and Research Methodology
 
LEAD6001 - Introduction to Advanced Stud
LEAD6001 - Introduction to Advanced StudLEAD6001 - Introduction to Advanced Stud
LEAD6001 - Introduction to Advanced Stud
 
Pharmacology chapter No 7 full notes.pdf
Pharmacology chapter No 7 full notes.pdfPharmacology chapter No 7 full notes.pdf
Pharmacology chapter No 7 full notes.pdf
 

Agile Scrum Quick Reference Card

  • 1. Agile SCRUM– Roles, Artifacts, Meetings, Tools, Glossary Quick Reference Cards +9122 4015 5175 +9122 2570 2772 +9122 2857 4960 http://www.techcanvass.com/ Copyrights @ Techcanvass | all rights reserved Owns the Software Scrum Team figures out how to turn the Product Backlog into an increment of functionality within a Sprint. Each team member is jointly responsible for the success of each iteration and of the project as a whole. • Team is cross functional ( Business Analyst, developer tester) • Team consists of 3-12 full time members ( Exceptions : Specific roles DBA) • Self-organizing and self-managing team • Maintains the Sprint Backlog • Conducts the Sprint Review • Technical implementation of User Stories • Delivers a “potentially shippable” product increment at every Sprint Manifesto for Agile Roles - Product Owner (PO) Owns the Product Backlog Product Owner represents the interests of project Stakeholders and is responsible for the final product • Elicitation of product requirements and features • Responsible for prioritizing of requirements • Owns the Product Backlog • Manage the Release Plan • Manage the Return on Investment • Accountable for product success Individuals and interactions over processes and tools Working software over comprehensive documentation Customer collaboration over contract negotiation Responding to change over following a plan Dynamic prioritized list of requirements • Product backlog is dynamically prioritized list of requirements ordered by Business Value • Requirements can be added by anyone at anytime • PBL can contain bugs and non-functional items • Requirements are broken down into User Stories by Product Owner • Prioritize the requirements based on Business Value Artifacts - Product Backlog (PBL) Owns the Scrum process Scrum Master is responsible for the Scrum process. He ensures everybody plays by the rules. The Scrum Master is not part of the Team. • Manage the Scrum process • Remove impediments for the Team • Facilitate communication • Is a facilitator and not a manager • Shields the team from external interference Roles – Scrum Team 1. Satisfy the customer through early and continuous delivery 2. Welcome changing requirements, even late in development 3. Deliver working software frequently 4. Business people and developers work together daily 5. Build projects around motivated individuals 6. Convey information via face-to-face conversation 7. Working software is the primary measure of progress 8. Maintain a constant pace indefinitely 9. Give continuous attention to technical excellence 10. Simplify: maximize the amount of work not done 11. Teams self-organize 12. Teams retrospect and tune their behaviors Meetings – Sprint Planning To commit the deliverable(s) to the PO PBL prepared prior to meeting. It’s a two part meeting: • PO presents the User Stories • Team selects items committing to complete • Discussion on PBI for clarifications • Creation of Sprint Backlog from PBL • Team solely responsible for deciding how to build • Breakdown of user stories in Tasks to fill the SBL (normally 3 to 4 days of work, than inspect & adapt) • PO available for questions Timebox: 4 hours Owner: Product Owner Participants: Scrum Master, Scrum Team Displays the remaining work • Burndown chart shows the amount of work remaining per Sprint • It is a very useful way of visualizing the correlation between work remaining at any point in time and the progress of the Team(s) • Use a tool e.g. JIRA for auto creation of the Burndown Chart To Inspect and Adapt the progress In this standup meeting the Team daily inspects their progress in relation to the Planning by using the Burndown Chart, and makes adaptation as necessary. • Held every day during a Sprint (same time & place) • Team members report to each other and not to SM • Ask 3 questions during meeting: "What have you done since last daily scrum?" "What will you do before the next daily scrum?" "What obstacles are impeding your work?“ Timebox: 15 minutes Owner: Scrum Master Participants: Team, all interested parties may silently attend To maintain the good, get rid of the bad At the end of a Sprint, the Team evaluates the finished Sprint. • What went well and what can be improved • Capture positive ways as a best practice, identify challenges and develop strategies for improvements. • SM helps team in discovery & not provide answers Timebox: 3 hours Owner: Scrum Master Participants: Team, (Product Owner) To demonstrate the achievements The team present product owner the result on the developed product of the Sprint. Product owner can accept or reject features depending on the agreed acceptance criteria. Timebox: 4 hours Owner: Team Participants: Scrum Master, Product Owner, optionally the PO can invite other Stakeholders Meetings - Daily Scrum Meetings - Sprint Review Artifact - Burndown Chart Visibility + Flexibility = “Scrum” “Done” = Potentially Shippable Scrum requires at the end of each Sprint that the product is production ready. That means the increment is: • Thoroughly tested and stable • Well-structured • Well-written code • User operation of the functionality is documented Artifacts - Potentially Shippable Product List of Tasks to fulfill the Sprint Goal • Sprint Backlog contains all the committed User Stories for the current Sprint broken down into Tasks by the Team • All items on the Sprint Backlog should be developed, tested, documented and integrated in order to fulfill the Sprint Goal. • Estimate Story complexity using Planning Poker Artifacts - Sprint Backlog (SBL) 12 Principles of Agile Development Roles - Scrum Master (SM) Meetings – Retrospective
  • 2. Agile SCRUM– Roles, Artifacts, Meetings, Tools, Glossary +9122 4015 5175 +9122 2570 2772 +9122 2857 4960 http://www.techcanvass.com/ Copyrights @ Techcanvass | all rights reservedQuick Reference Cards Set of values as the foundation for the team's processes and interactions Commitment towards team and Sprint Goal Focus being focused on the sprint and its goal Openness to highlighting when you have challenges and problems that are stopping you from success Respect helping people to learn the things that you are good at and not judging situations and people Courage to being transparent, but willing to change even if that means accepting that you are wrong Scrum / Task Board • Board containing teams Sprint goals, backlog items, tasks, tasks in progress, "DONE" items and daily Sprint Burndown chart • Scrum meetings best held around task board • Visible to everyone Free online Agile tools: Icescrum , Taiga , Scrumpy, Hansoft, scrumdesk ,YouTrack , JIRA, VersionOne and scrumdo Tools – Scrum Board 5 Scrum Values Inspection Timely checks on the process and artifacts towards Sprint Goal to detect undesirable variances Adaptation Adjusting a process as soon as possible to minimize any further deviation or issues 3 pillars in SCRUM SCRUM uses an empirical approach in order to adapt to the changing requirements of the customer Transparency Viewed in the form of Product Backlog, Task Boards and Burndown charts, Daily Stand-ups, Retrospectives, Sprint Reviews Empirical Process in SCRUM Make SMART Requirements: Simple, Measurable, Achievable, Realistic, Traceable. User Stories A very high level definition of what the customer wants the system to do. Each story is captured as a separate item on the PBL User Story Template: As a <user> I want <function> So that <desired result> INVEST in User Stores: • Independent • Negotiable • Valuable • Estimable • Small • Testable Tasks Make sure a Task is TECH. Time boxed, Everybody (can pick it up), Complete and Human-readable Requirements – User Stories & Tasks Epic: A very large user story that is eventually split up into multiple related user stories Timebox: Fixed time period which cannot be exceeded Scrum: Most widely used agile framework comprising of short iterations, called sprints. Actual work is done within sprints Sprint: Sprint is the scrum term for an iteration Task: A completely broken down form of a user story Spike: A short, time-boxed piece of research, usually technical, on a single story that is intended to provide just enough information that team can estimate the size of story Definition of “Done” (DoD): List of development activities required to consider an increment of functionality as “Done”. Velocity: Rate at which team converts items to “DONE” in a single Sprint. It is usually calculated in Story Points Poker Planning: Consensus based approach for estimating the efforts for a task. Generally involves team members and POs proposing estimation values using poker cards and then finally everyone agreeing to one value Impediment: Anything which slows the team down or prevents someone from working Technical Debt: A consequence of poor engineering practices which make a program difficult to modify. Technical bankruptcy follows: Throw the program away and write a new one Is Scrum agile? Yes. Scrum is agile, but agile is more than Scrum. Scrum signs up to all of the values and principles in the Agile Manifesto and so is one member of the agile family along with eXtreme Programming (XP), Kanban, Lean software development, Crystal, and even hybrids such as Scrumban. Who is responsible for managing the teams? Teams are responsible for managing themselves What is the effort/duration of a task? Tasks should take no longer than 16 hours. If longer then the task should be broken down further Who manages obstacles? Primary responsibility of managing obstacles is on the Scrum Master. However, teams must learn to resolve their own issues. Two of the biggest challenges in Scrum? • Teams not self-managing • Scrum Master managing not leading Agile Process Glossary FAQ Story points are estimates of effort as influenced by the amount of work, complexity, risk and uncertainty • Most popular way of estimation in Agile • Relative sizing technique • Entire team irrespective of specialty has to provide a single estimate and not sum of individual estimates • Usually scored on a scale of 1 to 10 (in order of difficulty) Estimation - Story Point (SP) Technique for Normalizing Story sizing: • Find a small story and assign it one Story Point • Estimate every other story relative to this story • Points to consider while doing relative sizing: Complexity, Knowledge and experience in the domain, technology, Uncertainly, Volume, Repetition and Risk