Product Manager Framework: Scrum Methodology
A Better Way Of Building Products
Scrum Guide 2017Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value.
Scrum itself is a simple framework for effective team collaboration on complex products. Scrum co-creators Ken Schwaber and Jeff Sutherland have written The Scrum Guide to explain Scrum clearly and succinctly. This Guide contains the definition of Scrum. This definition consists of Scrum’s roles, events, artifacts, and the rules that bind them together.
Lightweight Simple to understand Difficult to master Scrum Glossary The Scrum Glossary is meant to represent an overview of Scrum-related terms. Some of the mentioned terms are not mandatory in Scrum, but have been added because they are commonly used in Scrum.
To learn more about the Scrum framework, to identify which of these terms are required elements of Scrum and to understand how the mentioned elements are connected, we highly recommend that you reference The Scrum Guide. To learn more about terms specific to software development teams using Scrum and agile software development techniques, reference the Professional Scrum Developer glossary.
The Scrum Framework Scrum is simple. It is the opposite of a big collection of interwoven mandatory components. Scrum is not a methodology. Scrum implements the scientific method of empiricism. Scrum replaces a programmed algorithmic approach with a heuristic one, with respect for people and self-organization to deal with unpredictability and solving complex problems. The below graphic represents Scrum in Action as described by Ken Schwaber and Jeff Sutherland in their book Software in 30 Days taking us from planning through software delivery.
Scrum Framework An Introduction to the Scrum Framework This short video provides a simple overview of Scrum, allowing viewers to learn about the roles, artifacts and events and how they come together to deliver a product to market.
Hear from the Creators
This video highlights the latest version of The Scrum Guide with Ken Schwaber and Jeff Sutherland walking through the latest updates and tackle several myths that exist today. They provide insights into why they created Scrum, how they have used it through the years and where Scrum is going.
The Scrum Values Scrum ValuesAlthough always considered to be a part of Scrum and often written about, in July 2016, the Scrum Values were added to The Scrum Guide. These values include Courage, Focus, Commitment, Respect, and Openness. Read the Scrum Guide to learn more about these values, how they apply to Scrum and download this poster.
The Roles of the Scrum Team The Scrum Team consists of a Product Owner, the Development Team, and a Scrum Master. Scrum Teams are self-organizing and cross-functional. Self-organizing teams choose how best to accomplish their work, rather than being directed by others outside the team. Cross-functional teams have all competencies needed to accomplish the work without depending on others not part of the team. The team model in Scrum is designed to optimize flexibility, creativity, and productivity.
Where Does Your Current Role Fit? Watch this webinar on The Truth About Job Titles in Scrum to learn more about how roles have evolved and where you may fit.
Scrum defines three roles, the Product Owner, Scrum Master and Development Team Member. But what happens if you have a different job title? It doesn’t mean that you are out of luck or out of a job, in most cases it means the exact opposite with your job expanding to deliver more value in the Scrum Team. So, where do you fit in Scrum?
In this webinar, Dave West, CEO and Product Owner of Scrum.org talks about the roles of Scrum and how the three roles relate to your existing job titles. He describes the future of work in the context of an agile delivery model and what the implications are to job descriptions and career progression.
The Scrum Events Prescribed events are used in Scrum to create regularity and to minimize the need for meetings not defined in Scrum. All events are time-boxed. Once a Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process. The Scrum Events are:
Sprint Sprint Planning Daily Scrum Sprint Review Sprint Retrospective Scrum Artifacts Scrum’s artifacts represent work or value to provide transparency and opportunities for inspection and adaptation. Artifacts defined by Scrum are specifically designed to maximize transparency of key information so that everybody has the same understanding of the artifact. The Scrum Artifacts are:
Product Backlog Sprint Backlog Increment Learn from the Community There are over 100 books about Scrum on the market today, tens of thousands of papers, articles and presentations, but it all starts with The Scrum Guide. The Scrum Guide was written and is maintained by the creators of Scrum, Ken Schwaber and Jeff Sutherland and is considered as the Body of Knowledge for Scrum.
With over 200,000 members of our Scrum community, you can ask a question to the Forum and expect responses that will immediately help you. Our community of Professional Scrum Trainers (PSTs) are experts in their field and are always writing Blogs which provide insights from their experiences working directly on Scrum Teams. Articles, white papers, videos, webinars and other materials are often published by the community and available in the Resources section of the website and read other ways to learn about Scrum.