Remove 2011 Remove Agile Remove Innovation Remove Planning
article thumbnail

Exploit vs. Explore – When to Choose Agile over Traditional Approaches

Vitality Chicago

Agile ways of working have become extremely popular since 2001 when the Manifesto for Agile Software Development was published. But does agile work in all contexts? Deciding When to Choose Agile over Traditional Approaches. Exploit vs. Explore is Better than Agile over Traditional. Context Counts!

Agile 91
article thumbnail

The Complete Guide to Scaling Agile and SAFe for Business Agility

Agilemania

What is Scaling in Agile? Agile is a set of values and principles. Agile is an umbrella term for a group of iterative product development frameworks. It encourages adaptive planning, exploratory development, fast delivery, and continuous improvement. Facilitate teams of teams planning. Scaling Agile Frameworks.

Agile 98
Insiders

Sign Up for our Newsletter

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

article thumbnail

The Roles and Responsibilities of a SAFe Agilist You Never Knew

Agilemania

It was circa 2011 when Dean Leffingwell decided to conceptualize the Scaled Agile Framework. SAFe is a knowledge base of proven, integrated principles, practices, and competencies for achieving business agility using Lean, Agile, Systems Thinking, and DevOps. You need business agility. Let’s get kickstarted.

article thumbnail

Do we really need SAFe, LeSS, Spotify, or Nexus to be agile?

Agilemania

Agility at scale topics appears in most of the conversation nowadays, either to solve multiple teams coordination issues working on the same initiative, in the name of business agility, or enterprise agility. There are numerous frameworks those claim to solve or provide solutions for agility at scale.

Agile 93
article thumbnail

How To Write Good User Stories – An Aggregate of User Story Articles

BA Squared

If your agile project is struggling to stay above water, it’s possible you have holes in your user stories! When I coach agile teams, I often see user stories organized by technology component instead of user value. Huge User Stories : If your user stories cannot be developed in the planned iteration, they are too big.

Agile 246
article thumbnail

Comprehensive Guide to Becoming A SAFe Agilist

Agilemania

Added to this is the complex problem of managing multiple agile teams. The question still stands as to how to make an organization agile so that different functions within the organization can work together and not in silos? It was, for this reason, Dean Leffingwell decided to conceptualize SAFe® in 2011. Sounds too common?

article thumbnail

Evolution of Scrum – A Trip Down Memory Lane

Cprime

As most Agile practitioners are aware, the Scrum framework has been around since the 1950s. From 2010 to 2011, several interesting changes occurred with regards to Scrum. From 2011 to 2013, the Scrum guide was further refined to include a few key changes described below. This is a rule that is often misunderstood by teams.