Home
Search results “Agile what is a product” for the 2016
Making sense of MVP (Minimum Viable Product)
 
11:47
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: 97183 The CRM Team
The Role of the Agile Product Owner
 
03:37
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: 13607 CA Technologies
How To Do Agile Release Planning
 
04:14
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 release planning serves as a way to bring company vision together with the product roadmap. CA Agile Management helps teams plan how to strategically execute on these plans
Views: 86125 CA Technologies
Know all about Product Backlog under 5 minutes
 
05:18
You will find everything that you need to know about product backlog in Scrum Development If you have any additional queries, do leave a comment and I would be happy to clarify Want a quick Intro to Agile under 5 minutes? Watch this video https://youtu.be/N2hDKpgzdIE Want a quick Intro to Scrum under 5 minutes? Watch this video https://youtu.be/G-MVC6EO86A Twitter: @_KrishnaR_ Blogger: goo.gl/fyRYgn
Views: 11011 Krishna R
Do we need both Product Owners and Product Managers in Agile?
 
01:05
Do we need both Product Owners and Product Managers in Agile? Sign up to get more Brain Bytes: https://goo.gl/OSxFVl
Views: 375 Construx Software
Requirements Engineering for Agile Product Owners by Steve & Pavel
 
51:17
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: 404 ConfEngine
What is Agile?
 
11:56
This short cartoon answers the question "What Is Agile?" and will give you the background to understand the Agile principles and values and how they can help you and your team work together more efficiently. If you'd like a free book on this topic, please see below... https://mailchi.mp/326ba47ba2e8/agile-list I've published a book called "Starting Agile" that is designed to help you start your team's Agile journey outright. 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 the link above. If you'd like to connect with me on LinkedIn you can find me at the link below. Just send me a message saying hello and that you found me from one of my videos: https://www.linkedin.com/in/markshead
Views: 973137 Mark Shead
Agile User Stories
 
06:52
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: 87750 Mark Shead
Part 1  Agile Projects vs  Agile Product Dev
 
05:13
In the first of a series of training videos, PRINCE2 Agile Lead Author Keith Richards discusses agile projects and agile product development.
Scaled Agile Framework (SAFe) Overview for Product Managers
 
35:57
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: 2430 Greg Prickril
Agile Best Practices: Road Maps
 
05:24
3Pillar Global's SVP of Engineering Jeff Nielsen and Product Manager Sarah Dickinson discuss the importance of Road Maps to convey the vision of how a product is expected to evolve over a period of time. In an agile approach, a road map shows the release dates and the features that are targeted for each release.
Views: 3231 3Pillar Global
Agile Product Ownership in a Nutshell
 
02:03
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: 5198 Development That Pays
Agile Product Roadmaps
 
58:54
Webinar on agile product roadmaps for agilidade.org.
Views: 564 Roman Pichler
SAFe 4.0 in 5 minutes
 
05:14
This in an introduction to the Scaled Agile Framework or SAFe 4.0
Views: 206068 LeanSamurai
Agile Data Warehousing and Business Intelligence: A Disciplined Approach
 
54:27
Webinar presented by Scott Ambler 2016-01-26 on a Disciplined Approach to DW/BI
Views: 4853 Glen Little
How to Build an Agile Team
 
02:55
Subscribe to our YouTube channel to stay up to date on all of our world-class products and exciting updates: https://goo.gl/YhZF9h Looking to implement agile development? Learn how to build an agile team and empower them to solve today’s biggest problems. For more information, visit: http://cainc.to/Lw7fmZ We believe the people who are closest to the problem are the best people to solve it. And that when you empower your teams, you prepare them to solve today's biggest problems. That’s why teams are the foundation of agility. Traditionally, teams have started as functional silos—for example, discrete groups of developers, testers, and BAs. But in fast-paced technology environments, this structure can lead to obstacles. One major issue is limited transparency. Or, put another way, what happens when we can’t see past the walls of your own silos. For example, not knowing what occurred before the work arrives on our desk— or what will happen to it after we toss it over the next wall. This means you can’t know how a change in your part of the process might have a negative impact on another group. As a result, change is discouraged. And when it does happen, it’s often difficult and painful. So how do you actually embrace change as a way to help continuously improve? The first step is learning how to build an agile team. You begin by breaking down silos and bringing together cross-functional teams of five to ten people who have all the skills you need to deliver value to your customers. When each team represents multiple functional areas, you get more perspective into the whole system. And more easily find ways to improve the system for the team and for the customer’s benefit . So who makes up an agile team? First, you need a delivery team with all the skills needed to build, test, and deliver full value to customers and stakeholders. And when we say full value, we don’t simply mean code, but code that’s working and tested and deployed. Next, you need a product owner that represents the business and deeply understands the customers' needs. They know delivering the highest-value products to customers means focusing on outcomes, not outputs. And finally, a scrum master to help teams continuously improve on their ability to predictably meet commitments. So, to summarize, teams are the foundation of agility. When you build agile teams, you build a strong foundation for agile practice. And when you empower your teams, you prepare them to solve today's—and tomorrow’s—biggest problems.
Views: 6915 CA Technologies
Agile Planning - Product Roadmaps Part #1 - Creating a Compelling Vision
 
04:50
A product roadmap is an extremely useful way to describe how a product is likely to evolve, to align the stakeholders, and to acquire a budget for developing the product. But creating an effective roadmap is not easy, particularly in an agile context where changes occur frequently and unexpectedly. During this interview, we discuss the tips to create an effective roadmap. The next video https://youtu.be/wWFQzQp1eek Video on Progressive Elaboration https://youtu.be/pOqXkVLbuHM This also talks about strategies suggested by product planning experts such as Roman Pichler.
Views: 2138 Niroshan Madampitige
Product Roadmap Process
 
03:26
In all companies, hard choices have to be made about what new product or feature ideas should be fed the company's most precious resources — time and money. A product roadmap is one way to show where resources are being spent, and a transparent, competitive process for developing this roadmap will help everyone understand why resources are being spent this way. This video outlines the qualities of the best product roadmaps we've seen.
Views: 4536 Harrison Metal
How to prioritise your product backlog in Agile using WSJF method
 
02:43
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: 11318 Krishna R
Lean Startup Tools for Agile Product Teams by Raj Indugula
 
43:38
One of the risks agile organizations face is an over-reliance on a single omni-present and omni-potent Product Owner. This critical reliance on a fallible Product Owner often results in a lack of clear direction on how and when to "pivot", with IT falling back on their bias, which is to build more and more features. In this session, we will explore how lessons and ideas from the Lean Startup movement can be effectively combined with Agile delivery in a 5-step process to drive the right business outcomes. Holistic Discovery: Assessing key customers, problems & markets Risk-Driven Product Backlog: Challenging & testing your assumptions Exploratory Sprints: Quick, cheap ways to validate your approach Data-Driven Sprint Review: Using data to drive decisions Validating Product Increment: Analyzing & evolving your production system Tools and techniques gleaned from the Lean Startup movement will be leveraged to support each of the activities outlined. Conference: http://2016.agileindia.org Slide and Other details: https://confengine.com/agile-india-2016/proposal/1846
Views: 297 ConfEngine
The Agile Product Owner Is Not The Problem
 
05:06
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: 5134 Development That Pays
Scaling Your Product Team While Staying Agile — Dan Podsedly
 
01:11:35
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.
Creating a Product Vision
 
10:35
Creating a Product Vision. This is a technique for facilitating a product vision workshop and building a pitch deck.
Views: 4170 ForxiaAcademy
Should agile methodologies be applied to hardware product development?
 
04:03
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: 1564 SimpleP3M
The Art of Building a Roadmap - Atlassian Summit 2016
 
45:02
Sherif Mansour Principal Product Manager, Atlassian The process of defining a roadmap is arguably one of the most difficult but important things a product manager has to do. Far too often roadmaps are built without the complete picture in mind, without the right timing, in silos, or are misdirected. How then can we ensure we’re doing it right? Is there really such a thing as an agile roadmap? This talk will draw from lessons learnt building product to provide practical tips and techniques enabling you to understand roadmap inputs, plan with different perspectives in mind, optimise for learning, communicate and set roadmap goals as well as find agility when the landscape around you changes. Products covered: Confluence
Views: 56223 Atlassian
In Praise of the (Agile) Product Owner
 
04:48
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: 7007 Development That Pays
How to Write Good User Stories
 
03:52
Subscribe to our YouTube channel to stay up to date on all of our world-class products and exciting updates: https://goo.gl/YhZF9h Within Agile, user stories are created to help teams understand what they are required to build and deliver. CA can help teams create compelling stories for customers about the software being built.
Views: 124013 CA Technologies
Agile CRM Product Overview
 
28:10
The video is all about the product overview of Agile CRM
Views: 24315 Agile CRM
Minimum Viable Product: You're Doing It Wrong!
 
02:01
34. Minimum Viable Product: You're Doing It Wrong! // The concept of Minimum Viable Product (MVP) is not new, but it didn't 'click' for me until I saw one perfect image. → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe Henrik Kniberg's beautiful sketch powerfully illustrates where we've been going wrong: creating products that are MINIMAL, but not VIABLE. LINKS -- Frank Robinson: http://www.syncdev.com/minimum-viable-product/ -- Henrik Kniberg: http://blog.crisp.se/2016/01/25/henrikkniberg/making-sense-of-mvp Music: 260809 Funky Nurykabe: ccmixter.org/files/jlbrock44/29186 The best definition I've seen for "Minimum Viable Product" is not a set of words. It's a sketch. A sketch that encapsulates the concept so perfectly... ... that it went viral. Frank Robinson -------- Frank Robinson coined the term "Minimum Viable Product" in 2001. The idea - at least at a superficial level - is simplicity itself: Get a version of the product in front of a customer early as possible. Not with the aim of generating early income - though that is no bad thing - but with the aim of LEARNING. The chances are that you've heard of Minimum Viable Product before today.. ... and that when you heard it, you immediate "got it". As Frank himself said: “When I first said ‘minimum viable product’ I never had to repeat myself. The words went viral right before my eyes.” BUT... Is it Viable ------- Just because something is easy to grasp, doesn't mean it's easy to do. It's not easy. Far from it. Here's the problem: We - development teams, lead developers, product owners... even business owners - usually have an idea of what the "ultimate" product might look like. Ask us to come up with a minimum version and we'll hack off a feature here and a feature there. What we end up with will certainly be MINIMAL: that's the easy part. But will it be VIABLE That's the tricky part. Enter Henrick Kniberg ----- A gentleman by the name of Henrick Kniberg captured the difference between the two perfectly in his (now viral) image: In the top line, we have minimal, but not viable (until we get the final step). In the bottom line, we have minimal AND viable every step of the way. In a recent blog post, Henrik said that he was surprised that his image went viral. I'm not surprised at all. I think it's genius. Next time. ------- Next time we'll take a look at some "real world" Minimium Viable Products. https://www.youtube.com/watch?v=rmGOBzpn_98 https://www.youtube.com/watch?v=xxjbxk8dUqI
Views: 8527 Development That Pays
Principles of Lean Product Managment by Jez Humble
 
50:46
Traditionally, project management is the paradigm used to build digital products. In this talk, we'll start by examining why traditional project management is wholly unsuitable for product development. Jez will then present the principles used to build digital products successfully in the modern lean/agile paradigm. In this session you will find out how to apply impact mapping and hypothesis-driven development to take an experimental approach to product development. We will also explore how practices such as continuous delivery and A/B testing are used to create fast feedback loops to make data-based investment decisions. Conference: http://2016.agileindia.org Slide and Other details: https://confengine.com/agile-india-2016/proposal/1960
Views: 7404 ConfEngine
Painting a Vision for Your Product - Atlassian Summit 2016
 
12:16
Sherif Mansour Principal Product Manager, Atlassian Product without vision is dead. A lot has been said about the importance of vision setting, but not much has been shared about how to actually do it. Atlassian has been through several vision setting projects for individual products as well as for the whole company. Throughout these experiences, we've learned a lot about how to practically do this. This talk will share a highlights reel containing the top tips you can take back to your product teams and use for your next vision setting project.
Views: 6800 Atlassian
The Difference Between Lean and Agile
 
02:52
Subscribe to our YouTube channel to stay up to date on all of our world-class products and exciting updates: https://goo.gl/YhZF9h Though often considered to be contradictory principles, Lean and Agile are very complementary and when paired together guide teams to better results. Agile Management solutions from CA help teams use both principles in tandem to achieve success.
Views: 47189 CA Technologies
Product Ownership and Agile Discovery
 
09:07
Ellen Gottesdiener, Chief Product Owner & Founder of EBG Consulting, recently led two sessions at Agile 2016 on the topic of Product Management. She co-presented #DiscoveryDojo: Hunting Value with Structured Conversations with Steve Holyer, and also led an Agile 2016 Stalwarts session. In this interview, Ellen joins Leading Agile host Devin Hedge to talk about product management and product discovery techniques. She also shares information on EBG's new course offering, "Vision to Value: Certified Backlog Refinement Practitioner" and her book Discover to Deliver, she co-wrote with Mary Gorman. The book is a practical guide for rapidly discovering product needs with lean/agile projects. Links: #DiscoveryDojo at Agile 2016: https://agile2016.sched.org/event/6eeA/discoverydojo-hunting-value-with-structured-conversations-ellen-gottesdiener-steve-holyer EBG website: https://www.ebgconsulting.com/ Discover to Deliver book: http://www.discovertodeliver.com/ Vision to Value: Certified Backlog Refinement Practitioner training: http://bit.ly/BacklogRefinement
Views: 332 EBGConsulting
"Agile Planning - Scrum Team - Product Owner" - Agile Training - Theory & Concepts by Dr Sam Swapn
 
09:03
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: 251 DrSam Swapn
Angel Medinilla - Lean Startup for Agile Product Management
 
34:11
Angel Medinilla - Lean Startup for Agile Product Management, Agile Prague Conference 2015.
Views: 64 Agile Prague
Know all about Sprint Planning & Agile Estimation under 6 minutes
 
06:16
In this video, you can learn about a. what preparation need to be done before Sprint planning meeting b. how to conduct the Sprint planning meeting c. how to do Agile estimation - effort based and story point based Upfront estimation in Agile during project budding - https://youtu.be/ZHo7DkfNlfo Like, Subscribe and Share!!! Links Intro to Agile under 5 minutes - https://youtu.be/N2hDKpgzdIE Intro to Scrum under 5 minutes - https://youtu.be/G-MVC6EO86A All about Product Backlog under 5 minutes - https://youtu.be/W2fnr_hbDNw Twitter: @_KrishnaR_ Blogger: goo.gl/fyRYgn
Views: 29555 Krishna R
Agile Scrum Training Part 3 - Backlog Refinement Meeting
 
07:27
The third video in this series where we discuss Scrum Development. This video describes how to conduct a Backlog Refinement meeting in detail. Full Playlist: https://www.youtube.com/watch?v=NYBBrpFKI-Q&list=PLrIm-p2rpV0Ef1hU3sGaz9aQCFnGdv8Jz Reval Govender LinkedIn: https://uk.linkedin.com/in/reval-govender-0ba14860 Twitter: https://twitter.com/RevalGovender My site: http://revgov.co.uk/ 1 - Scrum Training Series - 0:09 2 - Backlog Refinement Overview - 00:21 3 - The Backlog - 1:05 4 - Product Backlog Item (P.B.I) - 1:29 5 - A Product Backlog Example - 1:57 6 - Refining P.B.I's into Epics and User Stories - 2:26 7 - Effort Levels - 03:09 8 - Prioritising the Backlog - 03:53 9 - Refining a P.B.I - 04:46 10 - Defining Users Stories - 04:54 11 - Estimating - 05:24 12 - Finishing Up - 05:59 13 - Links - 06:45 Planning Poker Cards: http://store.mountaingoatsoftware.com/products/planning-poker-cards Complexity Buckets: http://www.slideshare.net/emanish/agile-planning-and-estimation-48116753
Views: 8187 Reval Govender
Agile Planning - Product Roadmaps Part #2 - Creating a Compelling Vision
 
11:09
This is the second part of the video, interview on product roadmap. This is an extremely useful tool to describe how a product is likely to evolve, to align the stakeholders, and to acquire a budget for developing the product. But creating an effective roadmap is not easy, particularly in an agile context where changes occur frequently and unexpectedly. During this interview, we discuss the tips to create an effective roadmap. Video on Progressive Elaboration https://youtu.be/pOqXkVLbuHM
Product People: Tami Reiss, Lean + Agile Product Management Leader
 
23:44
Join Jay Stansell in an interview with Tami Reiss, Lean + Agile Product Management Leader. We discuss some top product management tips from Tami's 10 years in product management, learn about how she founded "Just Not Sorry", how to manage executives in enterprise through a lean agile and experimentation approach. You can learn more about Tami at https://www.linkedin.com/in/tamireiss and Jay at https://au.linkedin.com/in/jaystansell
3 Awesome Minimum Viable Products (MVPs)
 
04:54
What are the best MPVs of all time? I've absolutely no idea... but Buffer, Dropbox and Zappos are three of my favourites. Grab your FREE Lean Startup Cheat Sheet: http://www.developmentthatpays.com/cheatsheets/the-lean-startup 0:15 - Ground rules for a perfect MVP 1:00 - Buffer's MVP 1:58 - Dropbox's MVP 3:23 - Zappos' MVP LINKS - Steven Cohn: https://www.linkedin.com/pulse/death-minimum-viable-product-steven-cohn - Buffer: https://blog.bufferapp.com/idea-to-paying-customers-in-7-weeks-how-we-did-it - Dropbox: http://techcrunch.com/2011/10/19/dropbox-minimal-viable-product/ - Zappos: http://www.bullethq.com/blog/lean-startup-zappos-how-zappos-validated-their-business-model-with-lean/ → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe Music: 260809 Funky Nurykabe: ccmixter.org/files/jlbrock44/29186 ------------------- 35. 3 Awesome Minimum Viable Products (MVPs) Today, we're going to take a look at three of my favourite examples of Minimum Viable Products (MVPs). Before diving in. let's establish some ground rules for a "proper" MVP It's got to be Minimal It's got to be Viable And it's got to be a Prod... Actually No, it does not need to be a Product. (I'll be showing you a great example of a "non-product" in a minute or two.) Some have argued that the word "Product" in MVP is unhelpful. Steven Cohn has made a strong case for the word "Experiment". I agree. But for now let's stick with the "P" and temporarily re-define it to.... Pre-meditated. Meaning that the MVP must be a deliberate attempt to learn about the market. This rules out cases that look like MVPs in retrospect, but were really full products that - to everyone's surprise - developed into something big. Let's get going. No. 3 - Buffer ------ Buffer is a application that makes it easy to share content on social media. Here's what they put on the their site. A test, certainly. But it falls short of an MVP in my opinion. Their next test was better. They slotted this page in-between the other two pages. Now visitors to the website are not just saying "This is interesting" They're saying "I want to BUY this". Okay, there's nowhere to input your credit card details. But anyone who got this far was at least prepared to think about parting with their money. As co-founder Joel Gascoigne said: "After this result, I didn’t hesitate to start building the first minimal version of the real, functioning product." Minimal - certainly Viable - yes Pre-mediated - check Buffer's current valuation is something close to $400 million No. 2 - Dropbox ---- Dropbox, as I'm sure you know, is a file synchronisation service. Edit a file on your desktop... ... and seconds later its updated on all of your other devices. Rewind to the early days. The team - entirely composed of techies - had the basic synchronisation working. That was the easy bit. The hard bit was going to be to achieve the same trick on pretty well every platform: Mac, Windows, iPhone, etc. Given that the team was all techies, you'd have put money on them diving straight in. But CEO Drew Houston did something surprising. He made a video. The video - just three minutes long - demonstrated the synch process end to end. But it was more than just a demo: it was full of techie in-jokes... designed to appeal to early adopters. It worked like a charm In Drew's words: “It drove hundreds of thousands of people to the website. Our beta waiting list went from 5,000 people to 75,000 people literally overnight. It totally blew us away.” Minimal - Yes Viable - Not a product that could be used, but a product that could be demonstrated. Pre-Meditated - Yes Dropbox went on to do quite well. It's current value stands between $5 and $10 BILLION. No. 1 - Zappos ---- It's 1999. Co-founder Nick Swinmurn wanted to build an online store for shoes. But would people use it Here's how he went about finding out. He popped down to lis local shoe shops he went into the shops and... ... I sh!t you not... he PHOTOGRAPHED PAIRS OF SHOES! The photos were uploaded to a super-simple website. If someone clicked on the button to buy a pair Nick would pop down to the store and... BUY THE SHOES! Zero infrastructure. Zero inventory. Minimal - definitely Viable - This time it's not even up for discussion. Most definitely: real customers; real money changing hands; real shoes! Pre-meditated Check. Zappos went on to do quite well: it was acquired by Amazon in 2009 for a cool $1.2 billion. Your thoughts, please! ---- Buffer, Dropbox and Zappos. Three of my favourite MVPs. What do you think of my choices Any you disagree with Let me know in the comments. And I'd also like to he https://www.youtube.com/watch?v=xPJoq_QVsY4 https://www.youtube.com/watch?v=cjCCS3DxZRo
Views: 58554 Development That Pays
Release Planning - The Release Burnup Chart
 
06:42
A free lesson from the "The Ultimate Product Owner" course, created by Growing Agile: https://www.frontrowagile.com/courses/the-ultimate-product-owner/overview In this video, you will learn how to plan when you have a fixed date or fixed scope. Learn about the release burn up chart and how to use it, so you can predict when you're going to release.
Views: 10035 Front Row Agile

Erp case studies pdf to excel
Qmul history dissertation topics
Ethics and science essay questions
Is a 500 word essay longstreet
Different kinds of media violence essay