Must admit site is funny; I almost bought the t-shirt. I don't mean to imply any particular methodology (even though I do tend to favour evolutionary, functional prototyping methods hence my interest in Web2py). I'm more interested in how larger web dev projects are affected (or not) by the integrated nature of web2py, regardless of the dev methology used. Can larger teams work collaboratively just as easily with web2py as with say very lightweight frameworks (or perhaps more easily)? My belief is that they can, but it is only my belief. There are some who say that the architecture of web2py is likely to make it more difficult to separate the concerns of the various team members.
-- Luc On Wednesday, 8 August 2012 21:39:20 UTC+1, 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 > - Business-systems analyst > - 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 > > --
