Development Team

The Development Team is made up of the professionals who do the work of delivering the Product Increment. They self-organize to accomplish the work. Development Team members are expected to be available to the project full time.

Traditional software development approaches define various job types, such as architect, programmer, tester, database administrator, UI designer, and so on. Scrum defines the role of Development Team, which is simply a cross-functional collection of these types of people. The Development Team’s members, collectively, have the skills required to deliver the business value requested by the Product Owner. Whenever you can, you should create cross-functional teams. Parcelling the work out to different role-specific teams is suspect and is likely a serious impediment to the successful use of Scrum.

At the beginning of each Sprint, the Development Team participates in Sprint Planning. In collaboration with the Product Owner and with facilitation from the Scrum Master, the Development Team helps to establish the goal for the next sprint.

Read More »

Product Owner

The Product Owner is the empowered central point of product leadership. It is one of the three collaborating roles that constitute every Scrum Team (the others being the Scrum Master and the Development Team).

The Product Owner needs to look in at least two directions simultaneously. On one hand, the Product Owner must understand the needs and priorities of the organizational stakeholders, the customers, and the users well enough to act as their voice. In this respect the Product Owner acts as a product manager, ensuring that the right solution is developed. On the other hand, the product owner must communicate to the Development Team what to build and the order in which to build it. The product owner must also ensure that the criteria for accepting features are specified and the tests that verify those criteria are later run to determine whether the features are complete. The product owner doesn’t write detail-level tests but ensures that the high-level ones are written so that the team can determine when the product owner will consider the feature complete. In these respects the product owner is part business analyst and part tester.

productowner

Read More »

Scrum Master

The Scrum Master is one of the three roles that constitute every Scrum Team (the others being the Product Owner and the Development Team). While the Product Owner is focused on building the right product and the Development Team is focused on building the product right, the Scrum Master is focused on helping everyone understand and embrace the Scrum Values, principles, and practices. The Scrum Master acts as a coach to both the Development Team and the Product Owner. A Scrum Master also provides process leadership, helping the Scrum Team and the rest of the organization develop their own high-performance, organization-specific Scrum approach.

The Scrum Master is a servant leader, helping the rest of the Scrum Team follow their process. The Scrum Master must have a good understanding of the Scrum framework and the ability to train others in its subtleties.

The Scrum Master works with the Product Owner to help the Product Owner understand how to create and maintain the Product Backlog. He works with the Development Team to find and implement the technical practices that will allow them to get the job done at the end of each Sprint. He works with the whole Scrum Team to evolve the Definition of Done. The Scrum Master continuously helps the Scrum Team improve the process, whenever possible, to maximize delivered business value.

Read More »