How difficult should it be?

The basics of a team structure to drive from continuos customer dialog to delivery of result.

1. The Need Team
   1. Someone submits an idea for review (basically a change request from anyone)
   2. The team reviews the idea and assigns it a status
   3. Inform the other teams of relevant status constantly
   4. Inform the stakeholders (don’t forget the Someone) of relevant status constantly
2. The Architecture Team
   1. The idea is investigated to reveal it’s constituent parts
   2. The team runs several impact analyses on the repository based upon data about the idea
   3. Define the would be result of the change as part of a transition architecture
   4. Inform the other teams of relevant status constantly
3. The Program Team
   1. Create a change proposal (could be a project or some other type of job)
   2. Submit the change proposal and review it
   3. Prioritize among the changes in the portfolio
   4. Perform a trade off analysis
   5. Inform the other teams of relevant status constantly
4. The Production Manager Team
   1. Investigate resource utilization (Resource plan)
   2. Update the list of things to do (backlog) with the new change
   3. Assign responsible (project manager/team) to the task of resolving the change
   4. Inform the other teams of relevant status constantly
5. The Task Team
   1. Analyse and plan work (sprints)
   2. Do work and make sure it works
   3. Inform the other teams of relevant status constantly
   4. Deliver result
6. The Production Team
   1. Prepare production to receive result
   2. Put result into production
   3. Monitor result in production
   4. Inform the other teams of relevant status constantly

Guiding thoughts:

• An individual could participate in many teams
• Yes, there need to be some separation of concern when working with larger changes
• No, not all things end up as software
• Configure if the urge is there
• Consensus is a good state but may not always be reached
• Think different, think for your selves