Remove Blog Remove Cadence Remove Process Remove Software Review
article thumbnail

How We Reduced Cycle Time from 164 Days to 8 Days in 6 Months

Scrum.org

Due to horrible time-management on my part, we could not answer all the questions in the webinar, so we are answering them in this blog instead. You might get more value from reading this blog if you watched the recording and reviewed the slides that are available on the webinar page - A Cycle Time Journey: 164 to 8 Days in 6 Months.

Cadence 219
article thumbnail

Review People Over Process

Henny Portman

Levine wrote with People Over Process – Leadership for Agility a very pragmatic and down to earth book about leadership and agile projects. Furthermore, neither agile or scrum contemplates how the agile team should be connected to a larger organization and to external partners who will likely have differing development processes and cadences.

Insiders

Sign Up for our Newsletter

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

article thumbnail

11 Proven Stakeholder Communication Tactics

Scrum.org

Stakeholder communication: It is simply not enough for an agile product development organization to create great code and ship the resulting product like a clockwork. 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.

article thumbnail

How Do you Make a Retrospective an Interesting Session?

NimbleWork

Many teams lean into retrospectives to help uncover areas where processes could be slicker, where engagement hasn’t been as effective as it could and to look for areas of improvement. Get Software Tools that Support the Retro Process Make sure everyone has access to software tools designed specifically for retros.

Cadence 109
article thumbnail

Scaling Agile Practices – Improve Business Outcomes

Agilemania

Develop on Cadence; Release on Demand. Teams apply a process model that is optimized for highly variable knowledge work. In SAFe®, this is known as Develop on Cadence, a coordinated set of practices that support Agile Teams by providing a reliable series of events and activities that occur on a regular, predictable schedule.

Cadence 98
article thumbnail

A Review Of Scrum For Kanban Teams

Digite

Inspired by Steve Porter’s efforts to bring process practitioners closer together and educate Scrum practitioners, I’m writing a shadow series of posts that will follow the Kanban and Scrum – Stronger Together series and continue my own efforts to clear up misconceptions between practitioners of these methods. Disclaimer.

article thumbnail

How I transformed “multiple Scrum teams” into “multiple team Scrum”

Scrum.org

In this blog I want to share some common collaboration problems and solutions I experimented with. Delivering working software is perceived as an IT responsibility instead of a Business-IT collaboration. I was successful with optimising for feature size that could be delivered in a two-sprint cadence. Lack of product focus.