This document discusses an agile toolkit and development practices at eBuddy. It introduces the author, Niels Verdonk, as VP of Development at eBuddy. It provides overviews of scrum roles and artifacts. It discusses maintaining cohesion between onshore and offshore development teams. It promotes various agile practices like XP, lean, kanban, testing, and continuous integration. Test automation is emphasized as an important tool that pays off over time through faster feedback and bug fixing.

1. Copyright © eBuddy B.V. All rights reserved. August 25th, 2010 AgileToolkit

2. 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 NielsVerdonk VP Development eBuddy @nverdo

3. Scrum in a nutshell 3Roles Product Owner Scrum Master Team 3 Artifacts Product Backlog Sprint Backlog Burndown Chart 3 Ceremonies The Planning Daily Scrum Review Meeting SM Team PO

4. 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

5. 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

6. AgileToolkit

7. Scrum Agile Umbrella XP Lean Kanban Test Automation Release Burndown Self organization Continuous Integration DOD Pair Programming TDD Limit WIP

8. 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

9. My Top 3 Tools Unit Testing Continuous Integration Test Automation

10. Agile Testing Quadrants

11. 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

12. Cost of Bugs

13. 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 feature

14. AgileToolkit Put it in your Agile Toolkit!

15. Demo time ? 15

16. Q & A ? 16