Your SlideShare is downloading. ×
  • Like
Agile tour   agile development
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Agile tour agile development

  • 964 views
Published

A presentation of how we apply the principles of Agile Development at 10to1.

A presentation of how we apply the principles of Agile Development at 10to1.

Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
964
On SlideShare
0
From Embeds
0
Number of Embeds
1

Actions

Shares
Downloads
13
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide



















Transcript

  • 1. Agile Development at 10to1 Tom Klaasen
  • 2. Tom Klaasen • Developing software for 10 years • Java/J2EE • Co-founded 10to1 in 2006 • Since 2008: Ruby on Rails, iOS
  • 3. Who is here? • Experience with agile • You want to convince who?
  • 4. People
  • 5. People • 4 developers • Passionnate • Highly skilled
  • 6. Philosophy • Do what we want to do (programming!) • Have fun doing this • “Take your work seriously. Yourself, not so.”
  • 7. “Agile development”? • Communication
  • 8. Communication • Workable application from day 1 • Deployments every few days • Meetings: developers talk with users
  • 9. Communication • “We grow software” • http://blog.10to1.be/general/2010/06/17/ we-grow-software/
  • 10. Communication tools • Telephone • Face-to-face meetings (max. 1/week) • Email • Campfire • Lighthouse • git • Continuous integration • “10to1 Newsletter”
  • 11. Tests • Regression • Unit tests (business logic)
  • 12. What we don’t do • Kanban • Backlog at the beginning of the project • 100% test coverage • Test controllers (thin in Rails) • (Structured) pair programming
  • 13. What we do differently • Stand-up meeting: coffee!
  • 14. The influence of language • Ruby, Rails: Convention over configuration • Java/J2EE: A lot of groundwork
  • 15. Misconceptions • A way to put pression on developers
  • 16. Pain points • Contracts
  • 17. “Agile” • No one way • Philosophy, not rules
  • 18. • Tom Klaasen • tom@10to1.be • 0475 28 17 62 • @10to1