SlideShare une entreprise Scribd logo
1  sur  48
Télécharger pour lire hors ligne
An
Introduction to
Agile SCRUM Methodology
PresumptionsPresumptions
The audience is well aware of traditional
software development methodologies like
Waterfall Model, Iterative models, etc.
AgendaAgenda
 Introduction
 What is Agile Methodology?
 What is Scrum?
 History of Scrum
 Functionality of Scrum
 Components of Scrum
 Scrum Roles
 The Process
 Scrum Artifacts
 Scaling Scrum
 Q & A Session
IntroductionIntroduction
Classical methods of software development have
many disadvantages:
 huge effort during the planning phase
 poor requirements conversion in a rapid changing
environment
 treatment of staff as a factor of production
 New methods:
Agile Software Development Methodology
What is Agile ?What is Agile ?
 Agile proponents believe
 Current software development processes are too
heavyweight or cumbersome
 Too many things are done that are not directly related to
software product being produced
 Current software development is too rigid
 Difficulty with incomplete or changing requirements
 Short development cycles (Internet applications)
 More active customer involvement needed
 CMM focuses on process
Contd…Contd…
 Agile methods are considered
 Lightweight
 People-based rather than Plan-based
 Several agile methods
 No single agile method
 XP most popular
 No single definition
 Agile Manifesto closest to a definition
 Set of principles
 Developed by Agile Alliance
Agile ManifestoAgile Manifesto
A Statement of Values
 Individuals and interactions over processes and
tools
 Working software over comprehensive
documentation
 Customer collaboration over contract negotiation
 Responding to change over following a plan
 http://www.agilemanifesto.org
Agile MethodsAgile Methods
 Agile methods:
 Scrum
 Extreme Programming
 Adaptive Software Development (ASD)
 Dynamic System Development Method (DSDM)
 …
 Agile Alliance (www.agilealliance.org)
 A non-profit organization promotes agile
development
ScrumScrum
Scrum in 100 wordsScrum in 100 words
Scrum is an agile process that allows us to focus on
delivering the highest business value in the shortest
time.
It allows us to rapidly and repeatedly inspect actual
working software (every two weeks to one month).
The business sets the priorities. Our teams self-manage
to determine the best way to deliver the highest
priority features.
Every two weeks to a month anyone can see real working
software and decide to release it as is or continue to
enhance for another iteration.
History of ScrumHistory of Scrum
 1995:
 analysis of common software development processes  not suitable for empirical,
unpredictable and non-repeatable processes
 Design of a new method: Scrum by Jeff Sutherland & Ken Schwaber
 Enhancement of Scrum by Mike Beedle & combination of Scrum with Extreme
Programming
 1996:
introduction of Scrum at OOPSLA conference
 2001:
publication “Agile Software Development with Scrum” by
Ken Schwaber & Mike Beedle
 Successful appliance of Scrum in over 50 companies
Founders are members in the Agile Alliance
CharacteristicsCharacteristics
 Self-organizing teams
 Product progresses in a series of month-long “sprints”
 Requirements are captured as items in a list of
“product backlog”
 No specific engineering practices prescribed
 Uses generative rules to create an agile environment
for delivering projects
 One of the “agile processes”
How Scrum Works?How Scrum Works?
SprintsSprints
 Scrum projects make progress in a series of
“sprints”
 Analogous to XP iterations
 Target duration is one month
 +/- a week or two
 But, a constant duration leads to a better
rhythm
 Product is designed, coded, and tested during
the sprint
Sequential vs. Overlapping Dev.Sequential vs. Overlapping Dev.
Requirements Design Code Test
No changes during the sprintNo changes during the sprint
SprintInputs Tested Code
Change
 Plan sprint durations around how long you
can commit to keeping change out of the
sprint
Scrum FrameworkScrum Framework
 Roles : Product Owner, ScrumMaster, Team
 Ceremonies : Sprint Planning, Sprint Review,
Sprint Retrospective, & Daily Scrum Meeting
 Artifacts : Product Backlog, Sprint Backlog,
and Burndown Chart
Product OwnerProduct Owner
 Define the features of the product
 Decide on release date and content
 Be responsible for the profitability of the
product (ROI)
 Prioritize features according to market value
 Adjust features and priority every iteration, as
needed
 Accept or reject work results.
The Scrum MasterThe Scrum Master
 Represents management to the project
 Responsible for enacting Scrum values and practices
 Removes impediments
 Ensure that the team is fully functional and productive
 Enable close cooperation across all roles and
functions
 Shield the team from external interferences
Scrum TeamScrum Team
 Typically 5-10 people
 Cross-functional
 QA, Programmers, UI Designers, etc.
 Members should be full-time
 May be exceptions (e.g., System Admin, etc.)
 Teams are self-organizing
 What to do if a team self-organizes someone off the team??
 Ideally, no titles but rarely a possibility
 Membership can change only between sprints
CeremoniesCeremonies
 Sprint Planning Meeting
 Sprint
 Daily Scrum
 Sprint Review Meeting
Spring Planning MeetingSpring Planning Meeting
Sprint Planning
Meeting
Product Backlog
Team Capabilities
Business Conditions
Technology
Current Product
Sprint Backlog
ProductO
wner
Scrum
Team
M
anagem
ent
Custom
ers
Sprint Goal
Parts of Sprint Planning MeetingParts of Sprint Planning Meeting
 1st
Part:
 Creating Product Backlog
 Determining the Sprint Goal.
 Participants: Product Owner, Scrum Master,
Scrum Team
 2nd
Part:
 Participants: Scrum Master, Scrum Team
 Creating Sprint Backlog
Pre-Project/Kickoff MeetingPre-Project/Kickoff Meeting
 A special form of Sprint Planning Meeting
 Meeting before the begin of the Project
SprintSprint
 A month-long iteration, during which is
incremented a product functionality
 NO outside influence can interfere with the
Scrum team during the Sprint
 Each Sprint begins with the Daily Scrum
Meeting
Daily ScrumDaily Scrum
 Parameters
 Daily
 15-minutes
 Stand-up
 Not for problem solving
 Three questions:
1. What did you do yesterday
2. What will you do today?
3. What obstacles are in your way?
 Chickens and pigs are invited
 Help avoid other unnecessary meetings
 Only pigs can talk
Daily ScrumDaily Scrum
 Is NOT a problem solving session
 Is NOT a way to collect information about
WHO is behind the schedule
 Is a meeting in which team members make
commitments to each other and to the Scrum
Master
 Is a good way for a Scrum Master to track the
progress of the Team
Scrum FAQsScrum FAQs
 Why daily?
 “How does a project get to be a year late?”
 “One day at a time.”
 Fred Brooks, The Mythical Man-Month.
 Can Scrum meetings be replaced by emailed status
reports?
 No
 Entire team sees the whole picture every day
 Create peer pressure to do what you say you’ll do
Sprint Review MeetingSprint Review Meeting
 Team presents what it
accomplished during the sprint
 Typically takes the form of a
demo of new features or
underlying architecture
 Informal
 2-hour prep time rule
 Participants
 Customers
 Management
 Product Owner
 Other engineers
Sprint Retrospective MeetingSprint Retrospective Meeting
 Scrum Team only
 Feedback meeting
 Three questions
 Start
 Stop
 Continue
 Don’t skip for the first 5-6 sprints!!!
Product BacklogProduct Backlog
 A list of all desired work on the project
 Usually a combination of
 story-based work (“let user search and
replace”)
 task-based work (“improve exception
handling”)
 List is prioritized by the Product Owner
 Typically a Product Manager, Marketing, Internal
Customer, etc.
Product BacklogProduct Backlog
 Requirements for a system, expressed as a
prioritized list of Backlog Items
 Is managed and owned by a Product Owner
 Spreadsheet (typically)
 Usually is created during the Sprint Planning
Meeting
 Can be changed and re-prioritized before
each PM
Sample Product BacklogSample Product Backlog
From Sprint Goal to Sprint BacklogFrom Sprint Goal to Sprint Backlog
 Scrum team takes the Sprint Goal and
decides what tasks are necessary
 Team self-organizes around how they’ll meet
the Sprint Goal
 Manager doesn’t assign tasks to individuals
 Managers don’t make decisions for the team
 Sprint Backlog is created
Sprint Backlog during the SprintSprint Backlog during the Sprint
 Changes
 Team adds new tasks whenever they need to in
order to meet the Sprint Goal
 Team can remove unnecessary tasks
 But: Sprint Backlog can only be updated by the
team
 Estimates are updated whenever there’s new
information
Sprint BacklogSprint Backlog
 A subset of Product Backlog Items, which
define the work for a Sprint
 Is created ONLY by Team members
 Each Item has it’s own status
 Should be updated every day
Sprint BacklogSprint Backlog
 No more than 300 tasks in the list
 If a task requires more than 16 hours, it
should be broken down
 Team can add or subtract items from the list.
Product Owner is not allowed to do it
Sample Sprint BacklogSample Sprint Backlog
Sprint Burn down ChartSprint Burn down Chart
 Depicts the total Sprint Backlog hours
remaining per day
 Shows the estimated amount of time to
release
 Ideally should burn down to zero to the end of
the Sprint
 Actually is not a straight line
 Can bump UP
Information RadiatorInformation Radiator
"Two characteristics are key to a good
information radiator. The first is that the
information changes over time. This makes it
worth a person's while to look at the display...
The other characteristic is that it takes very
little energy to view the display."
Sprint Burndown ChartSprint Burndown Chart
Progress
752 762
664
619
304
264
180
104
200
100
200
300
400
500
600
700
800
900
5/3/2002
5/5/20025/7/2002
5/9/2002
5/11/2002
5/13/2002
5/15/2002
5/17/2002
5/19/2002
5/21/2002
5/23/2002
5/25/2002
5/27/2002
5/29/2002
5/31/2002
Date
RemainingEffortinHours
Release Burndown ChartRelease Burndown Chart
 Will the release be done on right time?
 X-axis: sprints
 Y-axis: amount of hours remaining
 The estimated work remaining can also burn
up
Product Burndown ChartProduct Burndown Chart
 Is a “big picture” view of project’s progress (all
the releases)
Scalability of ScrumScalability of Scrum
 A typical Scrum team is 6-10 people
 Jeff Sutherland - up to over 800 people
 "Scrum of Scrums" or what called "Meta-
Scrum“
 Frequency of meetings is based on the
degree of coupling between packets
Scalability of ScrumScalability of Scrum
Scalability of ScrumScalability of Scrum
Pros/ConsPros/Cons
 Advantages
 Completely developed and
tested features in short
iterations
 Simplicity of the process
 Clearly defined rules
 Increasing productivity
 Self-organizing
 each team member carries
a lot of responsibility
 Improved communication
 Combination with Extreme
Programming
 Drawbacks
 “Undisciplined hacking”
(no written
documentation)
 Violation of
responsibility
 Current mainly carried
by the inventors
Thank You !!!

Contenu connexe

Tendances

An introduction to scrum 2.0
An introduction to scrum 2.0An introduction to scrum 2.0
An introduction to scrum 2.0ITSON
 
Scrum guide presentation (Scrum Guide in easy to read PPT format)
Scrum guide presentation (Scrum Guide in easy to read PPT format)Scrum guide presentation (Scrum Guide in easy to read PPT format)
Scrum guide presentation (Scrum Guide in easy to read PPT format)Aloke Bhattacharya
 
Agile Scrum software methodology
Agile Scrum software methodologyAgile Scrum software methodology
Agile Scrum software methodologyAbdullah Raza
 
An Introduction to Scrum
An Introduction to ScrumAn Introduction to Scrum
An Introduction to Scrummbalas2
 
Scrum Roles and artifacts
Scrum Roles and artifactsScrum Roles and artifacts
Scrum Roles and artifactsNaresh Jain
 
agile with scrum methodology
agile with scrum methodology agile with scrum methodology
agile with scrum methodology rahul reddy
 
Scrum Introduction
Scrum IntroductionScrum Introduction
Scrum IntroductionJames Brett
 
Introduction To Scrum
Introduction To ScrumIntroduction To Scrum
Introduction To Scrumvineet
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrumtimmcowan
 
Scrum process powerpoint ppt slides.
Scrum process powerpoint ppt slides.Scrum process powerpoint ppt slides.
Scrum process powerpoint ppt slides.SlideTeam.net
 
Redistributable Intro To Scrum
Redistributable Intro To ScrumRedistributable Intro To Scrum
Redistributable Intro To ScrumErwin Verweij
 
Scrum 101
Scrum 101Scrum 101
Scrum 101beLithe
 
Introduction to Project Management with Scrum
Introduction to Project Management with ScrumIntroduction to Project Management with Scrum
Introduction to Project Management with ScrumPierre E. NEIS
 
Scrum Methodology well elucidated
Scrum Methodology well elucidatedScrum Methodology well elucidated
Scrum Methodology well elucidatedMuhammad Asim
 
Introduction into Scrum
Introduction into ScrumIntroduction into Scrum
Introduction into Scrummsorin
 

Tendances (20)

Introduction to Scrum - Agile Methods
Introduction to Scrum - Agile MethodsIntroduction to Scrum - Agile Methods
Introduction to Scrum - Agile Methods
 
An introduction to scrum 2.0
An introduction to scrum 2.0An introduction to scrum 2.0
An introduction to scrum 2.0
 
The Scrum Model
The Scrum ModelThe Scrum Model
The Scrum Model
 
Seminar On Scrum
Seminar On  ScrumSeminar On  Scrum
Seminar On Scrum
 
Scrum guide presentation (Scrum Guide in easy to read PPT format)
Scrum guide presentation (Scrum Guide in easy to read PPT format)Scrum guide presentation (Scrum Guide in easy to read PPT format)
Scrum guide presentation (Scrum Guide in easy to read PPT format)
 
2017 Scrum by Picture
2017 Scrum by Picture2017 Scrum by Picture
2017 Scrum by Picture
 
Agile Scrum software methodology
Agile Scrum software methodologyAgile Scrum software methodology
Agile Scrum software methodology
 
An Introduction to Scrum
An Introduction to ScrumAn Introduction to Scrum
An Introduction to Scrum
 
Scrum Roles and artifacts
Scrum Roles and artifactsScrum Roles and artifacts
Scrum Roles and artifacts
 
agile with scrum methodology
agile with scrum methodology agile with scrum methodology
agile with scrum methodology
 
Scrum Introduction
Scrum IntroductionScrum Introduction
Scrum Introduction
 
Introduction To Scrum
Introduction To ScrumIntroduction To Scrum
Introduction To Scrum
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrum
 
Scrum process powerpoint ppt slides.
Scrum process powerpoint ppt slides.Scrum process powerpoint ppt slides.
Scrum process powerpoint ppt slides.
 
Redistributable Intro To Scrum
Redistributable Intro To ScrumRedistributable Intro To Scrum
Redistributable Intro To Scrum
 
Scrum 101
Scrum 101Scrum 101
Scrum 101
 
Introduction to Project Management with Scrum
Introduction to Project Management with ScrumIntroduction to Project Management with Scrum
Introduction to Project Management with Scrum
 
Scrum Methodology well elucidated
Scrum Methodology well elucidatedScrum Methodology well elucidated
Scrum Methodology well elucidated
 
Introduction into Scrum
Introduction into ScrumIntroduction into Scrum
Introduction into Scrum
 
Introduction to Scrum
Introduction to ScrumIntroduction to Scrum
Introduction to Scrum
 

Similaire à Dot+Net+2010+Features

Agile Methodology in Software Development
Agile Methodology in Software DevelopmentAgile Methodology in Software Development
Agile Methodology in Software DevelopmentRaghav Seth
 
Agile Scrum Presentation-Detailed
Agile Scrum Presentation-DetailedAgile Scrum Presentation-Detailed
Agile Scrum Presentation-DetailedPrashaanth T R
 
Scrum Primer
Scrum PrimerScrum Primer
Scrum Primerdavelucey
 
Agile Process Introduction
Agile Process IntroductionAgile Process Introduction
Agile Process IntroductionNguyen Hai
 
Agile & SCRUM
Agile & SCRUMAgile & SCRUM
Agile & SCRUMejlp12
 
scrum-1-10.pptx
scrum-1-10.pptxscrum-1-10.pptx
scrum-1-10.pptxheelojr
 
Agile Scrum - Overview
Agile Scrum - OverviewAgile Scrum - Overview
Agile Scrum - OverviewMadan Upadhyay
 
Agile Development with Scrum.pptx
Agile Development with Scrum.pptxAgile Development with Scrum.pptx
Agile Development with Scrum.pptxzuma14
 
scrumppt-14057094134-php
scrumppt-14057094134-phpscrumppt-14057094134-php
scrumppt-14057094134-phpHelenCandy2
 
Presentation: "Agile methodologies for Project Management - SCRUM" by Varty K...
Presentation: "Agile methodologies for Project Management - SCRUM" by Varty K...Presentation: "Agile methodologies for Project Management - SCRUM" by Varty K...
Presentation: "Agile methodologies for Project Management - SCRUM" by Varty K...varty
 
Black Marble Introduction To Scrum
Black Marble Introduction To ScrumBlack Marble Introduction To Scrum
Black Marble Introduction To ScrumBusinessQuests
 
Intro-to-scrum
Intro-to-scrumIntro-to-scrum
Intro-to-scrumEslam Diaa
 
Software Engineering Agile methodology SCRUM
Software Engineering  Agile methodology SCRUM Software Engineering  Agile methodology SCRUM
Software Engineering Agile methodology SCRUM Hamza7777
 
Agile Software Development with Scrum
Agile Software Development with ScrumAgile Software Development with Scrum
Agile Software Development with ScrumChris Brown
 

Similaire à Dot+Net+2010+Features (20)

Agile Methodology in Software Development
Agile Methodology in Software DevelopmentAgile Methodology in Software Development
Agile Methodology in Software Development
 
Agile Scrum Presentation-Detailed
Agile Scrum Presentation-DetailedAgile Scrum Presentation-Detailed
Agile Scrum Presentation-Detailed
 
Scrum Primer
Scrum PrimerScrum Primer
Scrum Primer
 
Agile Process Introduction
Agile Process IntroductionAgile Process Introduction
Agile Process Introduction
 
Agile & SCRUM
Agile & SCRUMAgile & SCRUM
Agile & SCRUM
 
Agile Scrum Project Management
Agile Scrum Project ManagementAgile Scrum Project Management
Agile Scrum Project Management
 
scrum-1-10.pptx
scrum-1-10.pptxscrum-1-10.pptx
scrum-1-10.pptx
 
Agile Scrum - Overview
Agile Scrum - OverviewAgile Scrum - Overview
Agile Scrum - Overview
 
Agile Development with Scrum.pptx
Agile Development with Scrum.pptxAgile Development with Scrum.pptx
Agile Development with Scrum.pptx
 
Seminar on Scrum
Seminar  on  ScrumSeminar  on  Scrum
Seminar on Scrum
 
scrumppt-14057094134-php
scrumppt-14057094134-phpscrumppt-14057094134-php
scrumppt-14057094134-php
 
Scrum ppt
Scrum pptScrum ppt
Scrum ppt
 
Presentation: "Agile methodologies for Project Management - SCRUM" by Varty K...
Presentation: "Agile methodologies for Project Management - SCRUM" by Varty K...Presentation: "Agile methodologies for Project Management - SCRUM" by Varty K...
Presentation: "Agile methodologies for Project Management - SCRUM" by Varty K...
 
Black Marble Introduction To Scrum
Black Marble Introduction To ScrumBlack Marble Introduction To Scrum
Black Marble Introduction To Scrum
 
Agile processes scrum
Agile processes scrumAgile processes scrum
Agile processes scrum
 
Intro-to-scrum
Intro-to-scrumIntro-to-scrum
Intro-to-scrum
 
Scrum and Agile SDLC 101
Scrum and Agile SDLC 101Scrum and Agile SDLC 101
Scrum and Agile SDLC 101
 
Software Engineering Agile methodology SCRUM
Software Engineering  Agile methodology SCRUM Software Engineering  Agile methodology SCRUM
Software Engineering Agile methodology SCRUM
 
Agile Software Development with Scrum
Agile Software Development with ScrumAgile Software Development with Scrum
Agile Software Development with Scrum
 
Agile Methodologies - Project Management with SCRUM
Agile Methodologies - Project Management with SCRUMAgile Methodologies - Project Management with SCRUM
Agile Methodologies - Project Management with SCRUM
 

Plus de gurbaxrawat

Plus de gurbaxrawat (9)

Jogging
JoggingJogging
Jogging
 
Business.......
Business.......Business.......
Business.......
 
Techno+......
Techno+......Techno+......
Techno+......
 
Health+PPPPPP
Health+PPPPPPHealth+PPPPPP
Health+PPPPPP
 
Entertail+Present+....
Entertail+Present+....Entertail+Present+....
Entertail+Present+....
 
Edu+Presentation
Edu+PresentationEdu+Presentation
Edu+Presentation
 
dffdf
dffdfdffdf
dffdf
 
test11211
test11211test11211
test11211
 
Model question paper_mc0061
Model question paper_mc0061Model question paper_mc0061
Model question paper_mc0061
 

Dernier

ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDEADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDELiveplex
 
UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8DianaGray10
 
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostKubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostMatt Ray
 
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...Aggregage
 
Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Adtran
 
VoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBXVoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBXTarek Kalaji
 
Empowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership BlueprintEmpowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership BlueprintMahmoud Rabie
 
Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024SkyPlanner
 
Videogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdfVideogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdfinfogdgmi
 
Machine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdfMachine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdfAijun Zhang
 
Bird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystemBird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystemAsko Soukka
 
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationUsing IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationIES VE
 
Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024D Cloud Solutions
 
Designing A Time bound resource download URL
Designing A Time bound resource download URLDesigning A Time bound resource download URL
Designing A Time bound resource download URLRuncy Oommen
 
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Will Schroeder
 
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPAAnypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPAshyamraj55
 
AI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity WebinarAI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity WebinarPrecisely
 
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesAI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesMd Hossain Ali
 
COMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a WebsiteCOMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a Websitedgelyza
 

Dernier (20)

ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDEADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
ADOPTING WEB 3 FOR YOUR BUSINESS: A STEP-BY-STEP GUIDE
 
UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8UiPath Studio Web workshop series - Day 8
UiPath Studio Web workshop series - Day 8
 
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCostKubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
KubeConEU24-Monitoring Kubernetes and Cloud Spend with OpenCost
 
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
The Data Metaverse: Unpacking the Roles, Use Cases, and Tech Trends in Data a...
 
Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™Meet the new FSP 3000 M-Flex800™
Meet the new FSP 3000 M-Flex800™
 
VoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBXVoIP Service and Marketing using Odoo and Asterisk PBX
VoIP Service and Marketing using Odoo and Asterisk PBX
 
Empowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership BlueprintEmpowering Africa's Next Generation: The AI Leadership Blueprint
Empowering Africa's Next Generation: The AI Leadership Blueprint
 
Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024Salesforce Miami User Group Event - 1st Quarter 2024
Salesforce Miami User Group Event - 1st Quarter 2024
 
Videogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdfVideogame localization & technology_ how to enhance the power of translation.pdf
Videogame localization & technology_ how to enhance the power of translation.pdf
 
20230104 - machine vision
20230104 - machine vision20230104 - machine vision
20230104 - machine vision
 
Machine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdfMachine Learning Model Validation (Aijun Zhang 2024).pdf
Machine Learning Model Validation (Aijun Zhang 2024).pdf
 
Bird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystemBird eye's view on Camunda open source ecosystem
Bird eye's view on Camunda open source ecosystem
 
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve DecarbonizationUsing IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
Using IESVE for Loads, Sizing and Heat Pump Modeling to Achieve Decarbonization
 
Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024Artificial Intelligence & SEO Trends for 2024
Artificial Intelligence & SEO Trends for 2024
 
Designing A Time bound resource download URL
Designing A Time bound resource download URLDesigning A Time bound resource download URL
Designing A Time bound resource download URL
 
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
Apres-Cyber - The Data Dilemma: Bridging Offensive Operations and Machine Lea...
 
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPAAnypoint Code Builder , Google Pub sub connector and MuleSoft RPA
Anypoint Code Builder , Google Pub sub connector and MuleSoft RPA
 
AI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity WebinarAI You Can Trust - Ensuring Success with Data Integrity Webinar
AI You Can Trust - Ensuring Success with Data Integrity Webinar
 
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just MinutesAI Fame Rush Review – Virtual Influencer Creation In Just Minutes
AI Fame Rush Review – Virtual Influencer Creation In Just Minutes
 
COMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a WebsiteCOMPUTER 10 Lesson 8 - Building a Website
COMPUTER 10 Lesson 8 - Building a Website
 

Dot+Net+2010+Features

  • 2. PresumptionsPresumptions The audience is well aware of traditional software development methodologies like Waterfall Model, Iterative models, etc.
  • 3. AgendaAgenda  Introduction  What is Agile Methodology?  What is Scrum?  History of Scrum  Functionality of Scrum  Components of Scrum  Scrum Roles  The Process  Scrum Artifacts  Scaling Scrum  Q & A Session
  • 4. IntroductionIntroduction Classical methods of software development have many disadvantages:  huge effort during the planning phase  poor requirements conversion in a rapid changing environment  treatment of staff as a factor of production  New methods: Agile Software Development Methodology
  • 5. What is Agile ?What is Agile ?  Agile proponents believe  Current software development processes are too heavyweight or cumbersome  Too many things are done that are not directly related to software product being produced  Current software development is too rigid  Difficulty with incomplete or changing requirements  Short development cycles (Internet applications)  More active customer involvement needed  CMM focuses on process
  • 6. Contd…Contd…  Agile methods are considered  Lightweight  People-based rather than Plan-based  Several agile methods  No single agile method  XP most popular  No single definition  Agile Manifesto closest to a definition  Set of principles  Developed by Agile Alliance
  • 7. Agile ManifestoAgile Manifesto A Statement of Values  Individuals and interactions over processes and tools  Working software over comprehensive documentation  Customer collaboration over contract negotiation  Responding to change over following a plan  http://www.agilemanifesto.org
  • 8. Agile MethodsAgile Methods  Agile methods:  Scrum  Extreme Programming  Adaptive Software Development (ASD)  Dynamic System Development Method (DSDM)  …  Agile Alliance (www.agilealliance.org)  A non-profit organization promotes agile development
  • 10. Scrum in 100 wordsScrum in 100 words Scrum is an agile process that allows us to focus on delivering the highest business value in the shortest time. It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month). The business sets the priorities. Our teams self-manage to determine the best way to deliver the highest priority features. Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance for another iteration.
  • 11. History of ScrumHistory of Scrum  1995:  analysis of common software development processes  not suitable for empirical, unpredictable and non-repeatable processes  Design of a new method: Scrum by Jeff Sutherland & Ken Schwaber  Enhancement of Scrum by Mike Beedle & combination of Scrum with Extreme Programming  1996: introduction of Scrum at OOPSLA conference  2001: publication “Agile Software Development with Scrum” by Ken Schwaber & Mike Beedle  Successful appliance of Scrum in over 50 companies Founders are members in the Agile Alliance
  • 12. CharacteristicsCharacteristics  Self-organizing teams  Product progresses in a series of month-long “sprints”  Requirements are captured as items in a list of “product backlog”  No specific engineering practices prescribed  Uses generative rules to create an agile environment for delivering projects  One of the “agile processes”
  • 13. How Scrum Works?How Scrum Works?
  • 14. SprintsSprints  Scrum projects make progress in a series of “sprints”  Analogous to XP iterations  Target duration is one month  +/- a week or two  But, a constant duration leads to a better rhythm  Product is designed, coded, and tested during the sprint
  • 15. Sequential vs. Overlapping Dev.Sequential vs. Overlapping Dev. Requirements Design Code Test
  • 16. No changes during the sprintNo changes during the sprint SprintInputs Tested Code Change  Plan sprint durations around how long you can commit to keeping change out of the sprint
  • 17. Scrum FrameworkScrum Framework  Roles : Product Owner, ScrumMaster, Team  Ceremonies : Sprint Planning, Sprint Review, Sprint Retrospective, & Daily Scrum Meeting  Artifacts : Product Backlog, Sprint Backlog, and Burndown Chart
  • 18. Product OwnerProduct Owner  Define the features of the product  Decide on release date and content  Be responsible for the profitability of the product (ROI)  Prioritize features according to market value  Adjust features and priority every iteration, as needed  Accept or reject work results.
  • 19. The Scrum MasterThe Scrum Master  Represents management to the project  Responsible for enacting Scrum values and practices  Removes impediments  Ensure that the team is fully functional and productive  Enable close cooperation across all roles and functions  Shield the team from external interferences
  • 20. Scrum TeamScrum Team  Typically 5-10 people  Cross-functional  QA, Programmers, UI Designers, etc.  Members should be full-time  May be exceptions (e.g., System Admin, etc.)  Teams are self-organizing  What to do if a team self-organizes someone off the team??  Ideally, no titles but rarely a possibility  Membership can change only between sprints
  • 21. CeremoniesCeremonies  Sprint Planning Meeting  Sprint  Daily Scrum  Sprint Review Meeting
  • 22. Spring Planning MeetingSpring Planning Meeting Sprint Planning Meeting Product Backlog Team Capabilities Business Conditions Technology Current Product Sprint Backlog ProductO wner Scrum Team M anagem ent Custom ers Sprint Goal
  • 23. Parts of Sprint Planning MeetingParts of Sprint Planning Meeting  1st Part:  Creating Product Backlog  Determining the Sprint Goal.  Participants: Product Owner, Scrum Master, Scrum Team  2nd Part:  Participants: Scrum Master, Scrum Team  Creating Sprint Backlog
  • 24. Pre-Project/Kickoff MeetingPre-Project/Kickoff Meeting  A special form of Sprint Planning Meeting  Meeting before the begin of the Project
  • 25. SprintSprint  A month-long iteration, during which is incremented a product functionality  NO outside influence can interfere with the Scrum team during the Sprint  Each Sprint begins with the Daily Scrum Meeting
  • 26. Daily ScrumDaily Scrum  Parameters  Daily  15-minutes  Stand-up  Not for problem solving  Three questions: 1. What did you do yesterday 2. What will you do today? 3. What obstacles are in your way?  Chickens and pigs are invited  Help avoid other unnecessary meetings  Only pigs can talk
  • 27. Daily ScrumDaily Scrum  Is NOT a problem solving session  Is NOT a way to collect information about WHO is behind the schedule  Is a meeting in which team members make commitments to each other and to the Scrum Master  Is a good way for a Scrum Master to track the progress of the Team
  • 28. Scrum FAQsScrum FAQs  Why daily?  “How does a project get to be a year late?”  “One day at a time.”  Fred Brooks, The Mythical Man-Month.  Can Scrum meetings be replaced by emailed status reports?  No  Entire team sees the whole picture every day  Create peer pressure to do what you say you’ll do
  • 29. Sprint Review MeetingSprint Review Meeting  Team presents what it accomplished during the sprint  Typically takes the form of a demo of new features or underlying architecture  Informal  2-hour prep time rule  Participants  Customers  Management  Product Owner  Other engineers
  • 30. Sprint Retrospective MeetingSprint Retrospective Meeting  Scrum Team only  Feedback meeting  Three questions  Start  Stop  Continue  Don’t skip for the first 5-6 sprints!!!
  • 31. Product BacklogProduct Backlog  A list of all desired work on the project  Usually a combination of  story-based work (“let user search and replace”)  task-based work (“improve exception handling”)  List is prioritized by the Product Owner  Typically a Product Manager, Marketing, Internal Customer, etc.
  • 32. Product BacklogProduct Backlog  Requirements for a system, expressed as a prioritized list of Backlog Items  Is managed and owned by a Product Owner  Spreadsheet (typically)  Usually is created during the Sprint Planning Meeting  Can be changed and re-prioritized before each PM
  • 33. Sample Product BacklogSample Product Backlog
  • 34. From Sprint Goal to Sprint BacklogFrom Sprint Goal to Sprint Backlog  Scrum team takes the Sprint Goal and decides what tasks are necessary  Team self-organizes around how they’ll meet the Sprint Goal  Manager doesn’t assign tasks to individuals  Managers don’t make decisions for the team  Sprint Backlog is created
  • 35. Sprint Backlog during the SprintSprint Backlog during the Sprint  Changes  Team adds new tasks whenever they need to in order to meet the Sprint Goal  Team can remove unnecessary tasks  But: Sprint Backlog can only be updated by the team  Estimates are updated whenever there’s new information
  • 36. Sprint BacklogSprint Backlog  A subset of Product Backlog Items, which define the work for a Sprint  Is created ONLY by Team members  Each Item has it’s own status  Should be updated every day
  • 37. Sprint BacklogSprint Backlog  No more than 300 tasks in the list  If a task requires more than 16 hours, it should be broken down  Team can add or subtract items from the list. Product Owner is not allowed to do it
  • 38. Sample Sprint BacklogSample Sprint Backlog
  • 39. Sprint Burn down ChartSprint Burn down Chart  Depicts the total Sprint Backlog hours remaining per day  Shows the estimated amount of time to release  Ideally should burn down to zero to the end of the Sprint  Actually is not a straight line  Can bump UP
  • 40. Information RadiatorInformation Radiator "Two characteristics are key to a good information radiator. The first is that the information changes over time. This makes it worth a person's while to look at the display... The other characteristic is that it takes very little energy to view the display."
  • 41. Sprint Burndown ChartSprint Burndown Chart Progress 752 762 664 619 304 264 180 104 200 100 200 300 400 500 600 700 800 900 5/3/2002 5/5/20025/7/2002 5/9/2002 5/11/2002 5/13/2002 5/15/2002 5/17/2002 5/19/2002 5/21/2002 5/23/2002 5/25/2002 5/27/2002 5/29/2002 5/31/2002 Date RemainingEffortinHours
  • 42. Release Burndown ChartRelease Burndown Chart  Will the release be done on right time?  X-axis: sprints  Y-axis: amount of hours remaining  The estimated work remaining can also burn up
  • 43. Product Burndown ChartProduct Burndown Chart  Is a “big picture” view of project’s progress (all the releases)
  • 44. Scalability of ScrumScalability of Scrum  A typical Scrum team is 6-10 people  Jeff Sutherland - up to over 800 people  "Scrum of Scrums" or what called "Meta- Scrum“  Frequency of meetings is based on the degree of coupling between packets
  • 47. Pros/ConsPros/Cons  Advantages  Completely developed and tested features in short iterations  Simplicity of the process  Clearly defined rules  Increasing productivity  Self-organizing  each team member carries a lot of responsibility  Improved communication  Combination with Extreme Programming  Drawbacks  “Undisciplined hacking” (no written documentation)  Violation of responsibility  Current mainly carried by the inventors