Loading presentation...

Present Remotely

Send the link below via email or IM

Copy

Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.

DeleteCancel

Make your likes visible on Facebook?

Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.

No, thanks

Scrum Roles

No description
by

Laura Langer

on 14 September 2012

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Scrum Roles

are you committed or involved? Scrum Roles Productor Owner The Product Owner is the one person responsible for a project’s success. The Product Owner leads the development effort by conveying his or her vision to the team, outlining work in the scrum backlog, and prioritizing it based on business value. who is the product owner???? decides what will be built and in which order Responsibilities... Defines the features of the product Chooses release date Ensures profitability (ROI) Prioritizes features/outcomes Adjusts features/outcomes and priority Accepts or rejects work results Facilitates scrum planning ceremony Visionary and Doer
Leader and Team Player
Communicator and Negotiator
Empowered and Committed
Available and Qualified
Nobody is Perfect Desirable Characteristics Common Ways to Apply the Product Owner Role The Customer Plays the Product Owner Role One way to apply the product owner role is to ask the customer to play the role. This option is particularly useful for the development of bespoke (custom) software. For instance, if a web application is developed for a company’s marketing group – either by an in-house team or by an external software provider – a member of the marketing group should take on the product owner role. The Customer Plays the Product Owner Role One way to apply the product owner role is to ask the customer to play the role. This option is particularly useful for the development of bespoke (custom) software. For instance, if a web application is developed for a company’s marketing group – either by an in-house team or by an external software provider – a member of the marketing group should take on the product owner role. Advantages: The customer steers and controls the development of the software directly. This allows the customer to own the product, speeds up decision-making, and increases the likelihood of creating a product that serves the customer needs.

Challenges: The customer must be available, qualified, and empowered to create a successful product. The customer and the team must value transparency and develop a healthy, trustful relationship. The latter tends to be particularly challenging when the customer and the team have different interests, for instance, getting the essential features shipped as soon as possible vs. maximising revenue, or if they have had difficulties to collaborate in the past (“IT never delivers”). Advantages / Challenges We can decide to separate the customer and the product owner role. This option is applicable when software is developed for several customers:
A Customer Proxy Fills the Product Owner Role Advantages: Separating the customer and the product owner role helps create a product that addresses all the needs selected. It also provides the opportunity to employ professional full-time product owners with the right skills: Product managers, project managers, and business analysts can focus on playing the role effectively.

Challenges: Empowerment of the product owner can be difficult to achieve: Product owners often require the trust and support of senior management to be able to make the necessary decisions, to have the clout to say no, and to create stakeholder alignment. Companies that regard IT largely as a commodity can find it difficult to value product ownership and to invest in developing product owners. Advantages / Challenges Business analysts play an important role: They usually act as the link between the business units and IT, helping to discover the user needs and the solution to address them. In Scrum, there is no business analyst role. So what happens to the business analysts? Business Analysts in SCRUM One option for a business analyst is to take on the product owner role, as the following picture shows: Option 1: Business Analyst Plays the Product Owner Role The second option for business analysts is to work as team members. This is option is depicted by the following picture: Option 2: Business Analyst Works as a Team Member A common mistake is to deal with the role of business analysts in Scrum half-heartedly: Business analysts are neither play the product owner role nor are they team members. They rather end up as proxy product owners, a go-between the real decision maker and the development team: Avoid the Proxy Product Owner Trap Activity!!!!! On each project, Identify the business analyst and its role... The Underpowered Product Owner
The Overworked Product Owner
The Partial Product Owner
The Distant Product Owner
The Proxy Product Owner
The Product Owner Committee Avoiding Common Product Owner Mistakes Scrum Master The ScrumMaster protects the team. who is the Scrum Master???? 1 - Be a team player
2 - Remove impediments
3 - Radiate information
4 - Support the Product Owner
5 - Facilitate creativity and empowerment for the development team
6 - Runs The Daily meetings Responsibilities are you pig or chicken??
The Pigs are person committed with the project and with the Scrum Process. "Pig" Role Product Owner
ScrumMaster
Team "chicken" Role The chiken role isn´t part of Scrum Process but you must them in mind. Users
Stakeholders
Managers Scrum Team Characteristics cross-functional
Intensely collaborative
Self-organising
Committed to delivering their Sprint Goals
Trusting of one another
Make decisions as a Team
Constructive in their criticism of themselves and eachother
Creative and innovative
Responsible and accountable
Reliable
Business-value oriented Question the Product Manager/Product Owner to ensure they fully understand the requirements of the Product Owner and end-user Responsibilities The Scrum Team builds the product that the customer is going to consume.

A typical Scrum team is 7 +- 2 people

Members should be full-time

Members should change only between sprints who is the Scrum Team???? software engineer
architects
programmers
analysts
QA experts
UI designers typical team includes a mix of... "we're all in this together." Presenters
Laura Langer
Gabriel Gotelli warning!!!!!! questions???? Activity!!!!!!!!!!!!! Why do you think it is not a good idea to have a Proxy Product Owner? Avoid the Proxy Product Owner Trap Increase in miscommunication
A slowdown in decision making
A decrease in productivity and morale. The ScrumMaster serves as a facilitator for both the PO and the team. The ScrumMaster is responsible for making sure a Scrum team lives by the values and practices of Scrum. The ScrumMaster is not the team leader Transform Sprint Backlog tasks in a functional increment Quality development DEVELOPER
Full transcript