Agile is a collaborative approach to building custom software. Not only is collaboration important to the development team (with approaches like swarming and paired programming), it is also critical across all groups involved in the development process.
In this post, we identify each role and the tasks performed in the agile software development process.
Product Owner
The product owner controls the direction of the product. She/he is the main decision maker and has the final say regarding what features are implemented and when they are completed. Their main responsibilities include:
- Create and evolve the product vision
- Help create, prioritize, and provide detail as needed for user stories and specific functionality
- Have in-depth knowledge of the product
- Balance input from stakeholders
- Make business decisions as presented by members of the team
Scrum Master
The Scrum Master is the project manager in an Agile process. "Scrum" is a common method used to implement the principles of Agile development. It describes the approach and interaction of a tightly connected cross-functional team. The Scrum Master coordinates communication between the development team, product owner, and other stakeholders. Their main responsibilities include:
- Remove any blockers that the team may have
- Monitor, control, and report all activities within the process
- Navigate within the context of company culture
- Be a process expert...guide people within the process but also step out of process when deemed necessary
Team Members
The team members are the developers and designers who will be working on the project. Their role is to:
- Be experts in task decomposition
- Be technically competent
- Accurately translate product vision into functional software
Stakeholders
Stakeholders are those who have an interest in the product, but are not involved in the day-to-day process. They typically help evolve the product road map and vision with the product owner, providing product expertise or market insight. Their main roles are:
- Answering technical or other product related questions
- Communicate release points
- Articulate product drivers to the product owner
Users
Users' involvement can make or break a project. Users help answer the most important question: Are we building the right product? Their main roles are:
- Provide feedback to sprint reviews and/or demos
- Provide feedback to specific questions administered by the product owner
Defining and fulfilling roles are a key part of the Agile process. If you would like to learn more about how each role plays a part in the Agile software development process, download our free Ebook.
