Remove 2011 Remove Cadence Remove SCRUM Remove Software Review
article thumbnail

Kanban to manage Complex/ Quick Moving Situations

Digite

Most people, as well as me, are used to Scrum (or more likely Zombie-Scrum or Scrum-But ), but I believe it is too early to do proper Scrum here. In the usual Scrum process, the P.O. In my over 25+ years in the software industry, this has been an all too familiar situation! One column per person/pair?

article thumbnail

Disciplined Agile & SAFe

International Institute for Learning

They build on lean-agile thinking, and standard Scrum, Kanban, and DevOps practices. DA was developed in 2011 by Scott Ambler and Mark Lines and is based on Scott’s work at Rational Software and IBM. To coordinate the teams, SAFe applies cadence and synchronization. This configuration creates a balance of power.

Agile 59
Insiders

Sign Up for our Newsletter

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

article thumbnail

SAFe Simply Explained (Part 1): Core Competencies and Principles

Inloox

In most cases, however, previous experience is based only on the small-scale use of Scrum or other agile methods in individual departments. What usually started in software development can now be extended to the entire company and thus, change the way people collaborate. But it’s not that easy.

article thumbnail

Benefits of Scaled Agile Framework ( SAFe®) – Agilemania

Agilemania

The year was 2011 and there was a pressing need for a scaling framework that could help large organizations design efficient systems to build enterprise level products/solutions to cater to customer’s rapidly changing needs. Apply cadence and synchronize with cross-domain planning. SAFe is based on following 10 Lean-Agile principles-.

article thumbnail

Product Discovery Anti-Patterns Leading to Failure

Scrum.org

Scrum has proven to be an effective product delivery framework for all sorts of products. However, Scrum is equally well suited to build the wrong product efficiently as its Achilles heel has always been the product discovery part. How that is supposed to happen is nowhere described in the Scrum Guide.

article thumbnail

Compendium of Works to Increase Probability of Project Success

Herding Cats

Here's a collection of presentations, briefings, papers, essays, book content used to increase the Probability of Project Success (PoPS) I've written and applied over my career in the software-intensive system of systems and other domains. Agile Software Development (#ASD). Enterprise IT and Embedded Systems (#EIT).