Remove Development Team Review Remove Exercises Remove Risk Remove Technical Review
article thumbnail

Remote Agile (Part 7): Sprint Review with Distributed Teams

Scrum.org

TL; DR: A Remote Sprint Review with a Distributed Team. This seventh article now looks into organizing a remote Sprint Review with a distributed team: How to practice the review with virtual Liberating Structures, including and giving a voice to team members, stakeholders, and customers.

article thumbnail

Why Scrum requires completely “Done” software every Sprint

Scrum.org

But many teams struggle with this rule. An increment is considered “Done” by the Development Team, but requires further testing and stabilization in the next Sprint. Or work is considered “Done” by the Development Team, but the install package still needs to be created. It is tempting to fall into “shades of Done”.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

70 Scrum Master Theses

Scrum.org

On the one side, they address typical Scrum events such as Sprint Planning, Sprint Review, and the Sprint Retrospective. Keeping technical debt at bay. A good Scrum Team pays attention to the preservation of an application’s technical health to ensure the Scrum Team is ready to actually pursue an opportunity in the market.

SCRUM 227
article thumbnail

From Servant Leadership to Shared Leadership

Leading Answers

Yet, in reality, some of the best leaders are quiet, introverted people who care deeply for their teams and stakeholders and quietly grind away toward a common goal. It can be learned and exercised on a small scale before being brought to bear on larger groups. Willingness to take personal risks. Good communication skills.

article thumbnail

Strategy vs. tactics: How to use both to build better products

Planio

6 rules to follow How to bring strategy and tactics together: 5 examples for different teams 1. Product development teams 2. Digital marketing teams 3. Sales teams 4. Customer service teams 5. Benefits Good strategy aligns team members and helps everyone connect to the same ‘why’. Keep them risk-free.

article thumbnail

Product Owner Anti-Patterns — 31+2 Ways to Improve as a PO

Scrum.org

“The Product Owner is responsible for maximizing the value of the product resulting from work of the Development Team.” Remember: user story creation is a team exercise.). That is too much upfront work and bears the risk of misallocating the Scrum Team’s time.). Source : Scrum Guide 2017.

article thumbnail

T-shirt sizing in Agile and Waterfall Projects

Project Pulse Journal

Let us now check the world of T-shirt sizing - one of the project management tools that promises to streamline your planning process and transform it into an engaging, team-building exercise. Review and Adjust - Once all items are sized, review the assignments to ensure consistency across the backlog.

Agile 52