SlideShare a Scribd company logo
Agile
(SCRUM)
Methodology
Dominic Cushnan
@domcushnan
What is Agile Methodology?
➔ Agile methodology is an alternative to traditional project
management, typically used in software development. It helps
teams respond to unpredictability through incremental,
iterative work cadences, known as sprints.
➔ Agile methodologies are an alternative to waterfall, or
traditional sequential development.
➔ Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
➔ Welcome changing requirements, even late in development. Agile processes harness change for the
customer's competitive advantage.
➔ Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to
the shorter timescale.
➔ Business people and developers must work together daily throughout the project.
➔ Build projects around motivated individuals. Give them the environment and support they need, and trust
them to get the job done.
➔ The most efficient and effective method of conveying information to and within a development team is
face-to-face conversation.
Principles behind the Agile Manifesto
Principles behind the Agile Manifesto
➔ Working software is the primary measure of progress.
➔ Agile processes promote sustainable development. The sponsors, developers, and users should be able to
maintain a constant pace indefinitely.
➔ Continuous attention to technical excellence and good design enhances agility.
➔ Simplicity--the art of maximizing the amount of work not done--is essential.
➔ The best architectures, requirements, and designs emerge from self-organizing teams.
➔ At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior
accordingly.
What is Scrum?
➔ It is one of many iterative and incremental software development agile process for
managing product development.
➔ It is a framework within which people can address complex adaptive problems,
while productively and creatively delivering products of the highest possible value.
➔ It is based on multiple small teams working in an intensive and interdependent
manner. The teams in the organization work together while constantly focusing on
their common interests.
➔ Scrum has three roles: Product Owner, Scrum Master, and Team.
Scrum involves:
➔ Initial appointment of a project manager called the "scrum master."
➔ Definition and prioritization of tasks to be done.
➔ Planning sessions for each task.
➔ Daily meetings among teams.
➔ Identification and evaluation of potential project risks and process pitfalls.
➔ Execution of projects in brief, high-intensity, frequent work sessions.
➔ Reviews of progress and evaluations of completed projects.
➔ Openness to constructive criticism and ideas for improvement.
The Scrum Process
Scrum blends all
development activities
into each iteration,
adapting to discovered
realities at fixed
intervals.
The Calendar Template
Scrum
Roles
Scrum Roles consists of a Product Owner,
the Scrum Master, and the Development
Team.
Scrum Roles - Product Owner
➔ Single person responsible for maximizing the return on investment (ROI) of the development
effort
➔ Responsible for product vision
➔ Constantly re-prioritizes the Product Backlog, adjusting any long term expectations such as
release plans
➔ Final arbiter of requirements questions
➔ Accepts or rejects each product increment
➔ Decides whether to ship
➔ Decides whether to continue development
➔ Considers stakeholder interests
➔ May contribute as a team member
Scrum Roles - Scrum Master
➔ Facilitates the Scrum process
➔ Helps resolve impediments
➔ Creates an environment conducive to team self-organization
➔ Captures empirical data to adjust forecasts
➔ Shields the team from external interference and distractions to keep it in group flow (a.k.a. the
zone)
➔ Enforces timeboxes
➔ Keeps Scrum artifacts visible
➔ Promotes improved engineering practices
Scrum Roles - Development Team
➔ Cross-functional (e.g., includes members with testing skills, and often others not traditionally
called developers: business analysts, domain experts, etc.) Self-organizing / self-managing,
without externally assigned roles
➔ Negotiates commitments with the Product Owner, one Sprint at a time
➔ Has autonomy regarding how to reach commitments
➔ Intensely collaborative
➔ Most successful when located in one team room, particularly for the first few Sprints
➔ Most successful with long-term, full-time membership. Scrum moves work to a flexible
learning team and avoids moving people or splitting them between teams.
➔ 3-9 members (originally 7 ± 2 members)
Scrum
Artifacts
These represent work or value to provide
transparency and opportunities for
inspection and adaptation.
Scrum Artifacts - Product Backlog
The Product Backlog is an ordered list of everything that might be
needed in the product and is the single source of requirements for
any changes to be made to the product. The Product Owner is
responsible for the it, including its content, availability, and ordering.
It lists all features, functions, requirements, enhancements, and fixes
that constitute the changes to be made to the product in future
releases.
Scrum Artifacts - Product Backlog
➔ Force-ranked list of desired functionality
➔ Visible to all stakeholders
➔ Any stakeholder (including the Team) can add items
➔ Constantly re-prioritized by the Product Owner
➔ Items at top are more granular than items at bottom
➔ Maintained during the Backlog Refinement Meeting
Scrum Artifacts - Product Backlog
Product Backlog Item (PBI)
➔ Specifies the what more than the how of a customer-centric feature
➔ Often written in User Story form
➔ Has a product-wide definition of done to prevent technical debt
➔ May have item-specific acceptance criteria
➔ Effort is estimated by the team, ideally in relative units (e.g., story points)
➔ Effort is roughly 2-3 people 2-3 days, or smaller for advanced teams
Scrum Artifacts - Sprint Backlog
The Sprint Backlog is the set of Product Backlog items selected for the
Sprint, plus a plan for delivering the product Increment and realizing
the Sprint Goal.
The Sprint Backlog is a forecast by the Development Team about what
functionality will be in the next Increment and the work needed to
deliver that functionality into a “Done” Increment.
Scrum Artifacts - Sprint Backlog
➔ Consists of committed PBIs negotiated between the team and the Product
Owner during the Sprint Planning Meeting
➔ Scope commitment is fixed during Sprint Execution
➔ Initial tasks are identified by the team during Sprint Planning Meeting
➔ Team will discover additional tasks needed to meet the fixed scope
commitment during Sprint execution
➔ Visible to the team
➔ Referenced during the Daily Scrum Meeting
Scrum Artifacts - Sprint Backlog
Increment
The Increment is the sum of all the Product Backlog items completed
during a Sprint and the value of the increments of all previous
Sprints.
At the end of a Sprint, the new Increment must be “Done,” which
means it must be in useable condition and meet the Scrum Team’s
definition of “Done.”
Scrum Artifacts - Sprint Backlog
Sprint Backlog is often
represented with an
“information radiator” such
as a physical task board
(Scrum Board).
An example of a physical Scrum Board
Scrum
Events
Prescribed events are used in Scrum to
create regularity and to minimize the need
for meetings not defined in Scrum. All
events are time-boxed events, such that
every event has a maximum duration.
Scrum Events - Sprint Planning
The work to be performed in the Sprint is planned at the Sprint
Planning. This 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.
The Scrum Master ensures that the event takes place and that
attendants understand its purpose. The Scrum Master teaches the
Scrum Team to keep it within the time-box.
Scrum Events - Sprint Planning
Sprint Planning answers the following:
➔ What can be delivered in the Increment resulting from the
upcoming Sprint?
➔ How will the work needed to deliver the Increment be achieved?
Sprint Goal
The Sprint Goal is an objective set for the Sprint. It provides guidance
to the Development Team on why it is building the Increment. It is
created during the Sprint Planning meeting.
Scrum Events - Sprint Planning
Scrum Events - Daily Scrum/Daily Stand-up
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.
This is done by inspecting the work since the last Daily Scrum and
forecasting the work that could be done before the next one. The
Daily Scrum is held at the same time and place each day to reduce
complexity.
Scrum Events - Daily Scrum/Daily Stand-up
During the meeting, the Development Team members explain:
➔ What did I do yesterday that helped the Development Team meet
the Sprint Goal?
➔ What will I do today to help the Development Team meet the
Sprint Goal?
➔ Do I see any impediment that prevents me or the Development
Team from meeting the Sprint Goal?
Scrum Events - Daily Scrum/Daily Stand-up
The Development Team or team members often meet immediately
after the Daily Scrum for detailed discussions, or to adapt, or replan,
the rest of the Sprint’s work.
Daily Scrums improve communications, eliminate other meetings,
identify impediments to development for removal, highlight and
promote quick decision-making, and improve the Development
Team’s level of knowledge. This is a key inspect and adapt meeting.
Scrum Events - Sprint Review/Demo
A Sprint Review is held at the end of the Sprint to inspect the
Increment and adapt the Product Backlog if needed. During the
Sprint Review, the Scrum Team and stakeholders collaborate about
what was done in the Sprint.
This is an informal meeting, not a status meeting, and the
presentation of the Increment is intended to elicit feedback and foster
collaboration.
Scrum Events - Sprint Review/Demo
The Sprint Review includes the following elements:
➔ Attendees include the Scrum Team and key stakeholders invited by the Product Owner;
➔ The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”;
➔ The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were
solved;
➔ The Development Team demonstrates the work that it has “Done” and answers questions about the Increment;
➔ The Product Owner discusses the Product Backlog as it stands. He or she projects likely completion dates based on progress to
date (if needed);
➔ The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint
Planning;
➔ Review of how the marketplace or potential use of the product might have changed what is the most valuable thing to do next;
and,
➔ Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated release of the product.
Scrum Events - Sprint Retrospective
The Sprint Retrospective is an opportunity for the Scrum Team to
inspect itself and create a plan for improvements to be enacted
during the next Sprint.
The Sprint Retrospective occurs after the Sprint Review and prior to
the next Sprint Planning.
Scrum Events - Sprint Retrospective
The purpose of the Sprint Retrospective is to:
➔ Inspect how the last Sprint went with regards to people,
relationships, process, and tools;
➔ Identify and order the major items that went well and potential
improvements; and,
➔ Create a plan for implementing improvements to the way the
Scrum Team does its work.
CREDITS
Presentation template by SlidesCarnival
Photographs by Death to the Stock Photo (license)
SOURCES
http://agilemethodology.org/
http://scrummethodology.com/
http://searchsoftwarequality.techtarget.com/definition/Scrum
http://scrumreferencecard.com/scrum-reference-card/
http://www.scrumguides.org/scrum-guide.html
http://www.synagila.com/wp-content/uploads/2014/01/scrum-board.jpg
https://amareshv.files.wordpress.com/2011/03/fairydustboard_20110324.jpg
https://www.mountaingoatsoftware.com/agile/new-to-agile-or-scrum

More Related Content

What's hot

Agile & SCRUM basics
Agile & SCRUM basicsAgile & SCRUM basics
Agile & SCRUM basics
Arun R
 
Scrum In Ten Slides
Scrum In Ten SlidesScrum In Ten Slides
Scrum In Ten Slides
pmengal
 
Agile Process Introduction
Agile Process IntroductionAgile Process Introduction
Agile Process Introduction
Nguyen Hai
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrum
Sriram Srinivasan
 
Scrum 101: Introduction to Scrum
Scrum 101: Introduction to ScrumScrum 101: Introduction to Scrum
Scrum 101: Introduction to Scrum
Arrielle Mali
 
Scrum
ScrumScrum
Scrum for Beginners
Scrum for BeginnersScrum for Beginners
Scrum for Beginners
Anjana Saxena
 
What is Scrum? SlideShare
What is Scrum? SlideShareWhat is Scrum? SlideShare
What is Scrum? SlideShare
Invensis Learning
 
Agile - Scrum Presentation
Agile - Scrum PresentationAgile - Scrum Presentation
Agile - Scrum Presentation
gihanlsw
 
Introduction agile scrum methodology
Introduction agile scrum methodologyIntroduction agile scrum methodology
Introduction agile scrum methodology
Amit Verma
 
Agile Scrum Methodology
Agile Scrum MethodologyAgile Scrum Methodology
Agile Scrum Methodology
Rajeev Misra
 
Introduction To Scrum
Introduction To ScrumIntroduction To Scrum
Introduction To Scrum
Dave Neuman
 
Scrum
ScrumScrum
Scrum
Sujoy Saha
 
Agile - Scrum
Agile - ScrumAgile - Scrum
Agile - Scrum
Samir Chitkara
 
Scrum framework
Scrum frameworkScrum framework
Scrum framework
Rashmi Pathak
 
Scrum
ScrumScrum
AGILE METHODOLOGY
AGILE METHODOLOGYAGILE METHODOLOGY
AGILE METHODOLOGY
Deepak Agrawal
 
Agile Scrum software methodology
Agile Scrum software methodologyAgile Scrum software methodology
Agile Scrum software methodology
Abdullah Raza
 
Scrum Process
Scrum ProcessScrum Process
Scrum Process
Rodrigo Paolucci
 
Scrum 101
Scrum 101 Scrum 101
Scrum 101
Ozgur Ertem
 

What's hot (20)

Agile & SCRUM basics
Agile & SCRUM basicsAgile & SCRUM basics
Agile & SCRUM basics
 
Scrum In Ten Slides
Scrum In Ten SlidesScrum In Ten Slides
Scrum In Ten Slides
 
Agile Process Introduction
Agile Process IntroductionAgile Process Introduction
Agile Process Introduction
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrum
 
Scrum 101: Introduction to Scrum
Scrum 101: Introduction to ScrumScrum 101: Introduction to Scrum
Scrum 101: Introduction to Scrum
 
Scrum
ScrumScrum
Scrum
 
Scrum for Beginners
Scrum for BeginnersScrum for Beginners
Scrum for Beginners
 
What is Scrum? SlideShare
What is Scrum? SlideShareWhat is Scrum? SlideShare
What is Scrum? SlideShare
 
Agile - Scrum Presentation
Agile - Scrum PresentationAgile - Scrum Presentation
Agile - Scrum Presentation
 
Introduction agile scrum methodology
Introduction agile scrum methodologyIntroduction agile scrum methodology
Introduction agile scrum methodology
 
Agile Scrum Methodology
Agile Scrum MethodologyAgile Scrum Methodology
Agile Scrum Methodology
 
Introduction To Scrum
Introduction To ScrumIntroduction To Scrum
Introduction To Scrum
 
Scrum
ScrumScrum
Scrum
 
Agile - Scrum
Agile - ScrumAgile - Scrum
Agile - Scrum
 
Scrum framework
Scrum frameworkScrum framework
Scrum framework
 
Scrum
ScrumScrum
Scrum
 
AGILE METHODOLOGY
AGILE METHODOLOGYAGILE METHODOLOGY
AGILE METHODOLOGY
 
Agile Scrum software methodology
Agile Scrum software methodologyAgile Scrum software methodology
Agile Scrum software methodology
 
Scrum Process
Scrum ProcessScrum Process
Scrum Process
 
Scrum 101
Scrum 101 Scrum 101
Scrum 101
 

Viewers also liked

Introduction to Scrum for Project Managers
Introduction to Scrum for Project ManagersIntroduction to Scrum for Project Managers
Getting Started with Scrum
Getting Started with ScrumGetting Started with Scrum
Getting Started with Scrum
Silvana Wasitova, Scrum & Agile Coach
 
Agile & Scrum Training
Agile & Scrum TrainingAgile & Scrum Training
Agile & Scrum Training
Conscires Agile Practices
 
Agile & Scrum – intro slides
Agile & Scrum – intro slidesAgile & Scrum – intro slides
Agile & Scrum – intro slides
Artem Bykovets
 
Short introduction to Agile Scrum
Short introduction to Agile ScrumShort introduction to Agile Scrum
Short introduction to Agile Scrum
Nishan Bose
 
Scrum in Practice
Scrum in PracticeScrum in Practice
Scrum in Practice
Naresh Jain
 
Scrum in 5 slides
Scrum in 5 slidesScrum in 5 slides
Scrum in 5 slides
Joshua Partogi
 
Learn Scrum Engineering in 5 minutes
Learn Scrum Engineering in 5 minutesLearn Scrum Engineering in 5 minutes
Learn Scrum Engineering in 5 minutes
guest035e0d
 
Scrum In 15 Minutes
Scrum In 15 MinutesScrum In 15 Minutes
Scrum In 15 Minutes
Srikanth Shreenivas
 

Viewers also liked (9)

Introduction to Scrum for Project Managers
Introduction to Scrum for Project ManagersIntroduction to Scrum for Project Managers
Introduction to Scrum for Project Managers
 
Getting Started with Scrum
Getting Started with ScrumGetting Started with Scrum
Getting Started with Scrum
 
Agile & Scrum Training
Agile & Scrum TrainingAgile & Scrum Training
Agile & Scrum Training
 
Agile & Scrum – intro slides
Agile & Scrum – intro slidesAgile & Scrum – intro slides
Agile & Scrum – intro slides
 
Short introduction to Agile Scrum
Short introduction to Agile ScrumShort introduction to Agile Scrum
Short introduction to Agile Scrum
 
Scrum in Practice
Scrum in PracticeScrum in Practice
Scrum in Practice
 
Scrum in 5 slides
Scrum in 5 slidesScrum in 5 slides
Scrum in 5 slides
 
Learn Scrum Engineering in 5 minutes
Learn Scrum Engineering in 5 minutesLearn Scrum Engineering in 5 minutes
Learn Scrum Engineering in 5 minutes
 
Scrum In 15 Minutes
Scrum In 15 MinutesScrum In 15 Minutes
Scrum In 15 Minutes
 

Similar to Agile (Scrum)

Introduction to Agile & scrum
Introduction to Agile & scrumIntroduction to Agile & scrum
Introduction to Agile & scrum
Elad Sofer
 
Agile Scrum Project Management
Agile Scrum Project ManagementAgile Scrum Project Management
Agile processes scrum
Agile processes scrumAgile processes scrum
Agile processes scrum
Pruthviraj Yerram
 
Scrum referencecard
Scrum referencecardScrum referencecard
Scrum referencecard
Suresh Kumar
 
Scrum Method
Scrum MethodScrum Method
Scrum Method
David R. Iannone Jr.
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrum
James Walmsley CSM, PSM I, PSK I
 
Agile Methodology in Software Development
Agile Methodology in Software DevelopmentAgile Methodology in Software Development
Agile Methodology in Software Development
Raghav Seth
 
How scrum works
How scrum worksHow scrum works
How scrum works
Annu Rana
 
Agile
AgileAgile
Scrum-Agile : An Introduction
Scrum-Agile : An IntroductionScrum-Agile : An Introduction
Scrum-Agile : An Introduction
Global SQA
 
Scrum and Devops - Workshop & Handson
Scrum and Devops - Workshop & HandsonScrum and Devops - Workshop & Handson
Scrum and Devops - Workshop & Handson
Dony Riyanto
 
What is Scrum?
What is Scrum?What is Scrum?
What is Scrum?
Neoteric EU
 
Agile methodology
Agile methodologyAgile methodology
Agile methodology
subash kumar
 
Agile Bootcamp
Agile BootcampAgile Bootcamp
Agile Bootcamp
douglangille
 
Agile Scrum Quick Reference Card
Agile Scrum Quick Reference CardAgile Scrum Quick Reference Card
Agile Scrum Quick Reference Card
Techcanvass
 
Scrum Reference Card
Scrum Reference CardScrum Reference Card
Scrum Reference Card
enderturan
 
Scrum methodology 
Scrum methodology Scrum methodology 
Scrum methodology 
SnehaRoy74
 
Metodologia scrum actualizada qa
Metodologia scrum actualizada qaMetodologia scrum actualizada qa
Metodologia scrum actualizada qa
Alfonso Gabriel López Ceballos
 
hyaus Pjskilao.pptx
hyaus Pjskilao.pptxhyaus Pjskilao.pptx
hyaus Pjskilao.pptx
GeorgePama1
 
Let’s Play Agile ! 12-09-15-testers_hub
Let’s  Play  Agile ! 12-09-15-testers_hubLet’s  Play  Agile ! 12-09-15-testers_hub
Let’s Play Agile ! 12-09-15-testers_hub
Owner Tester's Hub
 

Similar to Agile (Scrum) (20)

Introduction to Agile & scrum
Introduction to Agile & scrumIntroduction to Agile & scrum
Introduction to Agile & scrum
 
Agile Scrum Project Management
Agile Scrum Project ManagementAgile Scrum Project Management
Agile Scrum Project Management
 
Agile processes scrum
Agile processes scrumAgile processes scrum
Agile processes scrum
 
Scrum referencecard
Scrum referencecardScrum referencecard
Scrum referencecard
 
Scrum Method
Scrum MethodScrum Method
Scrum Method
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrum
 
Agile Methodology in Software Development
Agile Methodology in Software DevelopmentAgile Methodology in Software Development
Agile Methodology in Software Development
 
How scrum works
How scrum worksHow scrum works
How scrum works
 
Agile
AgileAgile
Agile
 
Scrum-Agile : An Introduction
Scrum-Agile : An IntroductionScrum-Agile : An Introduction
Scrum-Agile : An Introduction
 
Scrum and Devops - Workshop & Handson
Scrum and Devops - Workshop & HandsonScrum and Devops - Workshop & Handson
Scrum and Devops - Workshop & Handson
 
What is Scrum?
What is Scrum?What is Scrum?
What is Scrum?
 
Agile methodology
Agile methodologyAgile methodology
Agile methodology
 
Agile Bootcamp
Agile BootcampAgile Bootcamp
Agile Bootcamp
 
Agile Scrum Quick Reference Card
Agile Scrum Quick Reference CardAgile Scrum Quick Reference Card
Agile Scrum Quick Reference Card
 
Scrum Reference Card
Scrum Reference CardScrum Reference Card
Scrum Reference Card
 
Scrum methodology 
Scrum methodology Scrum methodology 
Scrum methodology 
 
Metodologia scrum actualizada qa
Metodologia scrum actualizada qaMetodologia scrum actualizada qa
Metodologia scrum actualizada qa
 
hyaus Pjskilao.pptx
hyaus Pjskilao.pptxhyaus Pjskilao.pptx
hyaus Pjskilao.pptx
 
Let’s Play Agile ! 12-09-15-testers_hub
Let’s  Play  Agile ! 12-09-15-testers_hubLet’s  Play  Agile ! 12-09-15-testers_hub
Let’s Play Agile ! 12-09-15-testers_hub
 

More from Dom Cushnan

Digital healthcare show - How will Artificial Intelligence in healthcare will...
Digital healthcare show - How will Artificial Intelligence in healthcare will...Digital healthcare show - How will Artificial Intelligence in healthcare will...
Digital healthcare show - How will Artificial Intelligence in healthcare will...
Dom Cushnan
 
AI in healthcare - AISummit London
AI in healthcare - AISummit LondonAI in healthcare - AISummit London
AI in healthcare - AISummit London
Dom Cushnan
 
Google Drive (for dummies)
Google Drive (for dummies)Google Drive (for dummies)
Google Drive (for dummies)
Dom Cushnan
 
Google Hangouts (for dummies)
Google Hangouts (for dummies)Google Hangouts (for dummies)
Google Hangouts (for dummies)
Dom Cushnan
 
Twitter Tips & Tricks
Twitter Tips & TricksTwitter Tips & Tricks
Twitter Tips & Tricks
Dom Cushnan
 
Mailchimp for Beginners
Mailchimp for BeginnersMailchimp for Beginners
Mailchimp for Beginners
Dom Cushnan
 
What is a Vox Pop?
What is a Vox Pop?What is a Vox Pop?
What is a Vox Pop?
Dom Cushnan
 
Google Analytics: The Basics
Google Analytics: The BasicsGoogle Analytics: The Basics
Google Analytics: The Basics
Dom Cushnan
 
Why Asana is Great for Project Management
Why Asana is Great for Project ManagementWhy Asana is Great for Project Management
Why Asana is Great for Project Management
Dom Cushnan
 
Virtual Reality
Virtual RealityVirtual Reality
Virtual Reality
Dom Cushnan
 

More from Dom Cushnan (10)

Digital healthcare show - How will Artificial Intelligence in healthcare will...
Digital healthcare show - How will Artificial Intelligence in healthcare will...Digital healthcare show - How will Artificial Intelligence in healthcare will...
Digital healthcare show - How will Artificial Intelligence in healthcare will...
 
AI in healthcare - AISummit London
AI in healthcare - AISummit LondonAI in healthcare - AISummit London
AI in healthcare - AISummit London
 
Google Drive (for dummies)
Google Drive (for dummies)Google Drive (for dummies)
Google Drive (for dummies)
 
Google Hangouts (for dummies)
Google Hangouts (for dummies)Google Hangouts (for dummies)
Google Hangouts (for dummies)
 
Twitter Tips & Tricks
Twitter Tips & TricksTwitter Tips & Tricks
Twitter Tips & Tricks
 
Mailchimp for Beginners
Mailchimp for BeginnersMailchimp for Beginners
Mailchimp for Beginners
 
What is a Vox Pop?
What is a Vox Pop?What is a Vox Pop?
What is a Vox Pop?
 
Google Analytics: The Basics
Google Analytics: The BasicsGoogle Analytics: The Basics
Google Analytics: The Basics
 
Why Asana is Great for Project Management
Why Asana is Great for Project ManagementWhy Asana is Great for Project Management
Why Asana is Great for Project Management
 
Virtual Reality
Virtual RealityVirtual Reality
Virtual Reality
 

Recently uploaded

AWS Cloud Practitioner Essentials (Second Edition) (Arabic) Final Course Know...
AWS Cloud Practitioner Essentials (Second Edition) (Arabic) Final Course Know...AWS Cloud Practitioner Essentials (Second Edition) (Arabic) Final Course Know...
AWS Cloud Practitioner Essentials (Second Edition) (Arabic) Final Course Know...
karim wahed
 
Vip Girls Call ServiCe Hyderabad 0000000000 Pooja Best High Class Hyderabad A...
Vip Girls Call ServiCe Hyderabad 0000000000 Pooja Best High Class Hyderabad A...Vip Girls Call ServiCe Hyderabad 0000000000 Pooja Best High Class Hyderabad A...
Vip Girls Call ServiCe Hyderabad 0000000000 Pooja Best High Class Hyderabad A...
ashiklo9823
 
Wired_2.0_Create_AmsterdamJUG_09072024.pptx
Wired_2.0_Create_AmsterdamJUG_09072024.pptxWired_2.0_Create_AmsterdamJUG_09072024.pptx
Wired_2.0_Create_AmsterdamJUG_09072024.pptx
SimonedeGijt
 
Artificial intelligence in customer services or chatbots
Artificial intelligence  in customer services or chatbotsArtificial intelligence  in customer services or chatbots
Artificial intelligence in customer services or chatbots
kayash1656
 
React Native vs Flutter - SSTech System
React Native vs Flutter  - SSTech SystemReact Native vs Flutter  - SSTech System
React Native vs Flutter - SSTech System
SSTech System
 
dachnug51 - HCL Sametime 12 as a Software Appliance.pdf
dachnug51 - HCL Sametime 12 as a Software Appliance.pdfdachnug51 - HCL Sametime 12 as a Software Appliance.pdf
dachnug51 - HCL Sametime 12 as a Software Appliance.pdf
DNUG e.V.
 
Break data silos with real-time connectivity using Confluent Cloud Connectors
Break data silos with real-time connectivity using Confluent Cloud ConnectorsBreak data silos with real-time connectivity using Confluent Cloud Connectors
Break data silos with real-time connectivity using Confluent Cloud Connectors
confluent
 
BITCOIN HEIST RANSOMEWARE ATTACK PREDICTION
BITCOIN HEIST RANSOMEWARE ATTACK PREDICTIONBITCOIN HEIST RANSOMEWARE ATTACK PREDICTION
BITCOIN HEIST RANSOMEWARE ATTACK PREDICTION
ssuser2b426d1
 
Folding Cheat Sheet #7 - seventh in a series
Folding Cheat Sheet #7 - seventh in a seriesFolding Cheat Sheet #7 - seventh in a series
Folding Cheat Sheet #7 - seventh in a series
Philip Schwarz
 
WEBINAR SLIDES: CCX for Cloud Service Providers
WEBINAR SLIDES: CCX for Cloud Service ProvidersWEBINAR SLIDES: CCX for Cloud Service Providers
WEBINAR SLIDES: CCX for Cloud Service Providers
Severalnines
 
AWS Cloud Practitioner Essentials (Second Edition) (Arabic) .pdf
AWS Cloud Practitioner Essentials (Second Edition) (Arabic) .pdfAWS Cloud Practitioner Essentials (Second Edition) (Arabic) .pdf
AWS Cloud Practitioner Essentials (Second Edition) (Arabic) .pdf
karim wahed
 
active-directory-auditing-solution (2).pptx
active-directory-auditing-solution (2).pptxactive-directory-auditing-solution (2).pptx
active-directory-auditing-solution (2).pptx
sudsdeep
 
ENISA Threat Landscape 2023 documentation
ENISA Threat Landscape 2023 documentationENISA Threat Landscape 2023 documentation
ENISA Threat Landscape 2023 documentation
sofiafernandezon
 
Top 10 Tips To Get Google AdSense For Your Website
Top 10 Tips To Get Google AdSense For Your WebsiteTop 10 Tips To Get Google AdSense For Your Website
Top 10 Tips To Get Google AdSense For Your Website
e-Definers Technology
 
NBFC Software: Optimize Your Non-Banking Financial Company
NBFC Software: Optimize Your Non-Banking Financial CompanyNBFC Software: Optimize Your Non-Banking Financial Company
NBFC Software: Optimize Your Non-Banking Financial Company
NBFC Softwares
 
11 Top Cross Browser Testing Tools to Know About.pdf
11 Top Cross Browser Testing Tools to Know About.pdf11 Top Cross Browser Testing Tools to Know About.pdf
11 Top Cross Browser Testing Tools to Know About.pdf
kalichargn70th171
 
NYGGS 360: A Complete ERP for Construction Innovation
NYGGS 360: A Complete ERP for Construction InnovationNYGGS 360: A Complete ERP for Construction Innovation
NYGGS 360: A Complete ERP for Construction Innovation
NYGGS Construction ERP Software
 
introduction of Ansys software and basic and advance knowledge of modelling s...
introduction of Ansys software and basic and advance knowledge of modelling s...introduction of Ansys software and basic and advance knowledge of modelling s...
introduction of Ansys software and basic and advance knowledge of modelling s...
sachin chaurasia
 
Shivam Pandit working on Php Web Developer.
Shivam Pandit working on Php Web Developer.Shivam Pandit working on Php Web Developer.
Shivam Pandit working on Php Web Developer.
shivamt017
 
當測試開始左移
當測試開始左移當測試開始左移
當測試開始左移
Jersey (CHE-PING) Su
 

Recently uploaded (20)

AWS Cloud Practitioner Essentials (Second Edition) (Arabic) Final Course Know...
AWS Cloud Practitioner Essentials (Second Edition) (Arabic) Final Course Know...AWS Cloud Practitioner Essentials (Second Edition) (Arabic) Final Course Know...
AWS Cloud Practitioner Essentials (Second Edition) (Arabic) Final Course Know...
 
Vip Girls Call ServiCe Hyderabad 0000000000 Pooja Best High Class Hyderabad A...
Vip Girls Call ServiCe Hyderabad 0000000000 Pooja Best High Class Hyderabad A...Vip Girls Call ServiCe Hyderabad 0000000000 Pooja Best High Class Hyderabad A...
Vip Girls Call ServiCe Hyderabad 0000000000 Pooja Best High Class Hyderabad A...
 
Wired_2.0_Create_AmsterdamJUG_09072024.pptx
Wired_2.0_Create_AmsterdamJUG_09072024.pptxWired_2.0_Create_AmsterdamJUG_09072024.pptx
Wired_2.0_Create_AmsterdamJUG_09072024.pptx
 
Artificial intelligence in customer services or chatbots
Artificial intelligence  in customer services or chatbotsArtificial intelligence  in customer services or chatbots
Artificial intelligence in customer services or chatbots
 
React Native vs Flutter - SSTech System
React Native vs Flutter  - SSTech SystemReact Native vs Flutter  - SSTech System
React Native vs Flutter - SSTech System
 
dachnug51 - HCL Sametime 12 as a Software Appliance.pdf
dachnug51 - HCL Sametime 12 as a Software Appliance.pdfdachnug51 - HCL Sametime 12 as a Software Appliance.pdf
dachnug51 - HCL Sametime 12 as a Software Appliance.pdf
 
Break data silos with real-time connectivity using Confluent Cloud Connectors
Break data silos with real-time connectivity using Confluent Cloud ConnectorsBreak data silos with real-time connectivity using Confluent Cloud Connectors
Break data silos with real-time connectivity using Confluent Cloud Connectors
 
BITCOIN HEIST RANSOMEWARE ATTACK PREDICTION
BITCOIN HEIST RANSOMEWARE ATTACK PREDICTIONBITCOIN HEIST RANSOMEWARE ATTACK PREDICTION
BITCOIN HEIST RANSOMEWARE ATTACK PREDICTION
 
Folding Cheat Sheet #7 - seventh in a series
Folding Cheat Sheet #7 - seventh in a seriesFolding Cheat Sheet #7 - seventh in a series
Folding Cheat Sheet #7 - seventh in a series
 
WEBINAR SLIDES: CCX for Cloud Service Providers
WEBINAR SLIDES: CCX for Cloud Service ProvidersWEBINAR SLIDES: CCX for Cloud Service Providers
WEBINAR SLIDES: CCX for Cloud Service Providers
 
AWS Cloud Practitioner Essentials (Second Edition) (Arabic) .pdf
AWS Cloud Practitioner Essentials (Second Edition) (Arabic) .pdfAWS Cloud Practitioner Essentials (Second Edition) (Arabic) .pdf
AWS Cloud Practitioner Essentials (Second Edition) (Arabic) .pdf
 
active-directory-auditing-solution (2).pptx
active-directory-auditing-solution (2).pptxactive-directory-auditing-solution (2).pptx
active-directory-auditing-solution (2).pptx
 
ENISA Threat Landscape 2023 documentation
ENISA Threat Landscape 2023 documentationENISA Threat Landscape 2023 documentation
ENISA Threat Landscape 2023 documentation
 
Top 10 Tips To Get Google AdSense For Your Website
Top 10 Tips To Get Google AdSense For Your WebsiteTop 10 Tips To Get Google AdSense For Your Website
Top 10 Tips To Get Google AdSense For Your Website
 
NBFC Software: Optimize Your Non-Banking Financial Company
NBFC Software: Optimize Your Non-Banking Financial CompanyNBFC Software: Optimize Your Non-Banking Financial Company
NBFC Software: Optimize Your Non-Banking Financial Company
 
11 Top Cross Browser Testing Tools to Know About.pdf
11 Top Cross Browser Testing Tools to Know About.pdf11 Top Cross Browser Testing Tools to Know About.pdf
11 Top Cross Browser Testing Tools to Know About.pdf
 
NYGGS 360: A Complete ERP for Construction Innovation
NYGGS 360: A Complete ERP for Construction InnovationNYGGS 360: A Complete ERP for Construction Innovation
NYGGS 360: A Complete ERP for Construction Innovation
 
introduction of Ansys software and basic and advance knowledge of modelling s...
introduction of Ansys software and basic and advance knowledge of modelling s...introduction of Ansys software and basic and advance knowledge of modelling s...
introduction of Ansys software and basic and advance knowledge of modelling s...
 
Shivam Pandit working on Php Web Developer.
Shivam Pandit working on Php Web Developer.Shivam Pandit working on Php Web Developer.
Shivam Pandit working on Php Web Developer.
 
當測試開始左移
當測試開始左移當測試開始左移
當測試開始左移
 

Agile (Scrum)

  • 2. What is Agile Methodology? ➔ Agile methodology is an alternative to traditional project management, typically used in software development. It helps teams respond to unpredictability through incremental, iterative work cadences, known as sprints. ➔ Agile methodologies are an alternative to waterfall, or traditional sequential development.
  • 3. ➔ Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. ➔ Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. ➔ Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. ➔ Business people and developers must work together daily throughout the project. ➔ Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done. ➔ The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Principles behind the Agile Manifesto
  • 4. Principles behind the Agile Manifesto ➔ Working software is the primary measure of progress. ➔ Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. ➔ Continuous attention to technical excellence and good design enhances agility. ➔ Simplicity--the art of maximizing the amount of work not done--is essential. ➔ The best architectures, requirements, and designs emerge from self-organizing teams. ➔ At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
  • 5. What is Scrum? ➔ It is one of many iterative and incremental software development agile process for managing product development. ➔ It is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. ➔ It is based on multiple small teams working in an intensive and interdependent manner. The teams in the organization work together while constantly focusing on their common interests. ➔ Scrum has three roles: Product Owner, Scrum Master, and Team.
  • 6. Scrum involves: ➔ Initial appointment of a project manager called the "scrum master." ➔ Definition and prioritization of tasks to be done. ➔ Planning sessions for each task. ➔ Daily meetings among teams. ➔ Identification and evaluation of potential project risks and process pitfalls. ➔ Execution of projects in brief, high-intensity, frequent work sessions. ➔ Reviews of progress and evaluations of completed projects. ➔ Openness to constructive criticism and ideas for improvement.
  • 7. The Scrum Process Scrum blends all development activities into each iteration, adapting to discovered realities at fixed intervals.
  • 9. Scrum Roles Scrum Roles consists of a Product Owner, the Scrum Master, and the Development Team.
  • 10. Scrum Roles - Product Owner ➔ Single person responsible for maximizing the return on investment (ROI) of the development effort ➔ Responsible for product vision ➔ Constantly re-prioritizes the Product Backlog, adjusting any long term expectations such as release plans ➔ Final arbiter of requirements questions ➔ Accepts or rejects each product increment ➔ Decides whether to ship ➔ Decides whether to continue development ➔ Considers stakeholder interests ➔ May contribute as a team member
  • 11. Scrum Roles - Scrum Master ➔ Facilitates the Scrum process ➔ Helps resolve impediments ➔ Creates an environment conducive to team self-organization ➔ Captures empirical data to adjust forecasts ➔ Shields the team from external interference and distractions to keep it in group flow (a.k.a. the zone) ➔ Enforces timeboxes ➔ Keeps Scrum artifacts visible ➔ Promotes improved engineering practices
  • 12. Scrum Roles - Development Team ➔ Cross-functional (e.g., includes members with testing skills, and often others not traditionally called developers: business analysts, domain experts, etc.) Self-organizing / self-managing, without externally assigned roles ➔ Negotiates commitments with the Product Owner, one Sprint at a time ➔ Has autonomy regarding how to reach commitments ➔ Intensely collaborative ➔ Most successful when located in one team room, particularly for the first few Sprints ➔ Most successful with long-term, full-time membership. Scrum moves work to a flexible learning team and avoids moving people or splitting them between teams. ➔ 3-9 members (originally 7 ± 2 members)
  • 13. Scrum Artifacts These represent work or value to provide transparency and opportunities for inspection and adaptation.
  • 14. Scrum Artifacts - Product Backlog The Product Backlog is an ordered list of everything that might be needed in the product and is the single source of requirements for any changes to be made to the product. The Product Owner is responsible for the it, including its content, availability, and ordering. It lists all features, functions, requirements, enhancements, and fixes that constitute the changes to be made to the product in future releases.
  • 15. Scrum Artifacts - Product Backlog ➔ Force-ranked list of desired functionality ➔ Visible to all stakeholders ➔ Any stakeholder (including the Team) can add items ➔ Constantly re-prioritized by the Product Owner ➔ Items at top are more granular than items at bottom ➔ Maintained during the Backlog Refinement Meeting
  • 16. Scrum Artifacts - Product Backlog Product Backlog Item (PBI) ➔ Specifies the what more than the how of a customer-centric feature ➔ Often written in User Story form ➔ Has a product-wide definition of done to prevent technical debt ➔ May have item-specific acceptance criteria ➔ Effort is estimated by the team, ideally in relative units (e.g., story points) ➔ Effort is roughly 2-3 people 2-3 days, or smaller for advanced teams
  • 17. Scrum Artifacts - Sprint Backlog The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus a plan for delivering the product Increment and realizing the Sprint Goal. The Sprint Backlog is a forecast by the Development Team about what functionality will be in the next Increment and the work needed to deliver that functionality into a “Done” Increment.
  • 18. Scrum Artifacts - Sprint Backlog ➔ Consists of committed PBIs negotiated between the team and the Product Owner during the Sprint Planning Meeting ➔ Scope commitment is fixed during Sprint Execution ➔ Initial tasks are identified by the team during Sprint Planning Meeting ➔ Team will discover additional tasks needed to meet the fixed scope commitment during Sprint execution ➔ Visible to the team ➔ Referenced during the Daily Scrum Meeting
  • 19. Scrum Artifacts - Sprint Backlog Increment The Increment is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. At the end of a Sprint, the new Increment must be “Done,” which means it must be in useable condition and meet the Scrum Team’s definition of “Done.”
  • 20. Scrum Artifacts - Sprint Backlog Sprint Backlog is often represented with an “information radiator” such as a physical task board (Scrum Board).
  • 21. An example of a physical Scrum Board
  • 22. Scrum Events Prescribed events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum. All events are time-boxed events, such that every event has a maximum duration.
  • 23. Scrum Events - Sprint Planning The work to be performed in the Sprint is planned at the Sprint Planning. This 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. The Scrum Master ensures that the event takes place and that attendants understand its purpose. The Scrum Master teaches the Scrum Team to keep it within the time-box.
  • 24. Scrum Events - Sprint Planning Sprint Planning answers the following: ➔ What can be delivered in the Increment resulting from the upcoming Sprint? ➔ How will the work needed to deliver the Increment be achieved?
  • 25. Sprint Goal The Sprint Goal is an objective set for the Sprint. It provides guidance to the Development Team on why it is building the Increment. It is created during the Sprint Planning meeting. Scrum Events - Sprint Planning
  • 26. Scrum Events - Daily Scrum/Daily Stand-up 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. This is done by inspecting the work since the last Daily Scrum and forecasting the work that could be done before the next one. The Daily Scrum is held at the same time and place each day to reduce complexity.
  • 27. Scrum Events - Daily Scrum/Daily Stand-up During the meeting, the Development Team members explain: ➔ What did I do yesterday that helped the Development Team meet the Sprint Goal? ➔ What will I do today to help the Development Team meet the Sprint Goal? ➔ Do I see any impediment that prevents me or the Development Team from meeting the Sprint Goal?
  • 28. Scrum Events - Daily Scrum/Daily Stand-up The Development Team or team members often meet immediately after the Daily Scrum for detailed discussions, or to adapt, or replan, the rest of the Sprint’s work. Daily Scrums improve communications, eliminate other meetings, identify impediments to development for removal, highlight and promote quick decision-making, and improve the Development Team’s level of knowledge. This is a key inspect and adapt meeting.
  • 29. Scrum Events - Sprint Review/Demo A Sprint Review is held at the end of the Sprint to inspect the Increment and adapt the Product Backlog if needed. During the Sprint Review, the Scrum Team and stakeholders collaborate about what was done in the Sprint. This is an informal meeting, not a status meeting, and the presentation of the Increment is intended to elicit feedback and foster collaboration.
  • 30. Scrum Events - Sprint Review/Demo The Sprint Review includes the following elements: ➔ Attendees include the Scrum Team and key stakeholders invited by the Product Owner; ➔ The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”; ➔ The Development Team discusses what went well during the Sprint, what problems it ran into, and how those problems were solved; ➔ The Development Team demonstrates the work that it has “Done” and answers questions about the Increment; ➔ The Product Owner discusses the Product Backlog as it stands. He or she projects likely completion dates based on progress to date (if needed); ➔ The entire group collaborates on what to do next, so that the Sprint Review provides valuable input to subsequent Sprint Planning; ➔ Review of how the marketplace or potential use of the product might have changed what is the most valuable thing to do next; and, ➔ Review of the timeline, budget, potential capabilities, and marketplace for the next anticipated release of the product.
  • 31. Scrum Events - Sprint Retrospective The Sprint Retrospective is an opportunity for the Scrum Team to inspect itself and create a plan for improvements to be enacted during the next Sprint. The Sprint Retrospective occurs after the Sprint Review and prior to the next Sprint Planning.
  • 32. Scrum Events - Sprint Retrospective The purpose of the Sprint Retrospective is to: ➔ Inspect how the last Sprint went with regards to people, relationships, process, and tools; ➔ Identify and order the major items that went well and potential improvements; and, ➔ Create a plan for implementing improvements to the way the Scrum Team does its work.
  • 33. CREDITS Presentation template by SlidesCarnival Photographs by Death to the Stock Photo (license) SOURCES http://agilemethodology.org/ http://scrummethodology.com/ http://searchsoftwarequality.techtarget.com/definition/Scrum http://scrumreferencecard.com/scrum-reference-card/ http://www.scrumguides.org/scrum-guide.html http://www.synagila.com/wp-content/uploads/2014/01/scrum-board.jpg https://amareshv.files.wordpress.com/2011/03/fairydustboard_20110324.jpg https://www.mountaingoatsoftware.com/agile/new-to-agile-or-scrum