Scrum process under specific extremely short conditions
17
Extreme SCRUM Software Development Methodology for Fast Changing Environment Technical Director at CERTICON: http://www.certicon.cz Co-founder of Agile Consortium at Czech Republic: http://agilnikonsorcium.cz Agile blog: http://soch.cz/blog Zuzana Šochová [email protected], [email protected]
-
Upload
agileee -
Category
Technology
-
view
1.915 -
download
0
description
Slides from Zuzana Sochova talking at Agileee conference 2009, Ukraine
Transcript of Scrum process under specific extremely short conditions
Extreme SCRUM
Soft
war
e D
evel
op
men
t M
eth
od
olo
gy fo
r
Fast
Ch
angi
ng
Envi
ron
men
t
Technical Director at CERTICON: http://www.certicon.cz
Co-founder of Agile Consortium at Czech Republic: http://agilnikonsorcium.cz
Agile blog: http://soch.cz/blog
Zuzana Šochová[email protected], [email protected]
• Introduction - LOI Case Study
• Specifics
• Practices
• Results
• Difficulties
Presentation Outline
for my MBA dissertationhttp://soch.cz/agilesurvey.html
- How to start Agile?
- What did we learned?
- How tight must be Agile with
the company culture?
Agile Adoption Survey 2009
Web solutions
LOI Case Study - Introduction
Standard products, low customization
LOI Case Study - Introduction
Long-term customers
Partnership & Collaboration
LOI Case Study - Introduction
Internet is more than web presentation
Brand marketing
Sales marketing
Introduce to the new customers
Persuade customers
Keep existing customers
Poor project & time management
Poor estimates
Late delivery
No customer relationship
High customization
Difficult design
LOI Case Study – Starting Point
Lot of Idea Company
Small company
3 people
Short-term projects
Hours
Strict delivery conditions
‘On time or free’
Lot of Idea Case - Specifics
Scrum method with half-day Sprint:
What We Did and Why
WHY?
• Average task 2h
• Web solution in 3days
• E-shop in 5days
Low overhead x
Fast reaction to the project status
Half day Sprint including–Pre-Planning & Planning
– Stand-up meeting
–Point estimations
– Tasks in backlog
–Reflection meeting
LOI – Beginning SCRUM
At the Beginning…
– Extremely fast
–No backup
–Dependent on the customer responses
– Strict business model
–High risk
Difficulties
… Couple Weeks Later
–Half-day Sprint
– Stand-up meetings every half-day
–Pre-planning and planning
– Early customer communication
–Communication within the team
– Team cooperation
Summary – What We Did…
In 2 months we‘ve been able to fix:
–Predictability
–On-time delivery
–Customer satisfaction
–Increase velocity by 30%
Conclusion
Zuzana Šochová[email protected]
http://www.certicon.cz
http://soch.cz/blog
Please help me with Agile Adoption Survey:
http://soch.cz/agilesurvey.html
Thank you for your attention
