Remove Cadence Remove Demo Remove Risk Management Remove Software Review
article thumbnail

Stakeholder Communication Strategy: Part 3 of 4 Steps of Stakeholder Engagement

Scrum.org

As not all stakeholders are the same, the product owner or manager needs to communicate with them differently as well. For example, for a SaaS (Software as a service) product, one of the key stakeholders is James Bond- Head Of IT Security. My role was to coach product owners and managers.

article thumbnail

Troubleshooting in Lean-Agile Development

MPUG

Many project managers utilize a Lean-Agile approach when there is high change or churn in project requirements, significant lack of clarity in scope, high complexity to their projects, and/or a larger number of risks associated with such. It’s usually based on a cadence. When the feature is complete, it can be delivered.

Lean 64
Insiders

Sign Up for our Newsletter

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

article thumbnail

Creating a Risk-Adjusted Backlog

Leading Answers

This article explains what a risk-adjusted backlog is, why they are useful, how to create one and how teams work with them. What is a Risk-Adjusted Backlog? A risk-adjusted backlog is a backlog that contains activities relating to managing risk in addition to the usual features associated with delivering value.

Risk 145
article thumbnail

New PM, New Choices

Leading Answers

These days, new project managers are exposed to conflicting guidance. 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. Here, traditional project management approaches work great.

article thumbnail

Agile Release Train (ART)

Digite

Program Increments (PIs) provide a development timebox (default 10 weeks) that uses cadence and synchronization to facilitate planning, limiting WIP, provide for aggregation of value and assure consistent retrospectives. In the case of IT and software domain, that would mean working- software). An Example.

Agile 98
article thumbnail

A modern (and easy) guide to the 5 agile ceremonies

Planio

But what if you’re not entirely comfortable managing and running Agile ceremonies? Sprint review ceremony. Agile ceremonies — also known as Scrum ceremonies or just ‘events’ — are specific events that provide a structured framework for iterative software development processes. And why do they matter?). Sprint planning ceremony.

Agile 88
article thumbnail

Team using “Waiting for Release” column on their kanban board

Digite

From the questioner’s post, it is not clear if their team is doing production support or software/ app dev. We do product releases every 4-6 weeks, and these get deloyed to our SaaS servers – that cadence is well established. What is the business context? Support, SLAs, Meeting Market Requirements.