product-backlog-vs-sprint-backlog 
Rebel’s Guide to PM
JULY 24, 2020
And still , agile transformation consultancies spend a significant portion of their energy convincing senior executives it’s safe and good for the business to orient agile teams to build the right product vs. focusing on building the product right. What facilitation tips can you share? Facilitation is the key.
Project Bliss
JULY 26, 2020
Related reading: Scrum Master vs Project Manager: What’s the Difference? An iterative approach means delivering part of a product, getting feedback, and then adapting the product and the team based on that feedback. Scrum teams regularly build better products faster, while being happier too. Product Owner Access.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Scrum.org
APRIL 26, 2021
In their book Agile Retrospectives , Esther Derby and Diana Larsen popularized the idea that a Sprint Retrospect comprises five stages. Purpose of Sprint Retrospectives. The Scrum Team inspects how the last Sprint went with regards to individuals, interactions, processes, tools, and their Definition of Done.
Project Pulse Journal
APRIL 16, 2024
Whether you are maneuvering through the dynamic sprints of Agile or the structured phases of Waterfall, T-shirt sizing adapts seamlessly, offering a versatile tool across industry landscapes. Prepare the Backlog - Ensure the user stories and sizes in the backlog are understood. Categories may be XS, S, M, L, and XL.
Scrum.org
NOVEMBER 25, 2019
Because a "Done" increment provides transparency for everyone to inspect the increment and adapt the Product Backlog accordingly. When a Product Backlog item or an Increment is described as "Done", everyone must understand what "Done" means. Both inside and outside out influences, the sky is the limit.".
Planio
SEPTEMBER 27, 2021
Horizontal vs. vertical scaling. 10 ways product managers can help support (and encourage) scalability efforts. Balance ‘building’ sprints with ‘scalability’ sprints. Be the source of truth for vision and product strategy. If you’re unsure, we wrote an entire post on scaling product teams here!).
Scrum.org
APRIL 21, 2020
A system is a dynamic entity and can flip from a one-state into another when a certain threshold or tipping point is reached. Changing a part in a lower subsystem only affects the set-point (tipping point) of the system state. The Sales team expressed that the Scrum team is too slow in delivering product. product perspective.
Expert insights. Personalized for you.
295 
Let's personalize your content