Provide a summary of this practice.
Building the Extended Team gives the Core Team access to the information, expertise, authority and resources needed for successful delivery, but which the team does not already contain.
What is the overall goal or intention of this practice?
Building the Extended Team is used:
What are the schedule, cost, quality, frequency, performance or other expectations for completing this practice?
Although Building the Extended Team should be performed at the start of the release, it is also a continuing activity that needs to be reviewed and repeated from time to time as the Release or Iteration proceeds.
What must have happened or been delivered for this practice to be considered complete?
The Extended Team must always be defined well enough for the Core Team to be confident that it can successfully deliver all commitments for the foreseeable future.
At the very least, this should include all work in the current Release.
What pre-conditions must be met before this practice is used?
Building the Extended Team cannot realistically begin until the Core Team has a defined Release backlog.
This view shows a simplified version of this process. For full details, explanation and advice, click on the ‘Detailed process’ tab. For background such as entry and exit conditions, click on the ‘Context’ tab.
|1||Create Context Diagram.|
|2||Identify Core Team’s stakeholders|
|3||Define specific dependency|
|5||Set up mechanisms|
|1||Create Context Diagram.||Iteration Lead.|
|2||Identify Core Team’s stakeholders||Iteration Lead.|
|3||Define specific dependency||Iteration Lead.|
|Draft dependency log|
|4||Build relationship||Product Lead.|
|Relationship agreements||It is important that all relationships should be based on explicit agreements. It is likely that, when either side comes under pressure, their respective commitment is likely to be reinterpreted unpredictably.|
Agreements do not need to be formal, but they do need to include:
|5||Set up mechansisms||Iteration Lead.|
|Management mechanisms||Typical mechanisms:|
Issues & risks
What are the key concerns in making a success of this practice?
- Members of the Extended Team will have their own goals, priorities, processes, timescales, authorities…
- The Core Team needs to understand and respect these.
- Simply because it lies outside the Core team, the Extended Team represents a permanent risk to delivery.
- This may case delays, conflicting priorities, etc.
- If at all possible, skills or experience the team finds it needs regularly should be brought into the Agile team.