Remove Cadence Remove Influencer Remove Technical Review
article thumbnail

11 Proven Stakeholder Communication Tactics

Scrum.org

The two formal Scrum events that come to mind are: Sprint Reviews. The Sprint Review is Empiricism at work: inspect the Product Increment and adapt the Product Backlog. It is also because of this context that calling the Sprint Review a “sprint demo” does not match its importance for the effectiveness of the Scrum Team.

article thumbnail

Minimal measures for minimal stability in a complex environment

Scrum.org

One aspect of ‘complexity’ are the parameters, variables and events that influence an activity and its course. Sprint is a stable container event that provides overall rhythm and cadence to the opportunities for inspections and adaptations foreseen within a Sprint; Sprint Review, Daily Scrum, Sprint Review and Sprint Retrospective.

Cadence 247
Insiders

Sign Up for our Newsletter

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

article thumbnail

58 Product Owner Theses

Scrum.org

The Product Owner theses also address the Product Owner’s part in Scrum events from Sprint Planning to Sprint Review to Sprint Retrospective, and the Daily Scrum. The Product Owner owns the “why” and influences the “what” and “who,” but never the “how.” Sprint Planning, Sprint, Sprint Review, and Retrospective.

article thumbnail

Improve Objectives & Key Results (OKRs) With Key Result Validation

Scrum.org

In the world of tech, many industry giants such as Google choose to use a management framework known as Objectives and Key Results (OKR). When used as designed, OKRs can have a massive positive influence on organizations. OKRs are most effective when the key results set for an objective are validated during the OKR cycle.

article thumbnail

Project Boards and Project Steering Groups: An Introduction

Rebel’s Guide to PM

In every case, you should have people on the group who understand the project (or who can be brought up to speed) and who have influence and interest in the outcomes. It’s fine to have a different cadence at different points in the project lifecycle. Action review and next steps. Of course, the project manager should attend too.

article thumbnail

“Agile Is Just for Software” and other Scrum Myths

Scrum.org

For example, Scrum includes five events: the Sprint, Sprint Planning, Daily Scrum, Sprint Review and the Sprint Retrospective. PI Planning serves as the cornerstone of the Agile Release Train within SAFe, establishing a synchronized cadence for multiple teams to work together towards a common goal. It is deliberately incomplete.

SCRUM 207
article thumbnail

How should I handle an agile-waterfall hybrid project?

Kiron Bondale

For example, technology deliverables might be completed in an agile manner whereas change management deliverables such as training collateral get produced in a traditional manner. Another attribute which influences this is an understanding of who is delivering which work streams.

Agile 136