Slide 1

Slide 1 text

Agile Web Development in ten minutes Willy Ekasalim Panggi Libersa Jasri Akadol

Slide 2

Slide 2 text

Why Agile?  Lets compare it with Waterfall model:  Requirement -> Design -> Coding -> Maintenance.  Big design up front.  Then become too big to adapt changes.  OK for stable project, unchanging requirements.  Web requirements change from time to time right? so be Agile!

Slide 3

Slide 3 text

What¶s Agile?  It¶s actually many mini-Waterfalls

Slide 4

Slide 4 text

What¶s Agile (continue..)?  So every mini-Waterfalls is a Iteration  Adapt fast to changes, quick decision making.  An Iteration is short 1 week or 2 week.  Involve Pair Programming  Monday: create and assign tasks.  Tuesday: design, code, and test.  Wednesday: design, code, and test.  Thursday: design, code, and test.  Friday: Demo day, deploy, relax, research, tech talks.

Slide 5

Slide 5 text

More on Agile  Bullpen or open space office. No barrier.  Just talk, suggest, and discuss anytime!

Slide 6

Slide 6 text

Agile Tools  Continuous Integration (CI) Server  Developer needs quick feedback when they check-in code.

Slide 7

Slide 7 text

Agile Tools  Open Source CI server  Hudson and Cruise Control.  Online/Cloud Agile Project Management  Support Iteration development style.  Feature backlog or defect backlog  Example: Assembla, XP-Dev, Acunote, and more«

Slide 8

Slide 8 text

Agile Nature of Ruby on Rails  Faster development  Active Record for Object Relational Mapping  One language only for everything: Ruby  No need to learn other languages.  Less amount of codes.  DRY ( Don't Repeat Yourself )  Built in Testing Framework

Slide 9

Slide 9 text

http://bistip.com http://twitter.com/bistip http://facebook.com/bistip