Since I was writing about some of the challenges to this approach in my
last post, I thought I'd write about some of the potential advantages that
have been occurring to me over dinner. Here are some things that such an
organisation *could* do (probably not all of them, this is just
brainstorming):

   1. Provide a shared experience to clients regarding workflow process,
   particularly with regard to project management, communication and issue
   logging tools. Ie, if all the developers in the group agree to use the same
   tools, it's easier for the client to understand how to integrate a second
   developer, switch developers, etc.
   2. Provide a single point of entry to clients for workflow tools. Not
   only is the process between developers the same, but the client doesn't
   need to change accounts, etc. Adding issues against a given project
   automatically brings it to the attention of the right developer.
   3. Provide some volume discounts to developers for using some
   development tools.
   4. Provide a backup person for all client/developer relationships (I
   mentioned this already). Every developer would be another developer's
   backup. Your backup can call you at home in the middle of the night if you
   aren't responding to the client.
   5. Possibly provide support contracts from the collective, not an
   individual developer.
   6. Run an internal code review process, review each other's code via
   github.
   7. Build a shared name in relation to commits to some key open source
   projects. A shared policy of spending time in certain projects (presumably
   related to business goals) could help the group get know for being experts
   in those projects (which the group would actually become of course).
   8. Provide consistant and understandable rates (beware of price fixing
   laws).
   9. Aggregated blogging

I'm sure there's more.

Craig

-- 
You received this message because you are subscribed to the Google Groups "Ruby 
or Rails Oceania" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/rails-oceania?hl=en.

Reply via email to