Download - Scrum. software engineering seminar
![Page 1: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/1.jpg)
Scrum
Gavrishev Alexander
![Page 2: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/2.jpg)
What is Scrum?
“Scrum is a framework for developing
complex products and systems. It is grounded
in empirical process control theory. Scrum
employs an iterative, incremental approach to
optimize predictability and control risk.”
-Ken Schwaber
![Page 3: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/3.jpg)
History
• “The New New Product Development Game,”
by Hirotaka Takeuchi, Ikujiro Nonaka, Harvard
Business Review, 1986
• Influenced by best practices in Japanese
industry (Toyota and Honda)
• “Scrum Development Process,” Ken Schwaber
and Jeff Sutherland, OOPSLA 1995
![Page 4: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/4.jpg)
Scrum has been used by
• Microsoft
• Yahoo
• Electronic Arts
• IBM
• Philips
• Nokia
• Apple
• BBC
• Intuit
• Nielsen Media
• Qualcomm
• Texas Instruments
• ...
![Page 5: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/5.jpg)
Scrum has been used for
• Commercial software
• In-house development
• Financial applications
• Embedded systems
• 24x7 systems with
99.999% uptime
requirements
• Video game
development
• Life-critical systems
• Websites
• Mobile phones
• ...
![Page 6: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/6.jpg)
What is Scrum?
![Page 7: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/7.jpg)
What is Scrum?
Scrum is characterised by 3 roles:
• Product Owner, Scrum Master and Team
And, 4 meetings:
• Planning Meeting, Daily Scrum, Review
Meeting and Retrospective
![Page 8: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/8.jpg)
Product owner
• Responsible for maximizing the value of the
product
• Manages for the Product Backlog (items and
prioritization)
• Responsible for the product’s profitability
• Accepts or rejects work results
• Collaborates with both the team and
stakeholders
![Page 9: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/9.jpg)
Team
• Self-organized and cross-functional
• Select and commit to delivery highest-priority
items from the Product Backlog
• Members decide how the work is arranged and
how assignments are distributed.
• Optimal size is small enough to remain nimble
and large enough to complete significant work
within a Sprint
![Page 10: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/10.jpg)
Scrum Master
• Team's coach, helps Scrum practitioners
achieve their highest level of performance
• Shield the team from external interferences
• Works to ensure that the team has the best
possible circumstances for realizing the goals
fixed for the Sprint
![Page 11: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/11.jpg)
What is Scrum?
![Page 12: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/12.jpg)
Product Backlog
• To-do list of the changes of the product
• Constantly reprioritized
• Highest prioritized goals are transferred to a
Sprint Backlog
• Managed solely by Product Owners
![Page 13: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/13.jpg)
Sprint Backlog
• To-do list for a Sprint
• Consists of the with highest priority
• Created during Sprint planning meeting
• Estimated work remaining is updated daily
• Real-time picture of the work that the
Development Team plans to accomplish during
the Sprint
![Page 14: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/14.jpg)
Sprint
![Page 15: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/15.jpg)
Sprint
• Scrum projects make progress in a series of
“sprints”
• Time-box of 2–4 weeks at most
• Product is designed, coded, and tested during
the sprint
• A new Sprint starts immediately after the
conclusion of the previous Sprint
![Page 16: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/16.jpg)
Daily
• 15-minute time-boxed meeting
• Only team members can talk
• Everyone answers 3 questions
o What did they do yesterday?
o What will they do today?
o Is anything on the way?
• Helps avoid other unnecessary meetings
![Page 17: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/17.jpg)
Review & Retrospective
![Page 18: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/18.jpg)
Sprint Review
• Team presents what it accomplished during the
sprint
• Team and stakeholders collaborate about what
was done in the Sprint
• The form of a demo of new features or
underlying architecture
• No slides
![Page 19: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/19.jpg)
Retrospective
• 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
• Create a plan for implementing improvements
to the way the Scrum Team does its work
![Page 20: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/20.jpg)
Product Backlog Example
![Page 21: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/21.jpg)
Sprint Backlog Example
![Page 22: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/22.jpg)
Burndown Chart
![Page 23: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/23.jpg)
Retrospective Example
• What went well? o Team collaboration
o Splitting stories to the tasks
• What could be improved? o Meetings approvals
o Improve code documentation
• Adaptation o Follow meetings invitations
o Meeting about PHPDoc
![Page 24: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/24.jpg)
Issues
• Micromanagement of team members and the
process
• No guidance
• Ignore, customize the agile practices
• Continually fail to deliver product
• Large teams or not cross-functional teams
• Work is declared "done" whether it is done or
not.
![Page 25: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/25.jpg)
Questions?
![Page 26: Scrum. software engineering seminar](https://reader034.vdocuments.site/reader034/viewer/2022051411/5479ae815906b511358b45ad/html5/thumbnails/26.jpg)
References
“The Scrum Guide”, Ken Schwaber and Jeff
Sutherland
“How To Fail With Agile”, Mike Cohn and Clinton
Keith
“Getting Agile with Scrum”, Mike Cohn
“What is Scrum?”, Kane Mar