17,339 Like 136 Dislike
There is probably one part of the product management job we can all agree is the hardest - people. People are unpredictable, have strong opinions and unconscious biases, and many people in your organisation have more power than you, yet are wrong just as often. In this illuminating talk from Mind the Product San Francisco 2017 Janna Bastow, Co-Founder of Mind the Product and Co-Founder and CEO of ProdPad, shares her own stories of dealing with people, and how she handles the toughest part of the job.
Agile estimation is key to selecting which stories to select for your next iteration. In this video we look at how two-score agile estimating (time and value) can help you: * Order your stories so that you deliver high-value work first * Help your customer keep a track on how much value they are getting for their money * Help the customer decide when the project is finished.
Elon Musk: How To Achieve 10x More Than Your Peers How To Give An Amazing Presentation Playlist: http://bit.ly/2poTHJX Discover The 4 Emotions You Need To Make a Killer First Impression: http://bit.ly/2IBKpCr In this video we have three tips to achieve success and improvement as shown by Elon Musk! In five hundred years, we may look back and say, "Elon Musk was the single most influential person of our entire century." He has been able to do more in his 46 years than most of us could hope to do in ten lifetimes and yes, part of that is because Elon is incredibly smart and he works incredibly hard. ...and we're so hot up; we had just one computer so the website was up during the day and I was coding at night. ...work hard like it mean every waking hour; that's the thing I would say if your particular if you're starting a company. But working 100 hours a week still only puts you at two-and-a-half times as much as the average employee. And most geniuses do not make the international impact that Elon has. In fact, the man with the highest IQ in the world, Chris Langan is a bouncer. So while smarts and work ethic are critical to Elon's success, in order to impact the world, you simply have to be able to influence other people; there's no way around it. That includes employees investors and the public at large and Elon Musk is unique here because on this channel, we can normally point to a leader's ability to nail a public speech. 02:15 Elon perseveres despite a lot of failures 05:05 Elon has a vision that inspires Connect With Us Further: Website: http://www.charismaoncommand.com Facebook: http://facebook.com/charismaoncommand Instagram: @CharismaOnCommand Or if you want to see our personal stuff (regular life + playing music): Instagram: @CharlieHoupert Instagram: @IamBenAltman
Agile team based organizations comes in many shapes. Jimmy Janlén explores how such an organization could look like, and how you get there? Camera, script, graphics and editing: Jimmy Janlén Book: Visualization Examples - https://visualizationexamples.com/ Jimmy Janlén - https://www.crisp.se/konsulter/jimmy-janlen Jimmy's blog - http://blog.crisp.se/author/jimmyjanlen Jimmy on Twitter - https://twitter.com/jimmyjanlen Educational LEGO posters - https://somethingagileleansomething.com/ Crisp - http://www.crisp.se Intro music: Dubstep (Royalty Free Music from http://www.bensound.com)
Scrum and Kanban have much in common - and some striking differences. Watch the video... and grab your FREE CHEAT SHEET. Download your FREE CHEAT SHEET: http://bit.ly/scrum-vs-kanban-cheatsheet If you've been wondering about the differences between Scrum and Kanban, you've come to the right place. Scum and Kanban are perhaps the best known of a number of Agile software development. They have much in common - and some striking differences. And don't forget to grab your copy of the Scrum vs Kanban Cheat Sheet. → SUBSCRIBE for a NEW EPISODE every WEDNESDAY: http://www.DevelopmentThatPays.com/-/subscribe Music: 260809 Funky Nurykabe: ccmixter.org/files/jlbrock44/29186 ------------------- 68. Scrum vs Kanban - What's the Difference? + FREE CHEAT SHEET Scrum and Kanban are perhaps the best known of a number of Agile software development frameworks. Let's break that down: Software Development, in very broad terms, looks like this: The Product Owner decides what to build, The Development Team builds it, and Customers use it, experience it, benefit from it in some way. What makes software development Agile is that value is delivered to the customer in small increments. And - importantly - feedback is gathered from customers and fed back into the process. It's the Product Owner's job to take input from customers - and from various Stakeholders - and organise it into a prioritised list of features and User Stories. The list is known as the Product Backlog. What happens between the Product Backlog and the Customer is what distinguishes Scrum from Kanban. As we'll see, each has its own routines and rituals. It's this person's job (see below) to help the Product Owner and Development Team to adopt and maintain good habits. In Scrum, the role is known as the Scrum Master. In Kanban, the role is known as the Agile Coach. Something that Scrum and Kanban have in common is that both are PULL systems. Without getting into two much detail, a pull system ensures that work gets from Product Backlog to Customer in the shortest possible time. A pull system also helps to uncover bottlenecks in the process, which helps to ensure that work gets from Product Backlog to Customer in the shortest possible time! As you'll see in a moment, Scrum and Kanban implement the pull system in two strikingly different ways. Scrum ----- Scrum teams work in a series of Sprints, most commonly two weeks in length. Each Sprint it proceeded by a Sprint Planning Meeting, run by the Scrum Master and attended by the Product Owner and the Development Team. Together they select high priority items from the Product Backlog that the Development Team believe it can commit to delivering in a single Sprint. This is the "pull" I was talking about earlier. The selected items are known as the SPRINT BACKLOG. For the next two weeks, the Development Team focuses on working through the items in the Sprint backlog - and ONLY those items in the Sprint backlog: in all but the most exceptional circumstances, any new requirements that arise have to wait for the following Sprint. It's common practice for Scum teams to use a board to track the progress of the work. It's called a Scrum Board... or an Agile Board... or even (slightly confusingly) a Kanban Board. Each day during the Sprint there is a Scrum Meeting: it's a stand up meeting where the team takes a maximum of 15 minutes to discuss progress and identify any "blockers". At the end of the Sprint, the work completed during the Sprint is packaged for release, and any incomplete items are returned to the Product Backlog. The Sprint ends with two rituals: The Sprint Review, which is a demonstration of new functionality to Stakeholders. The Sprint Retrospective, which is an examination of what went well, what went badly and what could be improved. The aim of the Retrospective is to ensure that the next sprint is more efficient and effective than the last. And that's Scrum! Kanban ------ Kanban does a few things differently. There's no two-week sprint: Kanban is a continuous process. And there's no Sprint Backlog; the "pull" system in Kanban happens in a different way, via Work In Progress (WIP) limits. If an Agile Board is useful for Scrum, it's a necessity for Kanban. Each column on the Kanban Board has a Work in Progress limit related to the team's capacity. For example, a team with two developers might set a limit between two and four items. The lower the better. Let's see the pull system in action: When testing of a particular feature is complete, the corresponding ticket moves to the "Done" column. The empty column is a https://www.youtube.com/watch?v=rIaz-l1Kf8w&list=PLngnoZX8cAn8VEVJtgWUKyidEaV-mJKKe https://www.youtube.com/watch?v=https://www.youtube.com/watch?v=C3P44ZYXTBs
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:
Downloadable version of the video here:
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).