Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Interesting question.</p> <p>First, you have to have a clear notion of what problem this "architecture" team is solving. If you can not clearly define the "mission" of the team it will fail and do it with great big explosions. :)</p> <p>That being said, the first step is define the problem you are solving. Are you trying to keep up with technology? Are you trying to incorporate some code reuse between projects? Are you trying to utilize your development staff to the best possible effect? There are several reasons to implement an architecture team and given your setup, any one of these might be sufficent. From your question, it looks like your goal is reworking the existing apps so that is a good first step.</p> <p>Since you already have a group of leads that have good specific knowledge of the apps it would be a good idea to start with them. Get them together and hash out what the new global architecture should look like. You might also want to get a consultant to help facilitate the conversation at this point. Define the goals of the rework and come out with a "big picture" that everybody can agree to.</p> <p>After that I would take a handful of the leads and promote them (backfilling the leads from the developer pool) to the architecture team. They will then meet with the leads to ensure things are going according to that "Big Picture".</p> <p>I would NOT bring in a whole new group from the outside. That would create an unwanted Us vs. Them dynamic that is never good. The outsiders would also have no idea of how things are supposed to work or why things don't work the way logic would imply they should. :)</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload