Back

Forming a scrum team with the right size and skills is important in the delivery of any product. This is a critical part of the initiation phase of an Agile project. There are multiple deliverables within each sprint, and team members will need to be self-organising with a breadth of skills.

Scrum team formation is primarily managed by the team’s product owner. The product owner carries the vision of the organisation and as the individual responsible for the product backlog, they should have the greatest insight into the skills required to deliver prioritised features. Since the scrum master is one of the first team members identified, most product owners will engage this individual in identifying skills and the people who can best deliver.

Within Scrum teams, teams members are cross-functional with the specific technical skills to complete the product. Scrum Team members also support the rest of the team. The best teams are goal oriented and have 6 team members, give or take three. Unlike traditional project teams, the testing resources are not within silos’ in a separate part of the organisation.  As a cross-functional team, the development team consists of developers, testers, solution architects, and all of the other roles required to complete the product.

Testing is an important step in the delivery of shippable features and as such will need to be planned and executed to deliver the product. These shippable features will then need to be approved by the product owner during the sprint review ceremony.

Testers are involved throughout the project, and play crucial roles within the sprint and project ceremonies.  These ceremonies include the:

  • Backlog Development,
  • Sprint Planning
  • Sprint Review, and
  • Sprint Retrospective.

Backlog Development

The product owner is responsible for taking the product vision and dissecting it into workable features. These workable features are then prioritised according to value. According to Jeff Sutherland – co-creator of the Scrum framework for Agile – business value is defined by 3 dimensions:

  • What the customer wants
  • What can be sustain-ably delivered and
  • What the team is excited about delivering

The last metric is one that is commonly overlooked and should play a large part in selecting the scrum team members, particularly those with testing skills and responsibilities. In traditional project management, testers are viewed as strict gate-keepers with little knowledge of the actual product, and little enthusiasm for the product.  While this may not always be accurate, finding scrum team members who are invested in delivering high value products for the customers within each sprint is of paramount importance.

The features in the product backlog may require specific technical skills that test team members must have. Testers should have a wide array of testing skills – developing test plans, executing and clearly identifying defects, and good communication skills for quickly providing feedback to the developers. Having specialised testing skills is important in the formation of a scrum team.

Having a diversity in testing experience is beneficial for the scrum team. Testers with experience can quickly identify blockers that will impact the prioritisation of features. Experienced testers will also have other skills such as analysis or development. These are invaluable in terms of having a better understanding of the product delivery techniques and being in a position to assist other scrum team members. Likewise, having less experienced testers on the team will enable mentor engagement and active participation in sprint delivery thus expanding their skills during the life of product delivery and for future initiatives.

Recommended Further Reading

The following materials may assist you in order to get the most out of this course:

Section 2: Using the Agile Manifesto to Deliver Change

Section 3: The 12 Agile Principles

Section 4: The Agile Fundamentals

Section 5: The Declaration of Interdependence

Section 6: Agile Development Frameworks

Section 7: Introduction to Scrum

Section 8: Scrum Projects

Section 9: Scrum Project Roles

Section 10: Meet the Scrum Team

Section 11: Building the Scrum Team

Section 12: Scrum in Projects, Programs & Portfolios

Section 13: How to Manage an Agile Project

Section 14: Leadership Styles

Section 15: The Agile Project Life-cycle

Section 16: Business Justification with Agile

Section 17: Calculating the Benefits With Agile

Section 18: Quality in Agile

Section 19: Acceptance Criteria and the Prioritised Product Backlog

Section 20: Quality Management in Scrum

Section 21: Change in Scrum

Section 22: Integrating Change in Scrum

Section 23: Managing Change in Scrum

Section 24: Risk in Scrum

Section 25: Risk Assessment Techniques

Section 26: Initiating an Agile Project

Section 27: Forming the Scrum Team

Section 28: Epics and Personas

Section 29: Creating the Prioritised Product Backlog

Section 30: Conduct Release Planning

Section 31: The Project Business Case

Section 32: Planning in Scrum

Section 33: Scrum Boards

Section 34: Sprint Planning

Section 35: User Stories

Section 36: User Stories and Tasks

Section 37: The Sprint Backlog

Section 38: Implementation of Scrum

Section 39: The Daily Scrum

Section 40: The Product Backlog

Section 41: Scrum Charts

Section 42: Review and Retrospective

Section 43: Scrum of Scrums

Section 44: Validating a Sprint

Section 45: Retrospective Sprint

Section 46: Releasing the Product

Section 47: Project Retrospective

Section 48: The Communication Plan

Section 49: Formal Business Sign-off

Section 50: Scaling Scrum

Section 51: Stakeholders

Section 52: Programs and Portfolios

Translate »