How to Be Agile with a Big Vision by One Kings Lane Product VP
•Download as PPTX, PDF•
2 likes•239 views
What does it mean to be agile and how to be agile whilst having a global vision for the future? Learn from this presentation.
Recommended
More Related Content
What's hot
What's hot (20)
Similar to How to Be Agile with a Big Vision by One Kings Lane Product VP
Similar to How to Be Agile with a Big Vision by One Kings Lane Product VP (20)
More from Product School
More from Product School (20)
Recently uploaded
Recently uploaded (20)
How to Be Agile with a Big Vision by One Kings Lane Product VP
- 1. www.productschool.com How to Be Agile with a Big Vision by One Kings Lane Product VP
- 2. FREE INVITE Join 30,000+ Product Managers on
- 3. COURSES Product Management Learn the skills you need to land a product manager job
- 4. COURSES Coding for Managers Build a website and gain the technical knowledge to lead software engineers
- 5. COURSES Data Analytics for Managers Learn the skills to understand web analytics, SQL and machine learning concepts
- 6. COURSES Digital Marketing for Managers Learn how to acquire more users and convert them into clients
- 7. COURSES Blockchain for Managers Learn how to trade cryptocurrencies and build products using the blockchain
- 9. Hello, I’m Andrea Grew up in NYC English and Art major 15 years in Product and Tech in Ecommerce Non-linear path into Product (analytics, design, frontend, DBA) Built and scaled teams and products, solved very interesting challenges
- 11. Product Manager Verizon Sr. Product Manager Time Warner Sr. Product Manager Zappos Director of Product Rent the Runway Director of Product IfOnly VP of Product & Engineering One Kings Lane Where I’ve worked VP of Product Boxed
- 12. Framework as a way to think about your vision and how to get it to iteratively Agile as a way of thinking and guide on how to get there while using learnings along the way Common language since we are all PMs building software and use it with design, engineering and other cross-functional partners What I’ll talk about
- 17. It all starts with a vision
- 18. Iterative Framework Define Your Vision Plan Your Route Kick It Off Check In and Repeat
- 20. What is your vision? What is the goal or problem you are solving? Focus on the why and the what.
- 21. What is agile?
- 22. Software development methodology Iterative and continuous feedback to refine and deliver software Continuous planning, testing, integration Lightweight and adaptable Empowers people to make decisions together quickly and effectively
- 23. What is scrum?
- 24. Plan Your Route
- 25. 11 human spaceflights to get to the moon First 4 tested the spacecraft 6 out of 7 landed on the moon
- 26. Each mission had a goal
- 27. Treat sprints as your Apollo mission Must have goals Must have learnings Must be shippable enough to achieve each goal
- 28. Spend the time to plan Engage your team and brainstorm Do the work Reassess after each sprint
- 29. What is a sprint?
- 30. Has a goal and learnings Duration typically 1-4 weeks Should end in potentially shippable code Scope does not change within a sprint
- 31. How much can each person do? What is their capacity? Don’t forget QA Add a buffer - we are humans!
- 32. Don’t forget to reflect back
- 33. What did we do well? What can we improve? What questions do we still have? Action items with owners How can we be better? Are we on track for our vision?
- 34. Review previous sprint Was the goal achieved? Reassess for course corrections Plan the next sprint
- 35. What did you work on yesterday? What are you working on today? Any roadblocks?
- 36. Be flexible. The path you define to get to your vision isn’t set in stone. Don’t get frustrated if you have to course correct. Focus on your vision. Don’t obsess about your failures within a sprint. Use it for learnings and focus on the big picture. Do the work. You can’t hit your vision if you aren’t willing to do the hard work. In Summary...
- 37. www.productschool.com Part-time Product Management, Coding, Data, Digital Marketing and Blockchain courses in San Francisco, Silicon Valley, New York, Santa Monica, Los Angeles, Austin, Boston, Boulder, Chicago, Denver, Orange County, Seattle, Bellevue, Toronto, London and Online
Editor's Notes
- Start by giving a quick intro about me or why am I giving a talk about this topic :)
- What did my non-linear path look like?
- What am I going to talk to you about?
- 50 years since the moon landing; huge launch Apollo 11, first manned mission to land on the Moon, on July 20 1969 Like a product launch
- Maybe it’s more like this
- Either way, it takes a team to get your release out the door
- Or this team
- It all starts with a vision
- Be bold and long-term. Be clear and pay attention to the key words and values. Write your one-pager.
- Anyone can define it?
- Extreme Programming (XP), Scrum, Crystal, Dynamic Systems Development Method (DSDM), Lean Development, and Feature-Driven Development (FDD), Kanban
- Anyone can define it?
- So how do we use this to plan our route?
- Going back to our moon landing analogy
- Each sprint has to have a goal and objectives for learning Make sure shippable enough to achieve each goal
- Spend the time to plan your route with your team (engineers, designers, analytics) Grooming or brainstorm - do the work Split stories, figure out sprints, figure out goals for each, make your tickets, prioritize, ESTIMATE Revisit after each sprint so you can course correct if needed Think of it as planning all the sprints as you can
- Anyone?
- Always set a goal for learnings -- what are we hoping to accomplish? What’s the theme? Constant duration leads to better rhythm Commit to it
- Look at the team and properly plan capacity Take into account vacation and buffer (meetings, bugs, lunch last minute stuff) - 60% of time is work time You cannot succeed and ship anything without this; understand your resources and plan accordingly Imagine if they didn’t take this into account when planning the various Apollo missions? Make sure to include QA
- Continuously improve the way in which we are delivering functionality Learn or course correct means you have to do the retrospective How did we do with our estimates? Did we share with each other when things were ready? Were the stories clear? Don’t forget to set action items with owners (otherwise you’re just venting)
- Combine it all Close tickets Do the retrospective
- Do your standups Look at the board, otherwise you’re just talking in a circle Make sure there’s progress, there’s movement