Create a maintenance role that is dedicated to fielding bug reports and prioritizing them for resolution. Prioritization may come from higher up, but the role could at least asses the reports to explain what the problem is and describe steps to resolve (not actually resolve).
The role would be across all of the apps. Once the role is defined, rotate the team members responsible for it every week or two. It is going to open up communication between the person handling the maintenance role and the person who knows the most about the particular app in question. At the same time, it is going to allow the people in the maintenance role to gain more knowledge about the other apps. We do something similar and I think it would work well in your situation. .:.:.:.:.:.:.:.:.:.:.:.:. Bobby Hartsfield http://acoderslife.com http://cf4em.com -----Original Message----- From: Nathan Strutz [mailto:[email protected]] Sent: Friday, September 02, 2011 3:12 PM To: cf-talk Subject: How do you compose your dev teams? Hi everybody. I have a little management-type dilemma that I can't solve. I'm no manager, so I'm trying to collect info about how other people do it. I work in a small group of CF developers (7 of us) inside a big company (100k+ of us). The way we work is that pretty much everybody owns one or more applications in our group's portfolio of programs (probably 10 apps, 3 or 4 are big & important). My manager has noticed that we don't communicate enough and has started threatening drastic measures, moving people around and putting us where we don't want to be. I am not sure of his motivation, but it may be partially the hit-by-a-bus protection, wondering if his apps will be supported if one of us eats a piece of public transportation. So my question to the list is this: How do you organize your teams of developers successfully? Please let me know what you do, or what you have seen that actually works. I'll start us off. I asked my friend Mario, who says they have a team of core developers that do R&D at a higher level, overseeing the technical direction of their applications. Those R&D projects are flowed out into application development teams, and then they have a lot of other developers who do front-ends and integration work. Regular flow-down meetings help people share ideas and copy & adapt similar projects. Mario's team compositon sounds awesome, but he has a lot more people than I do. What do you do? nathan strutz [www.dopefly.com] [hi.im/nathanstrutz] [about.me/nathanstrutz] ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:347204 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
