1. HOW AGILE IS RAILS?
Face the necessary trouble.

2. JOSÉ MOTA
Senior Interaction Designer @ Iuz Technologies

3. I WANNA MAKE MONEY.
You guys want it too.

4. BUT I CARE MORE ABOUT
BEING HAPPY.
Do you?

5. THE AGILE MANIFESTO
It serves a holistic purpose:
to acknowledge the future in human behavior.

6. HOW AGILE IS RAILS?
How does it affect human behavior?

7. WORKING SOFTWARE

8. $ RAILS NEW
AWESOME_APP

9. MVC & CONVENTIONS
BUILT-IN.
Start doing your app.
Focus on the what, not the how.

10. $ RAKE TEST
OR
$ RSPEC
The framework (how) is tested,
start testing your app (what).

11. DEVELOPER’S PROFIT

12. DEVELOPER’S PROFIT
Less development time.

13. DEVELOPER’S PROFIT
Less development time.
Less headaches.

14. DEVELOPER’S PROFIT
Less development time.
Less headaches.
More time to document, contribute and learn.

15. BOSS’ PROFIT

16. BOSS’ PROFIT
More confidence on the team.

17. BOSS’ PROFIT
More confidence on the team.
Better response to clients.

18. CUSTOMER
COLLABORATION

19. FRAMEWORK
+
STRONG CONVENTIONS
=
SPEED

20. > SPEED
⇳
> PEER REVIEW RATIO

21. > PEER REVIEW RATIO
⇳
> SENSE TRUST AND
BELONGING

22. BUILD TRUST, CLIENTS
STICK AROUND.

23. DEVELOPER’S PROFIT
You get to keep your job.

24. BOSS’ PROFIT

25. BOSS’ PROFIT
You get to keep your clients. And your job.

26. BOSS’ PROFIT
You get to keep your clients. And your job.
A new sense of management. Collaboration, rather.

27. BOSS’ PROFIT
You get to keep your clients. And your job.
A new sense of management. Collaboration, rather.
Responsibility is better balanced.

28. RESPONSE TO CHANGE

29. TEST-DRIVEN
DEVELOPMENT
Pick your change:
Unitary
Integration
Acceptance

30. TDD GRANTS CONFIDENCE
ON THE DESIGN.

31. TDD + RUBY = AWESOME
SAUCE

33. SOURCE CONTROL
Use it how it’s meant to be used.
Rails has a .gitignore file and everything!

34. DATABASES
It supports data, not the app.

35. SQL?
Migrations – keep your database controlled over time.
Schema is always up to date.

36. USING COUCH OR MONGO?
They’re agile by nature, move along.

37. DEVELOPER’S PROFIT

38. DEVELOPER’S PROFIT
It’s freakin’ Ruby.

39. DEVELOPER’S PROFIT
It’s freakin’ Ruby.
Express yourself: type less, do more.

40. DEVELOPER’S PROFIT
It’s freakin’ Ruby.
Express yourself: type less, do more.
Less debugs.

41. DEVELOPER’S PROFIT
It’s freakin’ Ruby.
Express yourself: type less, do more.
Less debugs.
Come home sooner.

42. BOSS’ PROFIT.

43. BOSS’ PROFIT.
A better, more confident team.

44. BOSS’ PROFIT.
A better, more confident team.
More confident towards clients.

45. INDIVIDUALS AND
INTERACTIONS

46. THE TOOL / PROCESS IS
RAILS.
Stop worrying about it.

47. ITERATIVE / INCREMENTAL
DEVELOPMENT
More confidence on the present.

48. WORK WITH YOUR
CLIENTS,
NOT FOR THEM.

49. ABOUT PEOPLE AND
CHANGE...

50. IT'S 2012,
WE'RE INFORMATION
JUNKIES!
Of course we can change.

51. CLIENTS CHANGE THEIR
MINDS.
Deal with it.

52. YOU CAN’T AFFORD
PREDICTION.
Don’t think ahead (too much).

53. DEVELOPER’S PROFIT

54. DEVELOPER’S PROFIT
No prediction, no overkill.

55. DEVELOPER’S PROFIT
No prediction, no overkill.
Time to invest on good design with good tests.

56. BOSS’ PROFIT
Start projects right away.

57. LONG STORY SHORT?
I looked at code for the first time when I was eleven.

58. LONG STORY SHORT?

59. YOU WILL FACE TROUBLE.
Just avoid the unnecessary.

60. Github: josemota Twitter: @josemotanet
BE HAPPY.
Thank you.
❦
Come talk to me!