SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our User Agreement and Privacy Policy.
SlideShare uses cookies to improve functionality and performance, and to provide you with relevant advertising. If you continue browsing the site, you agree to the use of cookies on this website. See our Privacy Policy and User Agreement for details.
Successfully reported this slideshow.
Activate your 14 day free trial to unlock unlimited reading.
Scrum process under specific extremely short conditions
Scrum process under specific extremely short conditions
1.
Fast Changing Environment
Software Development Methodology for
Zuzana Šochová
zuzana@soch.cz, sochova@certicon.cz
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
Extreme SCRUM
2.
Presentation Outline
• Introduction - LOI Case Study
• Specifics
• Practices
• Results
• Difficulties
3.
Agile Adoption Survey 2009
for my MBA dissertation
http://soch.cz/agilesurvey.html
- How to start Agile?
- What did we learned?
- How tight must be Agile with
the company culture?
5.
LOI Case Study - Introduction
Standard products, low customization
6.
LOI Case Study - Introduction
Long-term customers
Partnership & Collaboration
Sales marketing
Introduce to the
Brand marketing
Internet is more than new customers
web presentation
Keep existing Persuade
customers customers
7.
LOI Case Study – Starting Point
Poor project & time management
Poor estimates
Late delivery
No customer relationship
High customization
Difficult design
9.
Lot of Idea Case - Specifics
Small company
3 people
Short-term projects
Hours
Strict delivery conditions
‘On time or free’
10.
What We Did and Why
Scrum method with half-day Sprint:
WHY?
• Average task 2h
• Web solution in 3days
• E-shop in 5days
Low overhead
x
Fast reaction to the project status
11.
LOI – Beginning SCRUM
Half day Sprint including
– Pre-Planning & Planning
– Stand-up meeting
– Point estimations
– Tasks in backlog
– Reflection meeting
15.
Summary – What We Did…
– Half-day Sprint
– Stand-up meetings every half-day
– Pre-planning and planning
– Early customer communication
– Communication within the team
– Team cooperation
16.
Conclusion
In 2 months we‘ve been able to fix:
–Predictability
–On-time delivery
–Customer satisfaction
–Increase velocity by 30%
17.
Thank you for your attention
Zuzana Šochová
zuzana@soch.cz
http://www.certicon.cz
http://soch.cz/blog
Please help me with Agile Adoption Survey:
http://soch.cz/agilesurvey.html