In this short video we'll talk about the Agile Product Owner role and discuss some key expectations of this very important role! Please share your feedback/comments on our AgileVideos.com site and watch the rest of the series! Thanks for watching :) Sally
Views: 56119 Agile Training Videos
This is basically a 1 day product ownership course compressed into 15 minute animated presentation. There's obviously more to product ownership than this, so see this is a high level summary. For translated versions & translation guide, see http://blog.crisp.se/2012/10/25/henrikkniberg/agile-product-ownership-in-a-nutshell Special thanks to Alistair Cockburn, Tom & Mary Poppendieck, Jeff Patton, Ron Jeffries, Jeff Sutherland, and Michael Dubakov for providing many of the models, metaphors, and ideas that I use in this presentation. Download the complete drawing here: https://www.dropbox.com/s/ph3spbc3evgoh3m/PO-in-a-nutshell.png Downloadable version of the video here: https://www.dropbox.com/s/h3fzydsss7sgqjd/PO-in-a-nutshell.mov PS: The intro & outtro song is just me jamming in my home studio. I bought a cool half-acoustic guitar a few months ago and was looking for an excuse to make use of it :o) Tools used: Artrage (drawing program), Wacom Intuos 5 (drawing tablet), Screenflow (screen & audio capture).
Views: 1883039 Henrik Kniberg
Subscribe to our YouTube channel to stay up to date on all of our world-class products and exciting updates: https://goo.gl/YhZF9h Agile Product Owners have a deep understanding of how products are used and the value they bring to both customers and the business. CA can help provide a deeper understanding of this essential role.
Views: 18610 CA Technologies
We've all been there before. We work with a Product Owner (or we are the Product Owner ourselves!) that is still on their Agile Journey. How do we help them? In this video we list some of the anti-patterns that Product Owners go through in their journey and we give you concrete, actionable ways to help those Product Owners be Awesome! To get the next 2 videos go here: (LINK MISSING)
Views: 719 Oikosofy
http://tv.ssw.com/what-is-a-product-owner The 2013 Scrum Guide definition of the 'Product Owner', in video form! http://rules.ssw.com.au/Management/RulesToBetterProductOwners/Pages/default.aspx (from the 2013 Scrum Guide:) The Product Owner The Product Owner is responsible for maximizing the value of the product and the work of the Development Team. How this is done may vary widely across organizations, Scrum Teams, and individuals. The Product Owner is the sole person responsible for managing the Product Backlog. Product Backlog management includes: Clearly expressing Product Backlog items; Ordering the items in the Product Backlog to best achieve goals and missions; Ensuring the value of the work the Development Team performs; Ensuring that the Product Backlog is visible, transparent, and clear to all, and shows what the Scrum Team will work on next; and, Ensuring the Development Team understands items in the Product Backlog to the level needed. The Product Owner may do the above work, or have the Development Team do it. However, the Product Owner remains accountable. The Product Owner is one person, not a committee. The Product Owner may represent the desires of a committee in the Product Backlog, but those wanting to change a backlog item's priority must convince the Product Owner. For the Product Owner to succeed, the entire organization must respect his or her decisions. The Product Owner's decisions are visible in the content and ordering of the Product Backlog. No one is allowed to tell the Development Team to work from a different set of requirements, and the Development Team isn't allowed to act on what anyone else says.
Views: 66551 SSW TV | Videos for developers, by developers
Who should attend? Professionals interested in Agile certification, Certified Scrum Master certification, SEO's for already certified professionals. Contact us today - Call- 1-877-648-0004 Email - [email protected] www.agilestrategicsolutions.com
Views: 33 DrSam Swapn
Presentation name: Challenges of product owner in a new agile team Speaker: Jan Zeleny Description: Product Owners are key in any agile teams that are being formed. They are communication hubs between their teams and all of their teams' stakeholders. They are also important advisors of the team. It is these people that often take the first hit when something does not work ideally ... which happens a lot in new projects. In this session we will take a look into the life of product owners as their projects take off, what hits they take and how do they deal with them. At the end of the session, the product owners in the audience will have some tips how to make their own lives easier. They will also know that they are not alone. The rest of the audience will have a better understanding of challenges the product owners face which will help them understand how to communicate more effectively. [ https://sched.co/JciK ]
Views: 39 DevConf
As part of the Scrum Tapas video series, Professional Scrum Trainer, Charles Bradley discusses ways that a Product Owner can spread their knowledge across multiple Scrum Teams. He looks at a few techniques and refinement activities.
Views: 4357 Scrum.org
In this video I answer whether a Product Owner can be a Scrum Master of a team, and whether this is good practice or not! My name is Anatoly Spektor and I have spent more than 10 years in Software Development world, and currently I help people with Agile Project Management. If you have any other questions about Agile that you'd like answered, don't be afraid to ask them on LinkedIn, Twitter, Quora, and of course in the comment section (all social media links further down)! If you need professional help to move your teams to Agile, go to http://www.defineagile.com and book your FREE first consultation with me! Twitter: https://twitter.com/defineagile LinkedIn: https://www.linkedin.com/in/anatolyspektor Website: http://www.defineagile.com
Views: 60 Define Agile
https://www.udemy.com/scrum-made-easy-the-agile-scrum-framework/ Introduction to the three key roles in a team delivering a product using the Agile/Scrum framework Now that you have a good idea of the what the scrum framework looks like, in this section I will discuss the make up of a typical scrum team. In most literature on the subject these are called the scrum roles And the roles in a scrum team are Product Owner, a Scrum Master and the Development Team. The Product Owner manages the product The Scrum Master manages the processes And the Development team? Well they manage themselves. The individuals in these roles work closely together to make sure the flow of information is smooth and the resolution of issues is quick. And that’s just what ’s needed to deliver a quality product in the shortest possible time. So let’s get into the three critical roles that make a scrum team tick… https://www.udemy.com/scrum-made-easy-the-agile-scrum-framework/
Views: 200 Jeb Riordan
Scrum Master vs Project Manager vs Product Owner. Is this confrontation a myth? Or do you really believe these roles cannot coexist in one project? Watch this video to learn more about roles and responsibilities of a Project Manager, Scrum Master, and Product Owner. Also, you can learn about different project management approaches that can mix these roles efficiently. If you want to become a software project manager get my guide: "How to Become a Software Project Manager": https://pmbasics101.com/become-software-development-pm/
Views: 6890 Project Management Basics
We've disrupted the role of Agile Managers in a big way, without giving them a clear path for their new role. Managers are used to wearing multiple hats such as: Subject matter expert, product owner, task manager, fire fighter, coach and mentor. Now, with Agile, several of these are covered by other roles and some of them might even go away. So what do we really want managers to focus on? How can they add value and contribute to the team and organization's success but in a new way? Watch this video with an open mind and be prepared to learn some new ideas around the role of Agile managers!
Views: 2807 Agile Training Videos
Why do we need a Scrum Product Owner and what are the roles a Product Owner plays in an Agile team? This video will help you find the answers to both these questions. For your Agile project to succeed, not only do you need strong commitment and involvement from the business, you need a good Product Owner. Product owners are an integral part of most Agile teams. Watch our video on Career Path of a Scrum Product Owner here: https://www.youtube.com/watch?v=4DxPMPsw8dc To know the difference between a Scrum Master and a Product Owner watch our video here: https://www.youtube.com/watch?v=CZnWiVhpdzQ&list=PLsikuZM13-0ws48Gf03elrQZlaj7CSZ0f&index=8 To know more about Scrum Framework watch our Scrum Tutorial playlist here: https://www.youtube.com/playlist?list=PLsikuZM13-0xY4fBrYbI5TaqVQhaAJqAn To know more about our Certified Scrum Product owner Certification Training visit: https://www.knowledgehut.com/agile-management/cspo-certification-training For more informative videos, Subscribe to KnowledgeHut- https://www.youtube.com/user/TheKnowledgehut?sub_confirmation=1 #ScrumProductOwner #Knowledgehut
Views: 184 KnowledgeHut
http://www.slideshare.net/lasse.ziegler/the-good-product-owner Lasse Ziegler is an agile coach and trainer with many years of experience working with different scrum teams in a variety of organizations both small and large. In the last 12 years Lasse has been a developer, architect, project manager, CTO and entrepreneur. Having been in different roles gives a coach good overview of different aspects of an organization as well as an understanding of their different needs. With this experience a coach is well equipped in delivering a end-to-end coaching experience where both the business as well as the development are engaged. The Good Product Owner - A path to become great A good product owner is probably the most important role in any Scrum project but for some reason they are exceedingly rare. Without one the development team is without direction and lost in a vast ocean of possibilities. Why is it that being a good product owner is difficult? What is expected and how do you become a good product owner. In this session we will cover a number of common product owner anti-patterns to learn from. In addition we will describe some good practices and provide you with some tools to be more effective and help you become the good product owner that you always dreamed about.
Views: 23018 Agile Lietuva
43. In Praise of the (Agile) Product Owner // Who has the toughest time "Being Agile"? Is it the Dev Team? Is it the Lead Developer? What about the Business Owner? Or is it... the Product Owner? → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe Arguably, it's the Product Owner that has the toughest job "being Agile". Building software in small, iterative cycles is easy to "sell" to a development team. But it takes nerves of steel on behalf of the Product Owner to trust that product features will build over time. Music: 260809 Funky Nurykabe: ccmixter.org/files/jlbrock44/29186 You've seen these guys before. Question. Who has the toughest time being Agile Is it the Dev Team Maybe The Lead Developer Possibly. The Business Owner Could be. Or is it... (and I think it might be...) The Product Owner. Boxes and Walls ---- Hi this is Gary Welcome to 'Development That Pays'. I wanted to turn the spotlight on the Product Owner. But I could't decide what to talk about Then Vlad came to my rescue with this great comment that gets right to the heart of one of the hardest aspects of being a Product Owner. "Problem now is that some of them do not upgrade, and continue to use the “boxes” to climb the wall…" Clearly, that's going to need some context. A recurring theme here on Development That Pays are the twin concepts of do the right thing, and do the thing right Way back in Episode 2, i used the metaphor of two walls Each wall is a potential business opportunity. And each ladder represent is a product. What more important: building a great ladder or, picking the right wall Well, any old ladder will get you up the wall But... the walls lead to very different places. So we can say that: Picking the right wall is more important than building a great ladder. Doing the right thing is more important that Doing the thing right. HOWEVER... There's a fatal flaw in the argument And that's what we went on to talk about in Episode 3 From this point, both of the walls look the same. From this point you can't see what's on the other side So you've no choice but to climb up there and take a look. It's Catch 22. You need to pick the right wall... But you can't pick the right wall until you've climbed the wall which you can't do without... picking a wall! One thing is for sure: If we’re going to have to climb a wall that may turn out to be the wrong wall Then this is no time for Do The Thing Right. No, this is the time to get there quickly and cheaply Certainly not an escalator Nor a staircase. A ladder would be a good choice Or even - dare I say it - a pile of boxes. Getting Stuck with the Boxes ----- We now have the context we need for Vlad's comment. Vlad's concern is that we get stuck with the pile of boxes ... even after we've found the perfect wall. Come with me now to a meeting. The meeting was called by the Product Owner She has an an idea for a new product. She's invited the entire dev team. to come and discuss a new product idea. She walks up to the whiteboard and draws something that looks a lot like an escalator A discussion follows. The dev team is clearly concerned about the scale of the task At a certain point, the lead dev walks up to the whiteboard and says What about if we start by building this... ... then we can come back and build this ... then this ... then this From there it should be easy to build what you've asked for. Quick aside ---- At this point, I'd like you to take a moment and notice how you feel about this plan of action. Are you comfortable with it Do you have concerns Back to the Meeting ---- My guess is that these guys [the developers] like the idea For them, it's an easy sell: This thing [the escalator] looks like a nightmare to code. This thing [the pile of boxes] looks straightforward. Could be live by the end of the week. Bish bash bosh. What about the Product owner How does it look from her point of view The picture isn't nearly as rosy. First of all, there's a big different between what she asked for and what she's going to get - at least in the short term Then there's the "challenge" that version two is CONDITIONAL on the success of version one (And version one looks so ropey that it's hard to see it being a success!) And if the first version is a success, what then How long will it be before it can be built The Dev team have spare capacity now... but will they have spare capacity a month from now Hard to say. And we haven't even talked about stakeholders. If the Product Owner agrees to this course of action, her next job - when she leaves the meeting - will be to 'sell' the approach to various internal stakeholders. None of which https://www.youtube.com/watch?v=D0Ax7eJuNX8 https://www.youtube.com/watch?v=502ILHjX9EE
Views: 8150 Development That Pays
TABLE OF CONTENTS: How Is The Product Owner Role Supposed To Work? How Does Your Large Organization Misinterpret The Product Owner Role? How Does Misinterpreting The Product Owner Role Delay Customer Feedback? How Does Misinterpreting The Product Owner Role Reduce Developer Motivation and Empathy For Customers? How Do Real Product Owners Deliver The Highest Customer Value? How Does Misinterpreting The Product Owner Role Reduce Value Delivery? What Is Unpleasant About Trying To Fulfill The Misinterpreted Product Owner Role? How Can We Help The People Stuck In This Role While increasing team self organization and cross functionality? Is It Necessary To Create New PO-derived Roles Like Chief Product Owner, Business Owner, etc.? This video corrects some errors in my friend Henrik Kniberg's otherwise excellent "Product Owner In A Nutshell" video.
Views: 10726 Michael James
A Product Owner is someone who is responsible for creatively solving users problem and strategically maximizing the value for the business. A product owner is responsible for everything related to the product including: - User Research - Market Research - Business Model Design and - Product Development. While PO owns everything, they may or may not do everything. At times, they may take help of the development team, a discovery team or anybody who can help. If you want to learn more about Product Ownership, join an online course on https://playscrum.com/ or join one of our Certified Scrum Product Owner (CSPO) courses at https://leanpitch.com/cspo-workshops/
Views: 2648 Play Scrum
Where does a business analyst fit in an agile world? Is the business analyst the Product Owner? Should they be the product owner? For more check out: http://www.metabusinessanalyst.com/the-agile-business-analyst-doesnt-exist/
Views: 16898 Angelo the BA
Scrum defines three roles, the Product Owner, Scrum Master and Development Team Member. But what happens if you have a different job title? It doesn’t mean that you are out of luck or out of a job, in most cases it means the exact opposite with your job expanding to deliver more value in the Scrum Team. So, where do you fit in Scrum? In this talk Dave West, CEO and Product Owner of Scrum.org talks about the roles of Scrum and how the three roles relate to your existing job titles. He describes the future of work in the context of an agile delivery model and what the implications are to job descriptions and career progression.
Views: 22659 Scrum.org
Dive deep into Scrum Framework and know about the roles and responsibilities of Scrum. Get to know the roles and responsibilities of Scrum Master. Know about the roles and responsibilities of Product owner and know about the roles and responsibilities of Scrum Team. Get CSM Certified from Knowledgehut here: https://www.knowledgehut.com/agile-management/csm-certification-training Get CSPO Certified from Knowledgehut here: https://www.knowledgehut.com/agile-management/cspo-certification-training
Views: 2207 KnowledgeHut
45. The Agile Product Owner Is Not The Problem // It's not unusual for Development Teams to consider the Product Owner to be the source of... issues. But in most cases, the real source of the problem lies elsewhere. → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe Some 18 months ago, I was trying to work out why a development team - my development team - was having such a hard time getting things done. It wasn't for a lack of talent. Nor was it for lack of teamwork: we worked well together. At the time, I blamed the Product Owner. He seemed to go out of his way to make life difficult for us. But the real source of the problem wasn't the Product Owner. The source of the problem was... an interface. All is revealed in the video. It's a little bit "out there"... but I hope you'll enjoy it. If you sit here (Development Team) Or here (Lead Developer) And things aren't running as smoothly as you would like. You may be thinking that the Product Owner is the source of your woes. Perhaps your Product Owner really is Evil. But it's more likely that your problem lies... Elsewhere. Reflections --- The mind works in strange ways. (As least, mine does) A few weeks ago, I was walking through the Inns of Court here in London. Headphones on, listening to a podcast. An actor was being interviewed. I don't remember his name. Might have been Albert Finley. Someone of that ilk. Whoever it was, he talking about a new role. I wasn't really paying attention. They were saying something about spectacles (glasses). How the choice of style was important in establishing the character And also, due to his advancing years to be able to see the other cast members clearly enough to be able to read their expressions. And then he said something that stopped me in my tracks: "I can't wear my own glasses, because of the reflections." Brainstorm ---- That line was enough to jolt my brain into action In a matter of seconds I got from Reflections all the way to Product Owners. As tenuous connections go, it's right up there ;) "Of Course!" --- My first thought was: "Of course reflections from actor's glasses would be a problem." I wondered why I'm never though of it before. Light ---- My second thought was a picture like this. (I should point out at this point that I'm a physics grad... so pictures like this are often in my brain!) This what happens whenever light encounters a boundary: a portion is reflected and - assuming the second material in translucent - a portion in transmitted. the proportion that is reflected is determined by the refractive indexes of the two materials. "Eureka!" ---- My third thought was "I know how to reduce the reflection". Imagine adding a layer of material with a refractive index roughly half way between that of air and glass. We've replaced a large step change with two smaller step changes. Although this adds an extra reflective surface, when all the calculations are done, more of the light gets through... and reflections are reduced. I know what you're thinking: why stop at one layer Why indeed! Turns out that you can get even more light through by applying a coating that continuously varies the refractive index. More light is transmitted. Less light it reflected. "Impedance Matching!" ---- My fourth thought and this one is particularly weird - was... Impedance Matching. (I told you there were some strange thoughts in my head.) Here's a electronic component It sends a signal to a second electronic component. at the boundary, a certain portion of the signal from the first component makes it to the second. That's a good thing. And a certain portion is reflected. That's a bad thing. The proportion that is reflected is determined by the DIFFERENCE in the RESISTANCES - more correctly the IMPEDANCES - of the two components. Sound familiar Yep, it's another discontinuity. Another step change. In this case, the solution is different to solution used for the glasses. The components are designed so that the OUTPUT resistance of the first component is as close as possible to the INPUT resistance of the second component. "What Else " -- My fifth thought was... I wondered what else is like this What other things where there is an interface - a discontinuity, a step change - where performance can to improved by: smoothing ... like the glasses or matching ... like the electronic components Scribble ---- My brain provided a perplexing response: this scribbled drawing. A drawing that I'd done MONTHS earlier. It wasn't as abstract as it looks: the sketch represented a real life team. A team ... of which I was a member. A team... that was struggling. There https://www.youtube.com/watch?v=0z5ExmD4fM0 https://www.youtube.com/watch?v=502ILHjX9EE
Views: 5845 Development That Pays
This is a snippet from 280 Group's Agile Certified Product Manager and Product Owner - Online Course and Exam Learn More About The Online Course: http://280.gr/2zrnRC5 To be totally clear, this is a discussion about roles and NOT titles. For example, your TITLE can be Product Manager while performing the ROLE of a Product Owner. Product Management is a big discipline that covers a vast range of activities and responsibilities. This means being the market expert. You own the product strategy which drives the vision and roadmap. You manage the product throughout its lifecycle. And you ensure that there is a business justification for your decisions. You present the need. Your focus is the problem space and you avoid defining the product. You make the tough decisions and tradeoffs between features, schedule and cost. Ultimately, you deliver differentiated products to market. In some companies, the role is so big, that different aspects of it are split between different people. On the flip side, this is how product ownership is defined. You maximize the value of the product and the work of the development team. And you are the sole person responsible for managing the product backlog. You need to make sure the backlog is visible and understood by the entire development team. And all of these tasks for a particular project or slice of a project are the responsibility of one person. When you map the roles side-by-side, you can see that the product owner is responsible for the detailed work. You can see how closely they work with the development team. There are a lot of tasks that overlap with product management responsibilities. To allocate these, you may need to adjust for individual strengths and weaknesses. Some tasks are outside the scope of what Agile defines as that of the Product Owner. Many organizations struggle with dividing their responsibilities and if someone has all of these assigned to them, the workload becomes overwhelming. As a result, the focus is on the urgent and strategic focus is greatly diminished or lost.
Views: 10792 280 Group
Many agile software development organizations have self managing teams when it comes to implementation of software, but still use a Product Owner role for product discovery, user and business value and story prioritization. At CCP Games, developers of award winning science fiction MMO EVE Online, the product owner role has been eliminated as a position held by individuals, and instead the responsibility of product ownership has been integrated into the development feature teams with good results. Hear how the change happened, how team based management is part of the puzzle, and what the results have been a year into this change for the EVE dev team. Foo Café is an independent and physical meeting place for people of all backgrounds and expertise within the IT-industry in the Malmö/Lund region. Foo Café is aimed at those interested in sharing, learning and creating. Join the fun at foocafe.org
Views: 1972 FooCafe
As part of the Scrum Tapas video series, Professional Scrum Trainer Steve Porter tells a story about his experience as a Product Owner and why his mistrust for the Scrum Team was a mistake and how the Product Owner should use the Sprint Backlog as a way of building that trust. Steve discusses the right ways to communicate with the Scrum Team and how the Product Owner is responsible for the "what" and the Scrum Team for the "how".
Views: 1456 Scrum.org
Agile practices rely on empiricism for the best solution to emerge. But what is ‘empiricism,’ anyway? And how does that affect the development of the optimum product? In this session, Professional Scrum Trainer Mark Noneman looks at what it takes to be a Product Owner who practices empiricism. He’ll explore the combination of empiricism and Product Ownership in agile development. How does empiricism affect the long-term role of the Product Owner? How should the Product Owner use empiricism to develop the best economic results? And how can an Empirical Product Owner explore their options using agile practices, in the first place? Join us for this thought-provoking discussion on the skills and behaviors of an Empirical Product Owner!
Views: 8492 Scrum.org
42. Agile Product Ownership in a Nutshell // Henrik Kniberg has created an extraordinary video that as close as you can get to the perfect primer on Agile Product Ownership. It covers a lot of ground, including: → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe - Vision - Stakeholders - User Stories - Capacity - Automated Testing / Continuous Integration - WIP Limits - Product Backlog - The importance saying "No" - Backlog Grooming - Risk - Customer Value / Knowledge Value - Estimating / Forecasting - Technical Debt - Multi-team projects Definitely worth 15 minutes of your time. Grab a hot beverage and prepare to be impressed: - Agile Product Ownership in a Nutshell: https://www.youtube.com/watch?v=502ILHjX9EE I think it's high time that we turned the spotlight on the Product Owner. If you Google for 'Product Ownership', the first result is a rather nice definition: The Product Owner (PO) is the member of the team responsible for defining Stories and prioritizing the Team Backlog so as to streamline the execution of program priorities, while maintaining conceptual and technical integrity of the Features or components the team is responsible for. I don't have a problem with any of that, other than it's a bit... dry. Scrolling down, there are some image results. (If you're a product owner yourself, I'm sure you'd approve of this one) But it's this one that I've brought you to see. You may recognise the style: it was drawn by Henrik Kniberg - the same guy that drew the Minimum Viable Product illustration that we featured in a previous episode. If a click through to the page, it's a video. And believe me when I tell you that it's no ordinary video: it's as close as I think you can get to a perfect primer on Product Ownership It covers a lot of ground, including: Vision... Stakeholders... User Stories Capacity Automated Testing / Continuous Integration WIP Limits Product Backlog The importance saying "No" Backlog Grooming Risk Customer Value / Knowledge Value Estimating / Forecasting Technical Debt and Multi-team Projects Definitely worth 15 minutes of your time. Do yourself a favour: grab a hot beverage and sit down and watch the video. If you like the video, make sure to give Henrik a thumbs up, then come back here and let me know your thoughts. That's it for this time. Join me next time for more Product Owner-related loveliness. https://www.youtube.com/watch?v=3qP27HEkHE8 https://www.youtube.com/watch?v=502ILHjX9EE
Views: 6033 Development That Pays
The Product Owner is one of the most critical roles in Scrum. Michael Goff, our Director of Agile Development explains their role in Agile software development. Learn more about the Product Owner's role in Michael's blog: https://www.smallfootprint.com/insights/how-technical-should-product-owners-be-in-agile-software-development
Views: 30 Small Footprint, Inc.
SCRUM ist die am weitesten verbreitete agile Methode im Projektmanagement. Weitere Informationen erhalten Sie unter: http://www.mitsm.de/scrum-master-product-owner DIE ROLLE DES PRODUCT OWNER Der Product Owner ist für das Produkt verantwortlich. Und damit auch für die Arbeit des Entwicklungsteams, mit dem er eng zusammenarbeitet. Der Product Owner ist immer eine einzelne Person und ist allein für das Product Backlog, also für den Anforderungskatalog rechenschaftspflichtig. Er kann aber gewisse Arbeiten wie die Pflege des Product Backlogs an das Entwicklungsteam übergeben. Außerdem tut gut daran, Einschätzungen und Empfehlungen des Entwicklungsteams schon frühzeitig zu berücksichtigen. Alle Entscheidungen müssen aus Gründen der Transparenz im Product Backlog dokumentiert sein. Auf das Sprint Backlog hat der Product Owner jedoch keinen direkten Einfluss. Das wird allein vom Entwicklungsteam geändert und aktualisiert. Indirekt kann er den Sprint Backlog natürlich mitgestalten, nämlich in der Sprint-Planungssitzung, bei dem die Ziele des nächsten Sprints festgelegt werden. Der Product Owner lädt das SCRUM Team und andere wichtige Stakeholder - also Interessensvertreter - zum Sprint Review ein. Der Product Owner ist als Einziger berechtigt, Einträge im Product Backlog auf 'done' - also erledigt - zu setzen. Das Product-Inkrement muss ein lauffähiges, bzw. einsatzfähiges Produkt sein, so dass der Product Owner es jederzeit veröffentlichen kann. Der Sprint beinhaltet also nicht nur die Entwicklung, sondern auch das ausführliche Testen. Selbstverständlich nimmt der Product Owner auch an der Sprint-Retrospektive teil. Hier hat er jedoch keine führende Rolle zu übernehmen. Er schlägt Verbesserungen vor und wird gegebenenfalls mit deren Durchsetzung beauftragt. Der Product Owner ist für das „optimale“ Produkt verantwortlich und repräsentiert in SCRUM den Kunden. Er bildet sozusagen die Brücke zwischen Kunde und Entwicklungsorganisation. Die Rolle "Kunde" ist übrigens im Original SCRUM Guide gar nicht explizit erwähnt und versteckt sich neben anderen Rollen hinter dem Begriff Stakeholder, also dem Interessensvertreter. Der Product Owner arbeitet eng mit dem Entwicklungsteam zusammen und bildet mit diesem und dem SCRUM Master das sogenannte SCRUM-Team. Um erfolgreich zu sein, muss die gesamte Organisation seine Entscheidungen, die im Product Backlog aus Gründen der Transparenz zu dokumentieren sind, respektieren. Eine der wichtigsten Regeln in der Zusammenarbeit zwischen Produkt Owner und Entwicklungsteam ist, dass nur er seinem Entwicklungsteam Aufgaben stellen darf. Die primäre Tätigkeit des Product Owners ist die Verwaltung des Product Backlogs. In ihm werden alle Anforderungen für Änderungen am Produkt aufgelistet. Das Product Backlog ist ein lebendiges Dokument, das niemals vollständig ist. Denn es entwickelt sich mit dem Produkt und dessen Einsatz dynamisch weiter. Der Product Owner kategorisiert die Anforderungen zum Beispiel nach neuen Funktionen bzw. nach Fehlerbehebung oder Verbesserung einer vorhandenen Funktion. Im Sprint Review überprüft der Product Owner, ob das neue Product Inkrement unter Berücksichtigung der Planung die Anforderungen erfüllt. Sollte dies der Fall sein, ist alleine er berechtigt im Product Backlog den dazugehörigen Status auf „erledigt“ zu setzen.
Views: 22588 Fred mITSM
A Business Analyst is a creative person who works with end users to understand their jobs, pains and creatively solve those problems working with development teams. On a Scrum team, that's something done by Product Owner. So Business Analysts closely map to Product Owner's role. However, they need to gain strategic skills to be an effective Product Owner. Join Satisha Venkataramaiah [https://www.linkedin.com/in/satishakv/] in any of our Certified Scrum Product Owner in cities across India at https://leanpitch.com/cspo-workshops/ ----------------------------------------------------------------------------- Please write back to us at [email protected] or call us at +91 80416 14192 for more information. Facebook: https://www.facebook.com/Leanpitch/ Twitter: https://twitter.com/leanpitch LinkedIn: https://in.linkedin.com/company/leanpitch
Views: 1218 Leanpitch Technologies Private Limited
In this "Agile Tips" video, Certified Scrum Trainer, Angela Druckman gives management tips on how to best support your Product Owner. She explains the Product Owner role and their needs and requirements. Keep Learning: http://www.collab.net/AgileTips Get Training http://www.collab.net/AgileTraining
Views: 10434 CollabNet VersionOne
Product Owner vs Scrum Master Transcript: http://defineagile.com/2019/03/10/difference-between-product-owner-and-scrum-master/ What is the difference between Product Owner and Scrum Master ? Are they the same thing ? What is the role of a Scrum Master vs Product Owner ? In this video I am talking very high level about the two roles Product Owner and Scrum Master. I am covering the main differences between the two, and what they are responsible for. This video will be useful if you pursue career of a Product Owner or a Scrum Master but not sure which one to choose. Also, if you are already doing one or the other (or both), it will give you a good perspective which are your actual responsibilities. I have been working as a Scrum Master for a long time, I have also played Product Owner role on many occasions. Those two roles are often confused. Sometimes - Product Owner and a Scrum Master is the same person. In the end of the video I will be giving you an advice, how you should approach the situation when you do not have a dedicated Scrum Master. I am open for any questions you might have. Please leave them in the comments down below. I will be happy to connect with if you are a fan of Agile like I am. Linkedin: linkedin.com/in/anatolyspektor Twitter: @defineagile Facebook: https://www.facebook.com/Define-Agile... Thank you for watching! Please subscribe because I am planning from now on to post 1 video a week. -~-~~-~~~-~~-~- Please watch: "Kanban vs Scrum - Differences Explained in 4 minutes" https://www.youtube.com/watch?v=8TzeyKl3Pv8 -~-~~-~~~-~~-~-
Views: 3301 Define Agile
Dies ist die deutsche Version des grandiosen Videos von Henrik Kniberg (original: http://blog.crisp.se/2012/10/25/henrikkniberg/agile-product-ownership-in-a-nutshell). Lerne das Wesentliche über Agiles Produktmanagement in nur 15 Minuten! Übersetzung: Corinna Baldauf (http://finding-marbles.com/), Sprecher: Toby Baier (http://www.agilesproduktmanagement.de)
Views: 56159 Toby Baier
http://www.agilejournal.com/agileconnect - While the product owner (PO) role is arguably the most crucial role within agile teams, we often hear horror stories about POs who aren't available to their teams, change their minds incessantly on business priorities, or ignore quality requirements and technical debt. Even the best POs struggle to meet the demands of their "regular business-focused job" while providing sufficient team guidance. Bob Galen shares real-world situations where he's observed product owners who deliver truly balanced value for their business stakeholders. Find out how story mapping and release planning set the stage for effective team workflow by establishing a big picture product view for everyone to see. Explore ways to develop shared goals—at both the iteration and release levels—to cement the partnership between the product owner and the rest of the team. Learn from Bob how to set up a tempo of regular, focused backlog grooming sessions to enable the team and the PO to prioritize well-nuanced and high-value backlogs. Leave with ideas for establishing an ecosystem where the PO and the entire team strive to continuously improve their performance.
Views: 6136 CMCMediaInc
www.DISYS.com While the product owner (PO) role is arguably the most crucial role within Agile teams, we often hear horror stories about POs who are not available to their teams, change their minds incessantly on business priorities, or ignore quality requirements and technical debt. Even the best POs struggle to meet the demands of their "regular business-focused job" while providing sufficient team guidance. DISYS Fellow Bob Galen shares real-world situations where he has observed product owners who deliver truly balanced value for their business stakeholders. Find out how story mapping and release planning set the stage for effective team workflow by establishing a big picture product view for everyone to see. Explore ways to develop shared goals—at both the iteration and release levels—to cement the partnership between the product owner and the rest of the team. Learn from Bob how to set up a tempo of regular, focused backlog grooming sessions to enable the team and the PO to prioritize well-nuanced and high-value backlogs. Leave with ideas for establishing an ecosystem where the PO and the entire team strive to continuously improve their performance. An Agile Methodologist, Practitioner, and Coach based in Cary, NC, Bob helps guide companies and teams in their pragmatic adoption and organizational shift towards Scrum and other Agile methods and practices.
Views: 752 DISYSGlobal
At #play14, Luxembourg, 14.-16.Mar.2014) Michael Tarnowski (Plays-In-Business.com) facilitated an open space session playing with 5 teams his new agile game "Product Owner Challenge (POChallenge)". "POChallenge" is an agile game with Lego bricks. The goal is to illustrate a waterfall-driven product development culture transitioning from Waterfall to Agile the agile mindset: communicate face-to-face clear objectives, requirements, and product vision -- a real challenge for a product development department. Play the game, contribute your ideas, and stay tuned! Web: http://bit.ly/POChallenge -- Twitter: @POChallenge, #POChallenge
Views: 2893 Michael Tarnowski
"FREE SCRUM MASTER CERTIFICATION TRAINING: http://bit.ly/pwrscrmytfree In this video, learn the different responsibilities of scrum team roles (scrum master, product owner and development team) — ► Download Your Free Scrum Ebook Here: http://bit.ly/freescrumebookYT — Watch all of my scrum master certification videos HERE: ►https://www.youtube.com/playlist?list=PL-AJA_8WK4zgOCex0qnvE4_ueJH_Zc7ZO Agile Scrum is a simple framework you can use to create any product and manage any project. It allows you to deliver on time, get early return on investment and explode your productivity through the roof! Whether you are a complete newbie, scrum master, product owner, team member, business stakeholder or preparing for a scrum certification, I can help you. Download my free scrum ebook now for a complete overview of scrum HERE: http://www.freescrumebook.com Paul VII is the CEO/Managing Director and Chief Scrum Master at Pashun Consulting Ltd. He is the Author of Scrum Mega Pack and over 100 Kindle books , 9 Udemy Training Courses and hundreds of audiobooks and videos on Scrum. -- ► Subscribe to My Channel Here: https://www.youtube.com/channel/UC_Uw-Bb0P28GpMzDgeARQWQ — Pashun Consulting is a specialist in Scrum training and coaching within major global organisations such as BBC, General Electric, Oracle, BSkyB, HiT Entertainment and Razorfish. Make sure to stay tuned for the latest Scrum training, whether you are a newbie, Scrum Master, Product Owner or Stakeholder. — Have you heard the term “agile development” before? Or maybe you have asked yourself “what is scrum?”. Agile scrum is a simple framework for completing even the most complex project. I train you from the basics to advanced topics all based on the scrum guide (from scrum.org). This is essential if you want to gain a Professional Scrum Master ( PSM 1 ) certification or any other certification ( such as the CSM ) You will need this training to learn product owner scrum basics so you can use scrum development to build your product. What set’s us apart is that unlike other training which uses an altered scrum model , we teach you how to become a scrum product owner, scrum master or team member or even how to plan using techniques such as planning poker ( with scrum cards ) using the official rule book, the scrum guide. Terms such as scrum, scrum agile and quesrtions such as “ what is a scrum master ? “ are all expplained and answered in my training videos, so be sure to check them out. I cover all the most popular topics such as scrum artifacts,what is scrum master, scrum poker and agile vs scrum. So if you are seeking a Scrum Master Certificate, need training on a scrum definition, or want answers to the question “ what is a scrum ? ” Then you have come to the right place. This is your number one resource for agile and scrum training with additional videos on topics like kanban scrum comparisons. — Follow Me Online Here: ►Facebook: https://www.facebook.com/paul.vii.3 ►Twitter: https://twitter.com/freescrumebook ►Udemy: https://www.udemy.com/user/paulvii2/ ►Website: http://www.pashunconsulting.co.uk/ — Subscribe to my VIP Newsletter for exclusive content and giveaways here: http://bit.ly/freescrumebookYT"
Views: 670 Paul VII - Scrum Master Certification
Delivering value through effective Program Increment execution With SAFe® 4 Product Owner/Product Manager Certification Based on version 4.6 of SAFe ---------------------------------------------------------------------------------------------------- Develop the skillsets needed to guide the delivery of value in a Lean enterprise—and learn about the activities, tools, and mechanics used to manage backlogs and programs—by becoming a SAFe® 4 Product Owner/Product Manager (POPM). During this two-day course, attendees will gain an in-depth understanding of the Agile Release Train (ART), how it delivers value, and what they can do to effectively perform their role. They will also learn how to apply Lean thinking to write Epics, break them down into Features and Stories, plan and execute Iterations, and plan Program Increments. Finally, attendees learn about the Continuous Delivery Pipeline and DevOps culture, how to effectively integrate as Product Owners and Product Managers, and what it takes to relentlessly improve the ART. To perform the role of a SAFe® Product Owner/Product Manager, attendees should be able to: Apply SAFe in the Lean enterprise Connect SAFe Lean-Agile principles and values to the PO/PM roles Collaborate with Lean Portfolio Management Explore continuous value with Program Increment Planning Execute the Program Increment and deliver continuous value Articulate the Product Owner and Product Manager roles Create a role action plan
Views: 272428 Aleph Technologies, LLC - Global Scrum Team™
Many business analysts feel like their role is not needed in agile. We hear that agile teams don’t want “requirements” and so we assume they don’t want business analysts! Nothing could be further from the truth. Here’s exactly why agile teams need business analysts. Learn more at: http://www.bridging-the-gap.com/agile-business-analyst/
Views: 4478 Bridging the Gap
47. The Product Owner Is Not The Problem III // Who are the THREE most powerful people in a software development "team"? And what can we do to help them work together more effectively? → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe In Part 1 we talked about step-changes... boundaries... discontinuities. In Part 2 we talked about the quality of relationships in the software development team. And their importance. This time we'll zoom in on the relationships between these players: - Business Owner - Product Owner - Lead Developer And ask the question: "What can be done to improve these key relationships?" LINKS -- Part 1: https://www.youtube.com/watch?v=0z5ExmD4fM0 -- Part 2: https://www.youtube.com/watch?v=IVDW-2lFidM Music: 260809 Funky Nurykabe: ccmixter.org/files/jlbrock44/29186 Previously: a road sign. Another road sign. This time: Yet another road sign. Oh.. and we'll move on from problem to solution Previously ---- In the last episode, I sprinkled road signs with stick figures. First, I mapped the relative sizes of the "discontinuities" between the team members. But then my brain then popped up with its "So what " question So I started again and mapped the relative importance of each of the relationships. So far so interesting. "Weighted Discontinuities" ---- I now have two rather crazy diagrams. Two crazy diagrams... that are related: The second [importances] is like a lens through which the first [discontinuitities] can be viewed. What I'd like to do is "magnify" the DISCONTINUITIES by the relative size of the IMPORTANCES to get a WEIGHTED discontinuity . He's the idea: this multiplied by this gives this this multiplied by this gives... a smaller "this" and this multiplied by this gives ... an enormous "this" I can now apply this "weighting" process to the discontinuities diagram: these four stay about the same size. These actually get smaller get smaller These two get bigger And this one gets MUCH bigger. Three key players ---- As I said last time: my search for answers started with the Development Team, but it lead me to this gang of three: the Business Owner the Product Owner and the Lead Developer What am I saying I'm saying that in my experience, the greatest improvement in a software development organisation can come as a result of improving the interactions of these three players. So what can be done I think there are two broad approaches... both of which got a mention in Part 1. Approach 1: Impedance Matching ----- Remember the electronic components The trick was to match the impedances as closely as possible. How do you do that with people Well, is to help each see the world from the other's point of view. To "get" where the other person is coming from. To walk a mile in their shoes. This, dear viewer, is what "Development that Pays" tries to do. Most of the episodes are intended to help these two [Product Onwner and Lead Developer] understand each other, But you'll also find the odd episode designed to help the Product Onwner and Lead Developer to understand where the Business Owner is coming from Approach 2. "Multi-coating" ------ The reflections on the glass lens were reduced by adding an intermediate layer. One big step is replaced by smaller steps. But what do we put on the step Not what. But whom. What about a Scrum Master Or (the term I prefer) the Agile Coach One of the most powerful things that an Agile coach does is to bridge the gap between the product owner and the Lead Developer. That's the immediate benefit The longer terms benefit is that the product and the lead developer move toward each other over time. Win win. https://www.youtube.com/watch?v=XbXP-Lho67w https://www.youtube.com/watch?v=502ILHjX9EE
Views: 2407 Development That Pays
In this quick explainer, Erika Flora employs any Scrum team's favorite tool (the post-it, of course) to explain the role of the Product Owner.
Views: 147 Beyond20LLC
Vaidas is CTO and co-founder of mobile payments ecosystem UAB „WoraPay“. He is the author of the blog and Agile trainings and consultancy center in Lithuania www.agilecoach.lt. Vaidas is also the president of Agile Lithuania association, as well as Agile project management lecturer at Vilnius University Faculty of Mathematics and Informatics (VU MIF). Vaidas has gather many years of experience of using and implementing Agile project management methods in companies. He shares his experience by running in-house and public Agile project management trainings as well as speaking in conferences. He is Certified Scrum Professional (CSP), Certified Scrum Master (CSM), Certified Scrum Product Owner (CSPO), and member of Lithuanian Project Management Association (LPVA). The only skill good Product Owner needs! There are many books and trainings that describe what good Product Owner should be. I have been a Product Owner for more than 5 years now. During this time I learned that there is only one skill that is essential to good Product Owner. I am ready to share it with you together with few "stories from the trenches" that will illustrate it.
Views: 6522 Agile Lietuva
Scrum Roles and Responsibilities. One of the most important things for the success of scrum is the role of the Product Owner, who serves as an interface between the team and other involved parties (stakeholders). It can be said that in companies that use scrum, the tasks and responsibilities of the particular Product Owner are never the same. A scrum team has a slightly different composition than a traditional waterfall project, with three specific roles: product owner, scrum master, and the development team. And because scrum teams are cross-functional, "the development team" includes testers, designers, and ops engineers in addition to developers. In Scrum there are three roles – Team member, Product Owner and ScrumMaster. Those three working together are called the Scrum Team (or just the Team). I add a fourth role – Stakeholder – to recognize all the people who orbit a Scrum Team and influence them. 1. Sprint Planning Meeting: This meeting begins with the Product Owner. This is where he or she explains her vision for the project as well as ways for the team to meet this goal. During this meeting, team members decide the amount of work they can complete in a timely manner. This is also when the team moves work from the Product Backlog to the Sprint Backlog. This step requires a lot of planning and usually this takes around 8 hours for the group to decide on a finalized 30-day Sprint. 2. Daily Scrum and Sprint Execution: From the planning meeting, we move into the daily scrum meetings. Every single day for about 30 minutes, the team gathers together to report any issues or progress on their tasks. Though brief, this meeting is an essential part of the scrum process. It is designed to keep all group members on track in a cohesive manner. Normally the Product Owner is present during all daily scrum meetings to assist in any way. 3. Sprint Review Meeting: This meeting is used to showcase a live demonstration of the work completed. During this meeting the Product Owner, Scrum Master and stakeholders are present to review the product and suggest changes or improvements. 4. Sprint Retrospective Meeting: This meeting is held to facilitate a team’s reflection on their progress. The team speaks openly about their organizational concerns and teamwork. During this meeting, dialogue should remain friendly, non-judgmental and impartial. This review session is a key part of team building and development and it’s also very important for future scrum projects. 5. Backlog Refinement Meeting: The last type of scrum meeting reviewed in this article is the backlog refinement meeting. Team members focus on the quality and skill work involved during sprints. This meeting is necessary for the business owners to connect with the development team and is used to assess the quality and development of the final product. This meeting involves important reflection on the team backlogs. These backlogs are often written in User Story form and specify what makes the product useful to the consumer.
Views: 547 harshal lonare