Skip to main content

Team Structures

Task Driven Team​

A task driven team operates by utilising a Kanban style to process tasks that are generally unrelated and of short duration. These teams are flexible and work is prioritised constantly based on changing circumstances.

iterative

Best suited for:

  • Teams where lots of individual tasks come in to be completed
  • Eg BAU requests, service requests, very small projects
  • Low complexity, short duration pieces of work
  • Focus is on throughput and closure of items

Iterative Team​

An iterative model is a cut down version of the Product Domain team model. It can operate by utilising a combination of Kanban and Scrum practices.

iterative

Best suited for

  • Small projects of short or defined duration
  • Some interlinked tasks as well as small independent tasks
  • Small teams
  • Can be Scrum based or task based
  • Small set (generally 1) stakeholder
  • Basic reporting requirements
  • Teams where resources may not be long-standing

Product Domain Team​

A product domain team is a long-living team that adds to and maintains a fixed set of software assets (Products). It has foxed core roles and can scale as needed. The domain knowledge of the system(s) is maintained in the team and work can come in from multiple sources and is prioritised. There are Ways of Working practices around the JIRA setup, roles and reporting to aid the Project Management teams to track work and progress.

iterative

Best suited for

  • Long standing teams with established core roles and people assigned
  • Demand coming from multiple projects
  • Serving a select set of products (Software assets or systems)
  • Diverse range of stakeholders
  • Team manages support, system maintenance and new system development
  • Clear, standardised reporting needed for PD and PM’s
  • Requirements can be waterfall or iterative in nature
Last updated on