I'd like to discuss what you consider being best practices.
Here is a quick list I put together. Let us know what you think
- freeze Rails (whatever version you use)
- freeze the gems used in your project
- use piston to freeze Rails
- use piston to install plugins
- use a test suite (RSpec FTW)
- have a test coverage of at least 1:1
- don't commit if the tests don't pass
- Keep your code under SCM (SVN, Git...)
- always keep the repository in "deployment" state
- always use an automatic deployment method (capistrano or Vlad
or ...)
- continuous integration (using cruiscontrol.rb for instance)
- tab = 2 spaces
And here is a list I consider being really important when I work on a
project:
- each task should have its user story
- each story should have its acceptance criteria
- each acceptance criteria should have its test
- projects should be broken down in iterations (a week or 2)
- an iteration should have a list of tasks
- prioritize the iteration tasks
- have 1 iteration planning meeting per iteration (~1 hour, with the
full team involved + client)
- have 1 retrospective per iteration (~1 hour, with the full team
involved )
- have a weekly demo with the client
- have at least 1 deployment per iteration(staging or production)
- have a daily 5 minutes stand-up with team + client
What do you consider best practices? What did I forget? Any comments
on my list?
-Matt
p.s: make sure to use the new Google Group mailing list :)
--
--------
http://railsontherun.com
_______________________________________________
Sdruby mailing list
[email protected]
http://lists.sdruby.com/mailman/listinfo/sdruby
