Topic

Agile Team Resource Management

Response

The success of an individual agile teams calls for:

clearly defined set of key results, which the agile team shall be responsible for delivering.
ensuring consistency and long-term engagement of individuals on the agile team.
the adoption of a competency led Agile team design and appointment approach.
team membership is limited to no more than 10.

Adoption of business objectives and key results

For an Agile Team to be successful they must to assigned clear, unambiguous, agreed and achievable set of business objectives and key results. To enable continuous and frequent measuring of the progress of such objectives and key results the adoption of a quarterly business review cycle is recommended.

Long-term engagement of individuals on the agile team

Successful Agile Teams establish a consistent rhythm of work, which allows them to deliver value frequently because they have been assigned to the Agile team for a suitable length of time and that their time allocation is high, so that they’re not consistently context switching between multiple Agile Teams or other work. Click here to learn more.

Competency led Agile team design and appointment approach

Agile teams own the end to end life cycle. From Design and analysis through to adoption and support. To ensure the right individuals join the Agile teams, it is recommended the resource management activities within the organisation follow the Monetical recommended competency led agile team design and appointment approach.

Agile team size and empowerment

Effective Agile Teams have around 6 permanent members (including a Product Owner, Scrum Master and several subject matter experts), and approx 4 additional people who they call upon from time to time (e.g. individual sprints), to support the delivery of a particular sprint goal. Multiple Agile Teams should be formed should the product, service or solution be complex. By limiting membership to 10, will keep the Agile Team focused on delivering value frequently, reduce the need to produce detailed documentation and ensure the effective adoption of the various Agile ceremonies.

Should an agile team become too large its ability to focus on a specific number of deliverables will become difficult as this will introduce further context switching and communication amongst the agile team and its stakeholders will become complex.

Discover more

Additional information, including working examples and templates are available in the Monetical knowledge base.