Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>Here are a few issues that should be thought about:</p> <ul> <li>What is the exact mandate for the architecture team?</li> <li>What is the architecture team's deliverable? A framework, guidelines, implementation help... Or are they just <a href="http://www.joelonsoftware.com/items/2008/05/01.html" rel="noreferrer">Architecture Astronauts</a>?</li> <li>Is this only for applications going forward, or will this be a backport?</li> <li>Who will be responsible for backporting? (And we mean budget here...)</li> <li>Will there be resources allocated to testing the backports?</li> <li>Does the Architecture Team have real muscle, or will management's will fold when the first group grouses about the 4 months it will take to implement the changes...</li> <li>How will you deal with the friction between the individual project groups and the architure team (and there will be friction?). Opportunists will take this as a wonderful opportunity to jockey for position...</li> <li>Be aware that this will be primarily a political game...</li> </ul> <p>My friend, you have a tough road ahead...</p> <p>The <strong>first</strong> step is to be crystal clear on what the architecture team is supposed to achieve.<br> Why are you putting the team in place?<br> Are you trying to unify all the applications, develop a common framework, what?<br> What is the mandate and the vision for this team?</p> <p>Whoever the lead on this team better have kick a** interpersonal skills.<br> It should <strong>not</strong> be the brilliant coder that can whistle the star wars theme song and make light saber noises... but he should probably be on the team in a technical capacity.</p> <p>You should probably populate the team with people that are familiar with the majority of the projects. I would be wary of selecting <em>all</em> the current leads, as that might take a big chunk of knowledge from the current teams. And let's face it, those teams have to be productive while the architecture team comes up with its own deliverables.</p>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

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