Roles in Agile Teams
PAGE 1
iOS Application Development
Roles in Agile Teams
MOBILE MAKERS ACADEMY 223 W Erie, Suite 4NW, Chicago, IL 60654 www.mobilemakers.co
© 2016 Mobile Makers Academy, LLC
PAGE 2
LEARNING OUTCOMES ● Explain how each role functions in an Agile development team
VOCABULARY ● Product Owner ● Scrum Master ● Team Members
MOBILE MAKERS ACADEMY 223 W Erie, Suite 4NW, Chicago, IL 60654 www.mobilemakers.co
© 2016 Mobile Makers Academy, LLC
PAGE 3
The Scrum process relies on the individuals that make up the team and how they interact with each other. Remember the first point in the Agile Manifesto? “Individuals and interactions over processes and tools.” A Scrum team will work together to define what needs to be done, what they can commit to completing, and how they will complete it. They trust each other to complete their own work and communicate frequently throughout the day to help each other when needed. Teams also figure out what is in their way and they take responsibility for resolving any blockers. There are only three roles: 1. Product Owner 2. ScrumMaster 3. Team member The Product Owner is responsible for creating and maintaining the vision of the product. They work with stakeholders or clients to define what the product should do, how it should work, and how it should look. This role is unique because he or she is typically closest to the “business” side of things and defines what needs to be completed and by when. The Product Owner is also responsible for creating and managing the Product Backlog—a list of all the functions needed for the application—and ensuring the team understands the priority of what tasks need to be completed first. Although it sounds like a lot, the Product Owner is definitely not responsible for everything. The team still determines how much they can get done each sprint, what questions to ask, and the specifics of how something should be built. This role doesn’t need to be able to do the job of a developer or designer, but they do need to know how to easily communicate with them. The Scrum Master is responsible for facilitating the Scrum process. They make sure the team is performing the Scrum activities appropriately and they help to ensure self-organization among the team. Most importantly, however, is that the Scrum Master removes obstacles that get in the team’s way. So if team members run into issues during a sprint , the Scrum Master is the one who is responsible for helping eliminate those issues. The Team Members are cross-functional developers, designers, and testers. They use their expertise to deliver completed User Stories based on their discipline. For example, a designer may create the designs to complete a specific User Story, the iOS
MOBILE MAKERS ACADEMY 223 W Erie, Suite 4NW, Chicago, IL 60654 www.mobilemakers.co
© 2016 Mobile Makers Academy, LLC
PAGE 4 developer may write the code for the specific User Story, and the tester may test the completed work to ensure the User Story is complete. It’s important to note that the Team Members self-organize to complete the work. This means they will determine how many User Stories they can commit to for a sprint and they are responsible for making sure their User Stories are complete before the end of that sprint, meaning that the story is built and tested before showing it to the client.
MOBILE MAKERS ACADEMY 223 W Erie, Suite 4NW, Chicago, IL 60654 www.mobilemakers.co
© 2016 Mobile Makers Academy, LLC
PAGE 5
MOBILE MAKERS ACADEMY 223 W Erie, Suite 4NW, Chicago, IL 60654 www.mobilemakers.co
© 2016 Mobile Makers Academy, LLC
iOS Application Development
Roles in Agile Teams
MOBILE MAKERS ACADEMY 223 W Erie, Suite 4NW, Chicago, IL 60654 www.mobilemakers.co
© 2016 Mobile Makers Academy, LLC
PAGE 2
LEARNING OUTCOMES ● Explain how each role functions in an Agile development team
VOCABULARY ● Product Owner ● Scrum Master ● Team Members
MOBILE MAKERS ACADEMY 223 W Erie, Suite 4NW, Chicago, IL 60654 www.mobilemakers.co
© 2016 Mobile Makers Academy, LLC
PAGE 3
The Scrum process relies on the individuals that make up the team and how they interact with each other. Remember the first point in the Agile Manifesto? “Individuals and interactions over processes and tools.” A Scrum team will work together to define what needs to be done, what they can commit to completing, and how they will complete it. They trust each other to complete their own work and communicate frequently throughout the day to help each other when needed. Teams also figure out what is in their way and they take responsibility for resolving any blockers. There are only three roles: 1. Product Owner 2. ScrumMaster 3. Team member The Product Owner is responsible for creating and maintaining the vision of the product. They work with stakeholders or clients to define what the product should do, how it should work, and how it should look. This role is unique because he or she is typically closest to the “business” side of things and defines what needs to be completed and by when. The Product Owner is also responsible for creating and managing the Product Backlog—a list of all the functions needed for the application—and ensuring the team understands the priority of what tasks need to be completed first. Although it sounds like a lot, the Product Owner is definitely not responsible for everything. The team still determines how much they can get done each sprint, what questions to ask, and the specifics of how something should be built. This role doesn’t need to be able to do the job of a developer or designer, but they do need to know how to easily communicate with them. The Scrum Master is responsible for facilitating the Scrum process. They make sure the team is performing the Scrum activities appropriately and they help to ensure self-organization among the team. Most importantly, however, is that the Scrum Master removes obstacles that get in the team’s way. So if team members run into issues during a sprint , the Scrum Master is the one who is responsible for helping eliminate those issues. The Team Members are cross-functional developers, designers, and testers. They use their expertise to deliver completed User Stories based on their discipline. For example, a designer may create the designs to complete a specific User Story, the iOS
MOBILE MAKERS ACADEMY 223 W Erie, Suite 4NW, Chicago, IL 60654 www.mobilemakers.co
© 2016 Mobile Makers Academy, LLC
PAGE 4 developer may write the code for the specific User Story, and the tester may test the completed work to ensure the User Story is complete. It’s important to note that the Team Members self-organize to complete the work. This means they will determine how many User Stories they can commit to for a sprint and they are responsible for making sure their User Stories are complete before the end of that sprint, meaning that the story is built and tested before showing it to the client.
MOBILE MAKERS ACADEMY 223 W Erie, Suite 4NW, Chicago, IL 60654 www.mobilemakers.co
© 2016 Mobile Makers Academy, LLC
PAGE 5
MOBILE MAKERS ACADEMY 223 W Erie, Suite 4NW, Chicago, IL 60654 www.mobilemakers.co
© 2016 Mobile Makers Academy, LLC
