Roles

Product Owner - He only cares about money. Every Scrum project must have a Product Owner. He knows everything about the system that is being developed and if he doesnt, he know who does. Another great responsability of the Product Owner is to keep the Product Backlog always up to date and priorized. He also will provide direction's for development team to follow so the project can generate the best possible ROI for it's stakeholders and users. This role will use this system mainly for:
  • Define the features of the product
  • Decide on release date and content
  • Be responsible for the profitability of the product (ROI)
  • Prioritize features according to market value
  • Adjust features and priority every iteration, as needed 
  • Accept or reject work results


Scrum Master
  • Represents management to the project
  • Responsible for enacting Scrum values and practices
  • Removes impediments
  • Ensure that the team is fully functional and productive
  • Enable close cooperation across all roles and functions
  • Shield the team from external interferences


Team Member - Team members are the hard working class of a Scrum project. They are responsable for turn user stories into working software at the end of every sprint. This role will use this system mainly for:
  • Keep track of tasks they're working on
  • Watch sprint progress on Sprint Burndown graph
  • Typically 5-9 people
  • Cross-functional:
  • Programmers, testers, user experience designers, etc.
  • Members should be full-time
  • May be exceptions (e.g., database administrator)
  • Teams are self-organizing
  • Ideally, no titles but rarely a possibility
  • Membership should change only between sprints

Last edited Jul 29, 2010 at 2:14 PM by mr0zek, version 5

Comments

No comments yet.