scrum powerpt
TRANSCRIPT
APPLICATION OF SCRUM METHODOLOGY IN A BUSINESS
INCUBATOR INCUBIO
Alina TsikhanavaDegree in Business and ITJuly 2014
Project GoalProject
Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
“We are using Scrum.”
Is it really Scrum?
MethodProject
Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
• Scrum Theory:• Scrum Guide• Scrum.org• Scrum Alliance
• ScrumButs:
• Incubio:• Interviews• Observation
Agile Emergence
Agile values:• Responding to change over following a plan• Customer collaboration over contract negotiation• Working software over comprehensive documentation• Individuals and interactions over processes and tools
BackgroundProject
Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
AgileEmpirical. Learning cycles
Welcomes changes
Light-weight. Incremental deliverySelf-organization
WaterfallUp-front planning.
PredictiveIntolerance to changes
Abundant documentation
Heavy regulation
1956 1990’s
BackgroundProject
Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
Scrum
• An agile framework for complex projects.
• Developed by K. Schwaber and J. Sutherland in early 1990’s.
• Teaches how to treat emerging challenges.
• Requires to keep everything visible and react on an empirical basis.
Scrum TheoryProject
Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
3 Concepts:
• Iterative and incremental delivery
• Bottom-up thinking
• Empiricism
Scrum Theory. Iterative and Incremental Delivery
Project Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
Sprints of 1-4 weeks
• reduce risk of cost
• address complexity
• working product version available
• stakeholders trust the Development Team
• keep the Team motivated
Scrum Theory.Bottom-up Thinking
Project Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
Empowering people who do the work: Self-management, self-organization
Scrum Team:• Product Owner. Customer
• Development Team. Development
• Scrum Master. Servant-leader
Scrum Theory.Empiricism
Project Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
3 basic ideas:
• Transparency 3 Artifacts:
• Inspection
• Adaptation
Sprint Backlog
Product Backlog
Increment
Sprint Review
Daily Scrum
Sprint Planning
Sprint Retrospective
4 Events:
Scrum Theory.Empiricism
Project Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
Source: Jansma, N., Mulder, T., Nikhogosyan, M. (2011). Scrum Beyond Software. How Dialogues Incubator Goes Agile.
ScrumButsProject
Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
Each component within the framework serves a specific purpose and is essential to Scrum’s success and usage. – Scrum Guide.
“We use Scrum, BUT (excuse) (workaround).”
Example: “We use Scrum, BUT
(our team is dispersed over various time zones), (so we have Daily Scrums whenever we can).”
ScrumButsProject
Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
• Goalless, soulless Scrum• Fractional theory implementation and
premature Scrum adaptations
• Protracted planning
• Scrum Master in a role of a project manager
• Competition among the team members
• Rehearsed demos
• Problem recurrence
ScrumButs.Good and Bad ScrumButs
Project Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
Good deviations remain within the Scrum framework and stay in harmony with all Agile values and principles.
Previously: “Follow the Scrum Guide.”
So are changes allowed or not?Skill acquisition model Shu Ha Ri:• Shu - novice level. Follows the rules. • Ha - expert level. Allowed to break rules. • Ri - master level. Can create their own approaches.
Good Deviation: Product Backlog is ordered, not prioritized. Building a house in the tropics with the main purpose of protecting you from the daily afternoon rain
Incubio.First Interview. VP of Engineering
Project Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
A startup incubator specialized in technological projects related to Big Data.
•Scrum TeamVP
Engineering
Start-up 1
Internal SM
PO
Dev. Team
Start-up 2
Internal SM
PO
Dev. Team
Start-up 3
Internal SM
PO
Dev. Team
Start-up 4
Internal SM
PO
Dev. Team
Start-up 5
Internal SM
PO
Dev. Team
Start-up n
Internal SM
PO
Dev. Team
IT Manager (Tech Lead)
IT Manager
(Tech Lead)
Incubio.First Interview. VP of Engineering
Project Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
•Scrum Master Performance.Scrum Coaching
•Visibility of the Process. JIRA Software. Scrum Board
•Workflow. Sprints. Events prescribed. Tweaked Sprint Planning. Only Done functionality presented
•Product Backlog. User stories. 1-2 Sprints
•Human Resourses Activities.Intragroups dynamics
Incubio.Second Interview. Quizlyse, CTO
Project Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
Inspection-adaptation. Estimates and effective time spent
Iterations as learning cycles. Better estimates in half a year
Product Owner, also CEO. Doesn’t believe in Scrum
Incubio.Third Interview. Groupiest. Daily Scrum
Project Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
Daily Scrum
Incubio.Third Interview. Groupiest. PO and SM
Project Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
Visibility. JIRA only
Sprints duration. 2 weeks from experience
Non-professional teams. Advantages
Product Owner. Multidiscipline. Marketing people help
Precise estimates. Too precise
ConclusionsProject
Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
Incubio is Agile
iterative delivery
customer collaboration
the teams are self-organizing and self-managing
changes are expected and accepted
motivated individuals
workspace perfect for close collaboration
ConclusionsProject
Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
3 Concepts:
Iterative and incremental delivery Bottom-up thinking Empiricism
ConclusionsProject
Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
Goalless, soulless Scrum
Fractional theory implementation and premature Scrum
adaptations
Protracted planning
Scrum Master in a role of a project manager
Competition among the team members
Rehearsed demos
Problem recurrence
ConclusionsProject
Goal
Method
Background
Scrum Theory
ScrumButs
Incubio
Conclusions
VP
Engineering
Start-up 1
Internal SM
PO
Dev. Team
Start-up 2
Internal SM
PO
Dev. Team
Start-up 3
Internal SM
PO
Dev. Team
Start-up 4
Internal SM
PO
Dev. Team
Start-up 5
Internal SM
PO
Dev. Team
Start-up n
Internal SM
PO
Dev. Team
IT Manager (Tech Lead)
IT Manager (Tech Lead) Ha Level
Shu Level
• Incubio. The Big Data Academy. The Scrum Academy as well.
• The individuals
• Scrum - “The art of the possible”
Thank you!