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: 1804278 Henrik Kniberg
This presentation was recorded at GOTO Amsterdam 2017 http://gotoams.nl Benjamin Mitchell - Partner at Equal Experts ABSTRACT Many people have experienced using Agile approaches within teams to deliver more working software, but what can be learnt from combing these approaches with Product Development? This talk will cover the top seven hard-earned tips I learnt from several years [...] Read the full abstract here: https://gotoams.nl/2017/sessions/124 https://twitter.com/gotoamst https://www.facebook.com/GOTOConference http://gotocon.com
Views: 12351 GOTO Conferences
Adapted from Crisp's blog by Henrik Kniberg. Explaining his MVP drawing. This drawing shows up all over the place, in articles and presentations, even in a book (Jeff Patton’s “User Story Mapping” – an excellent read by the way). Many tell me the drawing really captures the essence of iterative & incremental development, lean startup, MVP (minimum viable product), and what not. However, some misinterpret it, which is quite natural when you take a picture out of it’s original context. Some criticize it for oversimplifying things, which is true. The picture is a metaphor. Find the original article here: http://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp Video by The CRM Team. For more great content have a look at our resources page here: http://thecrmteam.com/resources/
Views: 107953 The CRM Team
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: 16570 CA Technologies
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: 50126 Agile Training Videos
Comparison of product-based and project-based development efforts using the ServiceNow ITBM Agile 2.0 application. Applies to UI16, the latest version of the user interface, in the Kingston release. May apply to future releases as well. UI16 is the default user interface for new instances, starting with the Geneva release. To get UI16 on upgraded instances, the UI16 plugin must be activated. Role required: none For best video quality, increase your player resolution to 1080p. For more information, see: ServiceNow product documentation: https://docs.servicenow.com/bundle/kingston-it-business-management/page/product/agile-development/concept/agile-development.html ServiceNow Education Services: http://www.servicenow.com/services/training-and-certification.html ServiceNow Community: https://community.servicenow.com/welcome ServiceNow TechBytes Podcast: https://community.servicenow.com/community/experts-corner/techbytes-podcasts For general information about ServiceNow, visit: http://www.servicenow.com/ Your feedback helps us serve you better! Did you find this video helpful? Leave us a comment to tell us why or why not.
Views: 6348 ServiceNow Support
Tommy Norman demonstrates how to create a product backlog. This lesson is an excerpt from the video course "Scrum Product Owner LiveLessons". Purchase the 4+ hour video course at 50% off using the code YOUTUBE from informit.com/YouTube Safari Subscribers - watch the video course at https://www.safaribooksonline.com/library/view/scrum-product-owner/9780134840451/
Views: 25348 LiveLessons
Learn how to write good user stories for Agile teams. If you'd like a free book on this topic, please see below... I've published a book called "Starting Agile" that is designed to help you start your team's Agile journey out right. You can buy a copy from Amazon, but I'm giving free copies away to my subscribers from YouTube. You can signup for a copy at this link: https://mailchi.mp/326ba47ba2e8/agile-list
Views: 114761 Mark Shead
As Agile become mainstream increasingly organizations are looking to double down on the role of the Product Owner encouraging them to manage the intersection between technology and the business. But Product Ownership is a difficult role as it tries to balance the needs of the business with the reality of software delivery. Also, for many organizations there is some ‘confusion’ with existing roles of business analyst, product manager or even project manager. What does the product owner do anyway? In this talk Dave West, Product Owner and CEO Scrum.org, the home of Scrum and Professional Scrum Trainer with Prowareness Rob van Lanen describe the genesis of the Product Owner role and how many organizations are dealing with the challenges of slotting this key role into existing product, project and release roles. They will introduce some techniques such as user-centric design, and hypophysis based development and describe how approaches such as Lean Startup and pragmatic marketing are providing product owners with a tool box to do their job.
Views: 18519 Scrum.org
This short video you will teach you on how to prioritise your product backlog using Weighted Shortest Job First method If you like it, do not forget to Share, Like & Subscribe to my channel Twitter: @_KrishnaR_ Blogger: goo.gl/fyRYgn
Views: 14258 Krishna R
http://www.mlwebco.com - In this video, I explain the Agile Scrum Development process (in plain speak) and talk about how UI/UX (Product Design) fits in.
Views: 30312 Mike Locke
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: 5772 Development That Pays
Want are User Stories and how do you write them? In this UX tutorial for beginners I show you how! ____ IF YOU LIKE MY CHANNEL, HERE ARE SOME NEXT STEPS... 1) HIRE ME: Want me to work with your startup or business? https://bit.ly/2AybHq8 2) FREE EBOOK: "How to start a career in UX" https://bit.ly/2xuYDDE 3) FREE PORTFOLIO REVIEW: Get my thoughts on your portfolio... https://bit.ly/2KuhpxM ____ In this video I go over what user stories are, how to write them and how to use them to create a product using an agile workflow. What is a User Story? It's a short, simple description of a product feature, told from the perspective of the person who wants that feature or as a potential/existing user of a product or service. They are used to define the product backlog in an Agile development workflow. The product backlog is a collection of user stories that drives feature development for a product or service. How do you Write a User Story? They are composed of 3 parts: - #1 User persona - #2 The feature the user requires - #3 The need satisfied by that feature Example: As a (user) I want a (feature) so that I can (satisfy a need). What is an Epic? An epic is essentially a very big user story which likely includes many other smaller user stories. Example (Airbnb): I want to find holiday destinations and travel abroad. Let's break own this example: Step 1 : Write our epics Epic #1 As a user I want to discover new and interesting destinations Epic #2 As a user I want to book accommodation in a foreign city. Epic #3 As a user I want to create an experience in a foreign city Step 2 : Break these epics into smaller stories ____ CREATE USER STORIES Sticky notes - http://amzn.eu/hDUuw9a Sharpie marker pens - http://amzn.eu/jhbAm8w FAVE UX TOOLS Webflow - https://webflow.com/ UX Pin - https://www.uxpin.com/ Balsamiq - https://balsamiq.com/ InVision - https://www.invisionapp.com/ Trello - https://trello.com/ Lucid Chart - https://www.lucidchart.com/ ____ Check out my social for more UX tips: Instagram: https://www.instagram.com/robertsmith.co/ Twitter: https://twitter.com/robertsmith_co
Views: 38222 Robert Smith
Hunting value through conversations. This is a skill that helps Product Owners when working with stakeholders, analysts and requirements engineers. Start with identifying your project partners, and use the 7 Product Dimensions (user, interface, activities, data, control, environment and quality attributes) to uncover correct requirements for your product. Understand how you can use it to focus on value, deliver value and optimise value. Unfortunately all too often, many Product Owners do much of their work alone. We want the participants to experience the power of the conversation structured to hunt value through a specifically designed dojo, and we want to create better awareness of good requirements engineering practices. This session is intended to help Product Owners and Business Analysts create better requirements and to help them have richer and more powerful conversations. The session is based on the work of Ellen Gottesdiener and Mary Gorman’s “Discover to Deliver” as well as the work of James Shore and Diana Larsen’s Agile Fluency Model. Conference: http://2016.agileindia.org Slide and Other details: https://confengine.com/agile-india-2016/proposal/1857
Views: 523 ConfEngine
This video from Analyst Zone touches upon the four pillars of agile development methodologies. You will learn the significance of concepts, principles, methods and techniques in the agile development methods such as LEAN, Scrum, DSDM, SAFe etc.
Views: 124 AnalystZone
JoinAgile Podcast presents an interview with a Lead Agile Product Owner who works for a major Australian Telco, and came on the show to share some of his experiences and findings as he transitioned into the role. Learn more about what a real Product Owner does in Waterfall-Agile large scale corporate environments, and get some pointers for your career development if you have ever considered becoming a Product Owner. Hopefully you'll find this enjoyable and useful to you professionally. *** #Podcast is available on #iTunes, #Stitcher and #SoundCloud, with new episodes scheduled to be released weekly: https://itunes.apple.com/au/podcast/lean-and-mean-agile-podcast/id1269551866 Please show your support by SUBSCRIBING and sharing this with your friends and colleagues who you think could also benefit from this knowledge. You could also follow me on Twitter and LinkedIn. Looking forward to connecting with you! *** http://JoinAgile.com http://Twitter.com/iarandine https://au.linkedin.com/in/iarandine
Views: 7585 JoinAgile Initiative
Understand what is product roadmap with real-world examples. We will also take a look at public roadmaps of two software product companies. Complete course to become the product manager and get the job you love. For more videos enroll in the course below ENROLL NOW : https://goo.gl/K1tpb4
Views: 499 iSimplyLearn
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: 7767 Development That Pays
Product Management event in Los Angeles about what agile development is. 👉 Subscribe here: http://bit.ly/2xMQLbS 🕊️ Follow us on Twitter: http://bit.ly/2xAQklN 💙 Like us on Facebook for free event tickets: http://bit.ly/2xPfjkh 📷 Don’t forget to follow us on Instagram: http://bit.ly/2eHmfJp Get the presentation slides here: http://bit.ly/2r0rmIA Find out more about us: http://bit.ly/2hcpht1 💻 What is Agile development? Product Manager at Cornerstone OnDemand, spoke about how a critical part of any Product Manager's job is execution and what Agile development is. He discussed the Agile and SCRUM processes for building software so you and your team can realize your product vision. Nick Lesec has been a full-time Product Manager for almost 4 years, starting with mobile websites in the e-commerce space and now in the enterprise social space. As a nerd for process, he has also had the opportunity to spearhead full-scale process transformations at multiple organizations and boosted his career because of it. He holds a Bachelor’s Degree in Letters and Science. Chapter 1 1:45 Why learn agile development? Chapter 2 3:05 What is agile? Chapter 3 11:00 What is SCRUM? Chapter 4 13:55 Who are the SCRUM members? Chapter 5 15:00 What are user stories? Chapter 6 24:10 What are SCRUM ceremonies? Chapter 7 26:20 Backlog grooming Chapter 8 27:55 Story points Chapter 9 44:20 Sprint planning Chapter 10 48:40 Daily standup Chapter 11 1:00:25 Sprint review Chapter 12 1:04:00 Sprint retrospective ABOUT US: We host product management, data and coding events every week in Silicon Valley, San Francisco, Los Angeles, Santa Monica, Orange County and New York. Click here to see what we have coming up: http://bit.ly/2xuqQbS Product School is the world’s first tech business school. We offer certified Product Management, Coding, and Data courses; our instructors are real-world managers working at top tech companies such as Google, Facebook, Snapchat, Airbnb, LinkedIn, PayPal, and Netflix. Our classes are part-time, designed to fit into your work schedule, and the campuses are located in Silicon Valley, San Francisco, New York, Orange County and Los Angeles. Product leaders from local top tech companies visit Product School campuses each week. Through lectures, panel discussions, and a variety of other forums, the world’s top product managers visit Product School to provide invaluable real-world insights into critical management issues. If you want to become a product manager in 8 weeks, see our upcoming courses here: http://bit.ly/2hcpht1 📓 The Product Book has arrived! Learn how to become a great Product Manager. On sale for a limited time. Get your copy here: http://amzn.to/2uJqg9A #ProductManagement #ProductSchool #Upskill #TechEducation #Education #Product #TechStartup #FinTech #Business #ProductManager #ProdMgmt
Views: 473 Product School San Francisco
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: 5584 Development That Pays
A screencast outlying key traits of project managers who work well with their engineering teams, from the perspective of a technical coach. The slides are available for download here: http://www.slideshare.net/joemoore1/7-keys-to-being-a-great-agile-pm-pcampatl-02192011 The full video of the presentation I gave at Product Camp ATL is here: http://www.youtube.com/watch?v=8QPhWma4g5I
Views: 2783 Joseph Moore
Learn how to plan, develop and deliver on all aspects of work in the lifecycle of digital products using lean, agile and systems design thinking. Take this course for free on edx.org: https://www.edx.org/course/product-management-lean-agile-system-bux-qd503x-0 Want to be the “CEO” of the digital product, but unsure which types of skillsets you may need? This course is for you. Product management drives the implementation of business models in startups and digital enterprises. Learn about the key decisions, underlying tradeoffs, and implementation decisions needed for each phase of the product life and master business and organizational logic to ensure product success in the marketplace. In this course, part of the Digital Product Management MicroMasters program, you will be introduced to frameworks for decision-making based on both economic and organizational considerations. These frameworks inform a rising product manager on how to: (i) understand customer co-creation, needs and become “a champion” for user centric development in the digital technologies. (ii) set up and manage specific work flows (e.g. either lean, agile or stage gate development tasks) that result in timely launch and upgrades of products. (iii) take a data and metrics driven approach to make product life cycle decisions including pricing, versioning, maintenance, helpdesks and end of life. (iv) shape the direction of the product based on experimentation and system design thinking by learning from product roadmaps, competitive considerations, and allied evolution of demand in digital markets. Caveat: This is not a course on software development or architecture or on product marketing. The role of a product manager is to work with these functions effectively, such that the interests of a product (e.g. its profitability) and its customers are best served. Thus, the perspectives and skills covered in this course are integrative, and allied with decision-making, in their orientation. What you'll learn Product line planning and road mapping alternatives Idea generation, customer need assessment, co-creation, definition and validation of minimal viable product (MVP) and allied set up of requirement documents Alternative approaches for lean, agile and waterfall development, along with the tools for assessing task, project and business risks (and risk mitigation strategies) at scrums or at stage gates. How to launch a product and create a go to market strategy to champion your product Performance Management: Ownership of product related profit (or loss) over various life cycle stages; how to track and optimize system performance metrics while marshalling of social media and third party data towards performance optimization
Views: 10696 edX
http://ytwizard.com/r/ZpF8cB http://ytwizard.com/r/ZpF8cB Product Management :Agile Requirements using Product Backlog Learn to manage requirements as a scrum product owner using user stories ( Business Analysis , Scrum Master)
Views: 249 Виктор Филипенко
There is currently a push within the project management community to extend the use of agile methodologies, such as Scrum and Kanban, to other industries beyond software development. This short video advises on how realistic and sensible it is to do this.
Views: 1723 SimpleP3M
Product Backlog Grooming or Backlog refinement for Agile software development team. Links to the Article https://agiledigest.com/agile-digest-tutorial/product-backlog-grooming/#WHAT https://agiledigest.com/agile-digest-tutorial/product-backlog-grooming/#WHY https://agiledigest.com/agile-digest-tutorial/product-backlog-grooming/#WHO https://agiledigest.com/agile-digest-tutorial/product-backlog-grooming/#WHEN https://agiledigest.com/agile-digest-tutorial/product-backlog-grooming/#INSIGHTS https://agiledigest.com/agile-digest-tutorial/product-backlog-grooming/#METRICS https://agiledigest.com/agile-digest-tutorial/product-backlog-grooming/#POST
Views: 11712 Agile Digest
This webinar discusses the fundamentals of the Product Manager and the Product Owner Role in Agile Teams. For more on Agile and to download the full PPT on this webinar visit, http://synerzip.com/free-downloads.htm. Agile development methodologies have the potential to deliver higher-quality software, more quickly and more often. On commercial software projects, product managers are typically responsible for understanding market/customer needs, defining the "right" product, and driving business processes that eventually bring in revenue. What does a product manager do, and how does this change with agile? Is a product owner different from a product manager? How do up-front requirements relate to customer showcases and frequent user feedback? Rich Mironov will take us through what development managers should know about agile product management. During this webinar, you will learn: -What product managers do, how agile expands this, and why development teams only see one part of the product management role -Why market risks outweigh technical risks -Core skills for your product managers and product owners Rich will draw on a wealth of real-world experience to help attendees build more successful and more profitable products. Presenter: Rich Mironov, Principal Mironov Consultants Rich Mironov is considered an expert on agile product management, marketing and pricing. His 30 years in Silicon Valley include product leadership at Tandem and Sybase, executive positions at four software start-ups, and consulting engagements with more than 40 tech companies. He chaired the product management tracks at the Agile 2009 and Agile 2010 conferences, and pioneered the meet-ups known as Product Camps. He is the author of "The Art of Product Management." Rich is a Principal at Mironov Consulting, where he consults to technology companies on product strategy, product management and agile transformations.
Views: 4954 Synerzip
To learn more about Actify SpinFire, Visit: http://www.actify.com/cad-viewer/ In this webinar, you will learn how design teams and manufacturers are using cost effective CAD viewing software to improve communication and collaboration, benefiting from faster access to feedback resulting in a faster time to market. Watch the webinar on our website: http://www.actify.com/videos/agile-product-development-powered-actify-spinfire-ultimate/
Views: 444 ActifyInc
How does your company or new venture go about developing new products? Would you like to see faster returns from new product development? In today’s rapidly changing marketplace, speed and agility are key. New product development, done quickly and efficiently, can cement the future success of a company. In contrast, poorly managed product development can be slow, frustrating and a drain on company resources. This one hour webinar will introduce you to agile new product development, and methods you can use to fast track your development process. Key topics to be covered include: • Rapid Product Development – Accounting for the value of time • Prototyping ideas through early release • Building market feedback into your NPD system Presented by Robert Geddes & Gerard Ryan
Views: 1180 QMISolutions
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: 21639 Agile Lietuva
NEWSLETTER — join 18,000 peers: https://age-of-product.com/subscribe/?ref=youtube Scrum has proven to be a practical product delivery framework for digital products like applications or apps. However, Scrum is equally suited to build the wrong product efficiently as its Achilles heel has always been the product discovery part. What product discovery part, you may think now. And this is precisely the point: The product owner miraculously identifies what the best way to proceed as a team by gating and prioritizing the product backlog is. From sunk costs, HIPPO-ism, my-budget-my-features to self-fulfilling prophecies - learn more about the numerous product discovery anti-patterns that can manifest themselves when you try to fill Scrum's product discovery void. HOST: Stefan Wolpers BLOG: https://age-of-product.com/webinar-product-discovery/ TRANSCRIPT: Hello, everybody. Welcome to the first Hands-On Agile Webinar. I'm your host Stefan Wolpers, and today we will be talking about product discovery anti-patterns. The first one basically everyone knows, it 'my budget, my feature.' Think Jira monkeys and coders. The product department is more treated like an internal agency, and stakeholders pursue the, "we pay for you," approach. Number two, speaking of silos, for example, marketing or sales, insist on channeling communication with customers and users. Their sales people are preventing [the product team] from talking directly with customers, which is making user interviews and user research very problematic. Number three, coders code. Engineers are supposed to deliver code and nothing else. They are not supposed to, for example, talk to customers, very often under the label that coders are too expensive and too scarce and they shouldn't waste time on talking to customers. I believe this is pure Taylorism at work. It's entirely output oriented. Number four, okay, as a product team we shouldn't assume a victim role here. We also contribute in some form or another to this whole product discovery anti-pattern process. For example, there's one issue that regularly triggers frustration on the side of the stakeholders if we are not transparent about how we work. Next category: personal issues. So, personal agendas, I don't think we have to talk about it in detail. Pet projects: pet projects are stakeholder driven. However, they do not exclusively apply to the middle management. You can also think of gold plating as an engineering approach, or why an exotic new technology suddenly becomes a part of the tech stack. A root-cause analysis will probably point to the "what is in it for me?" syndrome with one or more stakeholders. Number six, HiPPOism. HiPPO stands for highest-paid person's opinion, and there's the famous quote of Jim Barksdale of Netscape, "If we have data, let's go with the data. If all we have are opinions, let's go with mine." However, there's no scientific proof that the pay grade of an individual is linked to his or her ability to identify what's worth building. Number seven, bonus at risk: the misalignment between individual incentives on the one side and the team objective on the other side. Shortly before the end of the bonus period, the product team gets swamped with must-have requirements from sales. Psychological issues, the third and most interesting category of product discovery anti-patterns. The sunk cost fallacy, number eight. We believe that we make rational decisions most of the time. In fact, we're often only rationalizing them afterward. Substitution, number nine. Another piece from Kahneman's book. Kahneman's system number one tends to deliver answers to most of the questions that come to your mind very quickly. Now, for example, consider the question, "How's your life nowadays," which would require you to reflect on and analyze. That's actually another part of your brain. Yet, you come up with an answer immediately. The trick here is that the brain's actually not answering this complicated question, but it's answering a related question. For example, "How was your mood today?" and takes this substitute question as the ground for the belief that you answered the original question. #10 - Validating your solution: This self-fulfilling prophecy is closely related to the "I know what we have to build" issue we just talked about. With the best intentions, you want to validate your hypothesis and solution, you are data-driven, right? Survivorship bias, number 11. Survivorship bias or survival bias is the logical error of concentrating on the people or things that made it in the past through some selection process, and overlook at the same time what didn't happen, typically because of a lack of visibility. The last one, number 12: psychological distance. Steve Jobs once said, "It's really hard to design products by focus groups. A lot of times people don't know what they want until you show it to them."
Views: 1926 Age of Product
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: 10324 CollabNet VersionOne
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: 34551 Aleph Technologies, LLC - Global Scrum Team
NEWSLETTER — join 18,000 peers: https://age-of-product.com/subscribe/?ref=youtube If you are working as a product owner, there is — very likely — room for improvement. I curated the most common product owner anti-patterns to help you up your game. If you like to improve on those anti-patterns that you recognize why don’t you ask the scrum master and the team for support? The product owner anti-patterns list is a good starting point for a mutually beneficial retrospective. According to the Scrum Guide, the product owner is sole and accountable person optimizing the work of the engineers. In other words, the product owner has ideas or identifies ideas, or at least he or she curates suitable ideas from wherever and validates them whether those ideas are “product backlog worthy” or not. In my experience, this approach turns the product owner into the Achilles heel — or bottleneck by design — of the whole process. If you "remove" the PO as an independent and respected role, for example, by sticking with your organizations' stage-gate process, Scrum easily mutates into a Waterfall 2.0 process. This Hands-on Agile webinar addresses 12 familiar product owner anti-patterns interfering with the concept of the Scrum product owner role. Learn how to improve your professional performance by avoiding the typical product owner mistakes: from oversized product backlogs and prioritization by proxy, to be absent during the sprint, and outing yourself as a loner during the sprint review. HOST: Stefan Wolpers NEWSLETTER: Learn about new webinars in advance: https://age-of-product.com/subscribe/?ref=youtube BLOG: “Product Owner Anti-Patterns”: https://age-of-product.com/product-owner-anti-patterns/ SLIDEDECK: https://www.slideshare.net/wolpers1/handson-agile-webinar-6-product-owner-antipatterns CONTENT: (1) The first anti-pattern covers the oversized product backlog: The product backlog contains more items than the scrum team can deliver within three to four sprints. This way the product owner creates waste by hoarding issues that might never materialize. The product owner is probably using the product backlog as a repository of ideas and requirements. (This practice is clogging the product backlog, may lead to a cognitive overload and makes alignment with the ‘big picture’ at portfolio management and roadmap planning level very tough.) (2) The second anti-pattern covers creating the product backlog in the wrong way: The product owner treats product backlog items not as a token for discussion to build a shared understanding of the why, how, and what with the team, but as deliverables. Often, the PO creates product backlog items upfront by copying from requirement documents without including other members of the scrum team. (3) The third anti-pattern covers the weak product owner: The PO has not learned to say no to stakeholders demanding new requests. Trying to being everybody’s darling creates mediocre products that do not scale, though. It also defies the product owner’s most important duty: protecting the product backlog from tasks with little or no value. (4) The fourth anti-pattern covers prioritization by proxy: A single stakeholder or a committee of stakeholder prioritizes the product backlog — not the product owner. (The strength of Scrum is building on the strong position of the product owner. The product owner is the only person to decide what tasks become product backlog items. Hence, the product owner also decides on the priority. Take away that empowerment, and Scrum turns into a pretty robust waterfall 2.0 process.) (5) The fifth anti-pattern covers the omniscient product owner: The PO does not involve stakeholders or subject matter experts in the refinement process, and probably not even the Scrum team. (6) The sixth episode covers the lack of a sprint goal: The product owner cannot provide a sprint goal, or the chosen sprint goal is flawed. (7) The seventh anti-pattern covers the pushy PO: The product owner pushes the development team to take on more tasks than it could realistically handle. Probably, the product owner is referring to former team metrics such as velocity to support his or her desire. (8) The eighth anti-pattern covers how the product owner might be toying with the definition of ready. The PO tries to squeeze in some last-minute user stories that do not meet the definition of ready. (9) The ninth anti-pattern covers the absent product owner. If the PO is not available for immediate clarification, he or she will create artificial queues that probably will put the scrum team’s sprint goal at risk. (10) The tenth anti-pattern covers the product owner who cannot let go product backlog items once they become sprint backlog items. (11) The eleventh anti-pattern covers the selfish product owner, presenting “his or her” accomplishments to the stakeholders. (12) The twelveth anti-pattern covers the unapproachable, the broadcasting product owner.
Views: 1152 Age of Product
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: 53233 Toby Baier
This module covers the hidden fifth meeting that's essential to success at Scrum and other Agile approaches. Subtopics include how to recognize well-formed Product Backlog Items (PBIs), a team effort estimation game, decomposition of large PBIs (e.g. "epics") into smaller ones (e.g. "user stories"), acceptance criteria, definition of done, Product Backlog prioritization, and team self organization. This is an interactive, scenario based module. The learner observes a simulated team and is prompted to help them as they face various challenges. See the entire series! http://www.collab.net/ScrumTrainingSeries INVEST by Bill Wake http://xp123.com/articles/invest-in-good-stories-and-smart-tasks/ Definition of Done http://blogs.collab.net/agile/2008/10/14/suggested-topics-for-definition-of-d... Agile Manifesto http://AgileManifesto.org For the full quality, interactive version of this video, see: http://www.collab.net/ScrumTrainingSeries Find a Scrum class in your city: http://www.collab.net/services/training/agile Scrum Reference Card: http://www.collab.net/sites/default/files/uploads/CollabNet_scrumreferencecard.pdf Example ScrumMaster's Checklist: http://www.collab.net/sites/default/files/uploads/ScrumMaster_Checklist.pdf
Views: 250720 CollabNet VersionOne
Are you new to Agile and wondering what the Agile lifecycle looks like? Maybe you've been doing Agile and want to learn how other real world teams have been executing the lifecycle? This webinar will walk through what problems we're trying to solve by moving to Agile and then take you through a journey of the various activities, requirements and real world tips from the trenches of Agile teams.
Views: 75475 Agile Training Videos
L'animation de Henrik Kniberg sous-titrée en français: Il s'agit d'une journée de formation sur le rôle de Product Owner compressée en une animation de 15 minutes. Il y a évidemment beaucoup plus à dire sur ce rôle, considérez la donc comme un résumé de haut niveau. Si vous souhaitez sous-titrer cette video dans une autre langue, voyez cette page : If you plan to subtitle this video in another language, please refer to this page : http://blog.valtech.fr/2013/01/09/agile-product-ownership-henrik-kniberg-en-vostfr/
Views: 21360 Cédric Chevalérias
In this webinar, Dr. Robert G. Cooper – “father” of the Stage-Gate process and innovation guru – explains how many leading manufacturing firms are blending Agile methodologies with their existing processes to stunning results. He describes how this Agile-Stage-Gate methodology makes processes more adaptive and flexible, and more agile and responsive to customers, resulting in better products and accelerated time-to-market.
Views: 1121 Planisware
Melissa Perri (ProdUX Labs – New York) Lean Product Management Product Management has traditionally been a waterfall process. Teams will spend months building a product, only to find out after releasing it that none of their customers wanted to use it. Applying Lean Startup methods to Product Management can help teams create valuable products in shorter amounts of time. This talk will dive deep into the Product Management process from a Lean standpoint. We’ll discuss how the process works seamlessly on Agile teams. I’ll share my experiences implementing Lean into my role as a Product Manager, my challenges, and how it’s completely reshaped the way I approach building products for the better. Melissa Perri is a Product Manager and UX Designer from New York City. She is the founder of ProdUX Labs (produxlabs.com), a consultancy that specializes in providing guidance and workshops on Product Strategy, UX and Lean Startup methodology to startups and enterprises. She previously cofounded a company in Italy, participated in an international startup accelerator, and worked as a Product Manager and Lead UX Designer for two growing startups in NYC. Currently, she is teaching the Product Management course at General Assembly. Melissa is a firm believer in lean methodologies and measurable design. Through in person global workshops and classes on Skillshare, she teaches companies and individuals how to incorporate lean methodologies into their existing product teams. She also coaches and speaks about Lean UX and Lean Product at conferences, most recently at Lean Agile Scotland, and the iCatapult Startup Accelerator. When not in the office, you can find her mentoring at Lean Startup Machine workshops, exploring global startups, and plotting her next big venture Agile on the Beach Conference, Cornwall UK 2014 www.agileonthebeach.com Dates next year 2-3 Sept 2015
Views: 949 Agile on the Beach
Author and entrepreneur Eric Ries unpacks the difference between waterfall and agile product development theories, and outlines when each are best employed. Waterfall - the linear path of product build-out - is best used when the problem and i
Views: 3543 Entrepreneurship.org
SAFe (Scaled Agile Framework) is emerging as one of the best known approaches to scaling Agile development. But what does it mean to software product managers? In this webcast, we'll explore: - What is the Scaled Agile Framework (SAFe) and why is it important? - What are the key benefits of adopting SAFe? - What is the product manager’s role in organizations implementing SAFe? - How can I determine if my organization could benefit from SAFe?
Views: 2938 Greg Prickril
An excerpt from the "Scrum Repair Guide" by Mike Cohn: https://www.frontrowagile.com/courses/scrum-repair-guide ... This chapter of Mike Cohn's eLearning video training course, "Scrum Repair Guide," discusses how to understand problems with the product backlog, from how detailed items should be to what types of items belong on a backlog and to what backlog grooming is and when to do it. Earn four PDUs, SEUs and a certificate of completion after successfully completing the full course. Course may be downloaded or streamed at FrontRowAgile.com
Views: 32370 Front Row Agile
Slides: http://www.slideshare.net/Pivotal/scaling-your-product-team-while-staying-agile Software companies large and small need to move fast, and that typically requires growing your product teams beyond the proverbial “two pizza” rule. Finding and keeping great people is tougher than ever these days, but there is much more to scaling a product organization than just hiring! In this talk, Dan will walk through the challenges and opportunities encountered as product organizations grow from beyond the single agile team, based on real world experiences of Pivotal Tracker, a popular agile project management tool that’s been around for 10 years, as well as other fast growing product teams at Pivotal. Topics discussed will include the importance of a strong culture, pair programming as a growth strategy, vertical vs horizontal team organization, the product manager role, how design fits into a product team at scale, and much more. SpringOne Platform 2016 Speaker: Dan Podsedly; VP & GM, Pivotal Tracker.
Views: 1565 Pivotal Software, Inc.