Challenges On Adopting Scrum For Home Office Environments
1. Challenges on Adop'ng Scrum for
Distributed Teams in Home Office
Environment
Marlon Luz – Daniel Gazineu – Mauro Teófilo
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
3. Distributed work environments are
characterized by the lack of
proximity between co‐workers.
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
4. People sharing the same
environment tend to have similar
behavior
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
5. While different places drive people
to different behaviors
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
6. Interac've, face‐to‐face
communica'on is the cheapest and
fastest channel for exchanging
informa'on
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
8. In Home Office the group is
completely individually distributed
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
9. In the so/ware development field,
Home Office environments became
popular with the growth of Open
Source communi'es
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
10. Scrum Framework is composed by a
simple set of prac'ces and rules
based on the Agile Manifesto
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
12. There are in Scrum only three roles:
Product Owner, ScrumMaster and
Team Member.
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
13. The Product Owner is the person
responsible for the success of the
product
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
14. The Scrum Master is responsible for
the Scrum process
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
15. Team Members are responsible for
developing the project
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
16. There are also in Scrum three
ar'facts: Product Backlog,
Burndown Chart and Sprint Backlog
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
17. The Product Backlog is a priori'zed
list of requirements, features and
func'onali'es of the project or
product
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
18. The Sprint Backlog is a subset of
func'onali'es from Product Backlog
chosen by the team
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
19. The Burndown Chart is about
transparency and visibility
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
20. The Scrum defines also three
ceremonies: Sprint Planning
mee'ng, Daily Scrum mee'ng and
Sprint Review mee'ng
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
21. Product Owner Role Challenge:
It lies in transferring Product
Owner’s vision of the project to
Team Members
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
22. Share Scrum Visual Elements
Challenge:
Difficulty to share those between
distributed Team Members
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
23. Scrum mee'ngs Challenge:
How to keep a]en'on of so many
people during so many hours across
different places and even possibility
different 'me zones without face‐to‐
face?
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
24. Informa'on share Challenge:
How to transfer complex
informa'on between Team
Members when they do not have
opportunity to create and maintain
strong rela'onships among each
other?
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia
25. Thank you
Ques'ons & Answers
Interna'onal Conference on So/ware Science and Engineering
ICSSE 2009 – Bali, Indonesia