Product Innovation, Agile Transformation, Design Thinking
Needs can come from different users of your product, or from different internal stakeholders who sometimes may conflict with each other. For example, one stakeholder may want you to incorporate in your product the ability to snap photos and post them on social media. Another stakeholder may want an Artificial Intelligence (AI) system that is able to understand human language
In this episode of Product Bytes we interview Suman Sarkar, Head of Digital Product Management at OneMain Financial (NYSE: OMF), who shares product leadership lessons managing teams of product managers at large and small companies. This is an excerpt from the interview, published in our Product Bytes channel. Suman: I am Suman Sarkar. How do I introduce? So, most of
In this episode of Product Bytes we interview Toby Russell, co-CEO of Shift (NASDAQ: SFT), who shares product leadership lessons from building Shift. This is an excerpt from the interview, published in our Product Bytes channel. Toby: I am Toby Russell. I am the co-CEO of Shift. We run a company that essentially sells cars online and we are the
I am often asked the question: “How can we use Scrum for hardware projects?” The Scrum framework was created out of software projects as a way to improve productivity, deliver higher quality, and reduce time to market. In software, where things can be easily put together, tested, and if needed changed rapidly, everyone understands the benefits of Scrum in delivering
The new Scrum Guide is here. It’s been three years since the last update to the venerable guide was last published, and finally the new 2020 version has been released. Scrum is still Scrum, in all its simplicity. We are going to look at what’s new in this latest release. Scrum is a framework to build complex products using an
We were half-way in Sprint Planning and suddenly it hit me. Like a light bulb turning on. I had been listening to the discussion between the Developers and the Product Owner and all seemed normal… until this very moment. I just realized that the team was planning their sprint with absolute no idea of velocity or capacity. How did I
I always struggle with the word “requirements”. This is how specifications and functionalities are normally called when working on a project. Requirements create a blanket of necessity and limit the empowerment of product managers to be effective at solving problems. The word requirement, and its verb counterpart to require, in their essence define something that is “required”, “needed”, “expected”. The
The main goal of the Scrum Master is to create a highly productive team that is self-organizing and continuously improving. They do this by acting as a servant leader, coaching the team when needed, and creating the space for team members to own their work, their decisions, and the opportunities for self-improvement. Many Scrum Masters act in the dark side.
We wanted to provide a quick guide to Kanban including a list of resources to learn about what Kanban is and how to get started with Kanban. What is Kanban? (David Peterson)https://kanbanblog.com/explained/ What is Kanban? (Atlassian)https://www.atlassian.com/agile/kanban How to Create a Kanban Board for Any Projecthttps://kanbanzone.com/2019/create-kanban-board-for-any-project/ How To Create An Efficient Kanban Board/Processhttps://purplegriffon.com/blog/create-kanban-board-process 32 Practical Kanban Board Exampleshttps://kanbanize.com/kanban-resources/kanban-software/kanban-board-examples Kanban Tools The
Books This is a short list of great books on Agile, Scrum, and practices to become an effective Scrum Master. Scrum and Agile foundations “Essential Scrum: A Practical Guide to the Most Popular Agile Process“, by Kenneth Rubin “Your Scrum Playbook“, Fabian Schwarts, CST “Scrum: The Art of Doing Twice the Work in Half the Time“, by Jeff and JJ