Cascade #13 –   One Architect/Analyst can generate enough work for two Developers and one Tester; structure your project teams in this ratio.

This is a “rule of thumb” that has been borne out over time. (The ratio may vary a bit from case to case, like when the experience levels are different across the roles.) This ratio combines with the specialization of principle #6 to form the strong basis for the Cascade effect covered in the last principle below. 

I use the most common ‘role titles’ of analyst, designer, developer, and tester for the remainder of this book. Sometimes these roles have different names, and there are many other roles in IT overall, but these four are the most recognizable to anyone doing primarily project work. (And the Project Manager makes five! Can’t forget them…)


Would you recommend this article?

Thanks for taking the time to let us know what you think of this article!
We'd love to hear your opinion about this or any other story you read in our publication. Click this link to send me a note →

Jim Love, Chief Content Officer, IT World Canada
Previous articleWhy can’t healthcare work like an ATM machine?
Next articleCascade #14 – It