The Agile Product Owner [PDF]

Scrum in 100 Words. •Scrum is an agile process that allows us to focus on delivering the highest business value in the

42 downloads 34 Views 2MB Size

Recommend Stories


The Agile Product Owner
Suffering is a gift. In it is hidden mercy. Rumi

Agile Journey Index Product Owner Extensions
Your task is not to seek for love, but merely to seek and find all the barriers within yourself that

Product Owner
No matter how you feel: Get Up, Dress Up, Show Up, and Never Give Up! Anonymous

Product Owner Job Description
We must be willing to let go of the life we have planned, so as to have the life that is waiting for

Les outils du Product Owner
In the end only three things matter: how much you loved, how gently you lived, and how gracefully you

Agile Product Management at Planon
If your life's work can be accomplished in your lifetime, you're not thinking big enough. Wes Jacks

Making Agile Product Roadmaps Work
Raise your words, not voice. It is rain that grows flowers, not thunder. Rumi

[PDF] Agile Project Management
Everything in the universe is within you. Ask all from yourself. Rumi

[PDF] Agile Project Management
If you want to become full, let yourself be empty. Lao Tzu

PdF Download Agile Testing
Your task is not to seek for love, but merely to seek and find all the barriers within yourself that

Idea Transcript


The Agile Product Owner Unifying the Three Sides of the Talent Triangle

Dave

Todaro @dave_todaro

President & COO Ascendle

Strategy

Commercial Software Development

Building

Coaching

Connect the business and the development team

Product Owner

Act as the product visionary

Drive business goals Image: danielguenther (Flickr)

Scrum in 100 Words • Scrum is an agile process that allows us to focus on

delivering the highest business value in the shortest time. • It allows us to rapidly and repeatedly inspect actual working software (every two weeks to one month). • The business sets the priorities. Teams self-organize to determine the best way to deliver the highest priority features. • Every two weeks to a month anyone can see real working software and decide to release it as is or continue to enhance it for another sprint.

24 hours

Sprint 2-4 weeks

Sprint goal

Return Cancel Return Coupons Gift wrap Gift Cancel wrap Product backlog

Sprint backlog Coupons

Potentially shippable product increment

Roles

•Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts

•Product backlog •Sprint backlog •Burndown charts

Scrum framework Roles

•Product owner •ScrumMaster •Team Ceremonies •Sprint planning •Sprint review •Sprint retrospective •Daily scrum meeting Artifacts

•Product backlog •Sprint backlog •Burndown charts

The Product Owner Role • Defines the features of the product • Prioritizes features according to business value • Adjusts features and priorities every sprint, as needed • Accepts or reject work results • Decides when to release and what’s included • Responsible for the profitability of the product (ROI)

“Customer Proxy”

The ScrumMaster • Provides management of the process

• Responsible for enacting Scrum values and practices • Removes impediments

• Ensures that the team is fully functional and productive • Enables close cooperation across all roles and functions • Shields the team from external interferences

The Team • Typically 5-9 people

• Cross-functional: Programmers, testers, user experience, designers, etc. • Members should be full-time • May be exceptions (e.g., database administrator): “external team members”

The Team • Teams are self-organizing • Ideally no titles, but rarely a possibility

• Membership should change only between sprints

• •

Self-organizing Size: 7 +/- 2

Product Owner

QA Engineer

ScrumMaster

Software Engineer

UX Architect

Software Engineer

Visual Designer

Technical Lead/Architect

• Form bridge between the business and the team • Work closely with software architect/technical lead to form the technical vision • Ensure the technical vision supports business goals • Use the product: try out new features every day or two and provide feedback to the team

• Act as figurehead for the team: “lead singer” • Go-to resource for the team • Vision holder for the product • Test everything to make sure it matches the vision

• Manage the product backlog • Solicit input from stakeholders • Demonstrate the product every sprint – typically every 2 weeks • • • •

Status report to stakeholders Get feedback Incorporate it into the product backlog Discuss priorities

ScrumMaster

Tech Lead

CEO

VP Sales

VP Customer Service

Engineer

Product Owner

Engineer

QA

From Our Blog 7 Simple Secrets to Building High Performance Teams With Scrum 6 Secrets for Creating an Agile Development Team in 2 Weeks or Less

Mike Cohn Mountain Goat Software, LLC

THANK YOU! Dave Todaro @dave_todaro

Ascendle.com

Ascendle.com/Blog

Smile Life

When life gives you a hundred reasons to cry, show life that you have a thousand reasons to smile

Get in touch

© Copyright 2015 - 2024 PDFFOX.COM - All rights reserved.