Back

Scrum Project Roles – Part 11

Communication becomes exponentially harder and more complex as team members increase. More time and effort is spent on communications for larger teams. This is true for team members as well as the Scrum Master. Keeping communication effort down is important since this can start to eat away at productivity. If a team is too small, communication between the team may be easier, but collaboration may become harder. As a Scrum Master, you should consider the nature of the work and what is needed for the team when deciding a team size. This will allow you to keep the team and project going in a productive, efficient manner.

Forming the Scrum Team

Scrum is a framework that encourages delivery of potentially shippable product increments every 2-6 weeks. The work is developed and delivered by the scrum team which is composed of a product owner, scrum master, and development team. In traditional project management or waterfall, the development phases – requirements analysis, coding, testing, and deployment – are done sequentially. Each development phase corresponds to a specific role. Business requirements come from business analysts and product owners; coding is done by developers; testing is executed by software testers, and deployment is made possible by release management professionals.

Traditionally, as all these steps are done in phases, the people working on each phase are people of the same role. For example, during development, all developers work together; during testing, testers interact with fellow testers. Once the code has been turned over, there is no actual interaction between testers and the developers. It is understood that since the phase has ended, the responsibility is handed over as well. In Agile Scrum, all phases are done in one sprint (which spans from 1-6 weeks). This means that all of the significant roles in delivering a potentially shippable product increment are brought together in one team called a scrum team. The scrum team is composed of 6-10 individuals – programmers, testers, business analysts, scrum master and a product owner – that possess the needed skills for development.

59 Seconds Training Video

Master of Agile – Agile Scrum Tester With 59 Seconds Agile (Video Training Course)

Introductory Offer: Free Course

Master of Agile – Agile Scrum Tester With 59 Seconds Agile (Video Training Course)

What is this course?

This ‘Master of Agile – Agile Scrum Tester With 59 Seconds Agile (Video Training Course)’ provides an in-depth understanding of the Agile Scrum Tester roles and responsibilities

You will explore the Agile Scrum project life-cycle, including how an Agile User Story is created, to how we know when it is ‘done’

This course is aimed at those with or without prior knowledge and experience of the Agile values and principles

During this course you will learn the tools needed to succeed as an Agile Scrum Tester

What will you learn?

You will gain an in-depth understanding of the Agile Scrum Tester roles and responsibilities, and you will be able to

  • Fully understand the role of the Agile Scrum Tester
  • Understand the roles involved in an Agile project
  • Create an effective Product Backlog
  • Effectively participate in Scrum Meetings such as the Daily Stand-up, Sprint Review and Retrospective
  • Identify the roles involves in the Scrum Team
  • Fully understand the role of the Agile Scrum Developer
  • Understand the roles involved in an Agile project
  • Create an effective Product Backlog
  • Effectively participate in Scrum Meetings such as the Daily Stand-up, Sprint Review and Retrospective
  • Identify the roles involves in the Scrum Team

What topics are covered within this course

You will cover the following topics during this course:

  1. An Introduction to Agile Project Management (Tester)
  2. The 12 Agile Principles (Tester)
  3. Introduction to Scrum (Tester)
  4. Scrum Projects (Tester)
  5. Scrum Project Roles (Tester)
  6. Quality in Agile (Tester)
  7. Acceptance Criteria and the Prioritised Product Backlog (Tester)
  8. Quality Management in Scrum (Tester)
  9. Epics and Personas (Tester)
  10. Planning in Scrum (Tester)
  11. Scrum Boards (Tester)
  12. User Stories (Tester)
  13. The Daily Scrum (Tester)
  14. The Product Backlog (Tester)
  15. Review and Retrospective (Tester)
  16. Validating a Sprint (Tester)

Our Book Recommendations

We found these books great for finding out more information on Agile Scrum:

Translate »