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

Scrum Master Interview Questions (1): Scrum Master Role

Scrum.org

A Scrum Team’s communication with stakeholders should not be run through a gatekeeper (e.g. solely through the Product Owner) because this hurts transparency and negatively affects the team’s performance. Increased software quality can be demonstrated by measurably less technical debt, fewer bugs, and less time spent on maintenance.

SCRUM 230
Insiders

Sign Up for our Newsletter

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

article thumbnail

New PM, New Choices

Leading Answers

When our projects undertake defined, repeatable work using technologies and approaches our organizations have experience in, then uncertainty and change rates are typically low and manageable. Designing something is typically a consensus-gathering and problem-solving exercise. Consider the process of designing a new car or home.

article thumbnail

Transformation Corner: The Intersection of Product and Project Managers

MPUG

Product Manager To understand the general scope of the work, we will review the generally regarded areas of expertise of the Product Manager and the Project Manager. Product Managers typically have a background in business, marketing, or engineering, and may work in various industries, including technology, consumer goods, and healthcare.

article thumbnail

The Truth About Transformations

Leading Answers

Iterative development of small batches of work, with frequent reviews, provides better insights into progress and issues than sequential, large-batch development. Since they now represent the organization's f ace and communications vehicle, expect ongoing investment in their upkeep and technology refresh cycles.

article thumbnail

Stories about Stories in Agile Development

MPUG

Things such as value delivered, cost incurred, risk involved, knowledge gained etc. There will be work items to improve the infrastructure, improve processes, find a response to a risk, etc. Every development team uses a number of infrastructure related to coding, debugging, deployment, and configuration, among many others.

Agile 99
article thumbnail

The Truth About Transformations

Leading Answers

Iterative development of small batches of work, with frequent reviews, provides better insights into progress and issues than sequential, large-batch development. Since they now represent the organization's f ace and communications vehicle, expect ongoing investment in their upkeep and technology refresh cycles.