Agile toolkit mo conf
-
Upload
niels-verdonk -
Category
Documents
-
view
1.356 -
download
2
description
Transcript of Agile toolkit mo conf
Copyright © eBuddy B.V. All rights reserved.
August 25th, 2010
AgileToolkit
About
• eBuddy has just been introduced by Onno– I ‘manage’ the development teams
• A bit about me:– 15 yrs industry experience
• Developer, Team Lead, Architect, Consultant• Moved to eBuddy to do product development
– Passionate about• Technology; Java, Design Patterns, Web & Mobile• Agile methods; Scrum, XP, CI, PP, TDD, Lean
– Management style• Lead by Example• Facilitator, Coach
Niels VerdonkVP Development eBuddy
@nverdo
Scrum in a nutshell
• 3 Roles– Product Owner– Scrum Master– Team
• 3 Artifacts– Product Backlog– Sprint Backlog– Burndown Chart
• 3 Ceremonies– The Planning– Daily Scrum– Review Meeting
PO
SM
Team
Development Team Size
• It motivates developers to have responsibility
• It works both ways; when we ask them to commit– They also want to be involved in the recruitment process
Quar-ter
Q3-2006
Q4-2006
Q1-2007
Q2-2007
Q3-2007
Q4-2007
Q1-2008
Q2-2008
Q3-2008
Q4-2008
Q1-2009
Q2-2009
Q3-2009
Q4-2009
Q1-2010
Q2-2010
Q3-2010
Q4-2010
Q1-2011
0
5
10
15
20
25
30
35
40
Developers
Left Team
Offshore
We want:• Share the eBuddy team feeling• Focus on Lean & Agile values• Remain efficient & Improve
We don’t want:• Isolated teams (Us vs Them)• Communication issues
Local
Backend
LT
LT
LT
LT
LT
Mobile I
LT
LT
LT
LT
Remote
Web
LT
LT
LT
LT
LT
Mobile II
LT RT
Mobile III
LT
RTLT
RT
RT
RT
RTLT
LT
LT
AgileToolkit
Scrum
Agile Umbrella
XP
ContinuousIntegration Pair
Programming
Kanban LeanTestAutomation
ReleaseBurndown
DOD
LimitWIP
Self organization
TDD
Use your Toolkit
• Continuously try to improve– More efficient, less waste
• Different problems require different tools– Some tools may not be right for you
• Sometimes you need to look for new tools– Try something new
My Top 3 Tools
• Unit Testing• Continuous Integration• Test Automation
Agile Testing Quadrants
Cost of Manual Testing
• Start of a project – Only a few tests to run– Easy to be done manually– Not live / limited users
• Over time this increases– Manual testing takes too long– Product in production, a lot of
people affected by bugs
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 160.0
5.0
10.0
15.0
20.0
25.0
30.0
35.0
Regression
Tests
Cost of Bugs
Software Development Stage Fix
Requirements and Design 5 mins
Code and Unit Testing 15 mins
Integration and System Testing 1 hour
Beta Testing 2 hour
Post Release 1 day
Test Automation – Do it!
• Preferable from the start– Small investment for each story– Tests can be run often at no cost– Fast feedback, quick fixes
• We didn’t do it from the start – It’s never too late to start!– It’s not going to be easy, but will
still pay back big time!– Just start now! Start writing new
tests with each new feature1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
0.0
5.0
10.0
15.0
20.0
25.0
30.0
35.0
Regression
Tests
AgileToolkit
Put it in your Agile Toolkit!
15
Demo time
?
16
Q & A
?