It's not a Web2py question. It's a team management point.
As far as Web2py work with MVC (Django, Rails, etc. as well), all pros and cons apply here, too.
It's a matter of your workload approach. Maybe some reading in scrum or other management technique may help you.
-- Vinicius Assef On 08/08/2012 05:39 PM, Luc Chase wrote:
What particular constraints and advantages does using web2py tend to bring for larger project development teams as opposed to those working solo or in very small teams? I assume for example these roles benefit from rapid feedback and ability to adjust requirements more easily? * Project stakeholder (client or business owner) * Project manager * Producer * Editor/copywriter * Information architect * Tech lead * Database administrator * Quality assurance engineer But are these roles less-able or more-able to work in parallel? * Graphic designer * HTML developer * Developer --
--
