Remove 2001 Remove Documentation Remove Reference
article thumbnail

Download Our Free Agile and Scrum Cheat Sheet

Vitality Chicago

This handy reference contains the 4 Agile Values and 12 Agile Principles from the 2001 Manifesto for Agile Software Development. Solutions are more important than Documents. This is a helpful reference to Agile and Scrum ways of working. Are you just getting started with Agile and Scrum? The 4 Agile Values.

Agile 103
article thumbnail

Nimble Vs Agile: why is a unique term not enough?

Analysts Corner

working software more than comprehensive documentation. This group met in 2001 and created the Agile Manifesto (2) with a set of values ​​and principles. Agile is a specific approach to getting the job done, while Nimble refers to an organization’s capability to respond quickly to changes and opportunities.

Agile 130
Insiders

Sign Up for our Newsletter

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

article thumbnail

Evolution of Scrum – A Trip Down Memory Lane

Cprime

Expressed in various forms and concepts, Scrum was formally documented and published in 2001 as the Scrum Guide by Ken Schwaber and Jeff Sutherland. Because there is little documentation on what changes occurred the time of its inception in 2001 and 2010, we will take a look at what transpired between 2010 and 2021.

article thumbnail

Half Agile Isn’t Real Transformation

Leading Agile

The latter provides a nice-looking and usable interface to the “real” systems in the back-end, to provide read and write access to customers’ data via their smart devices, and to print materials to be mailed out, such as account summaries, late payment notices, and documentation required by regulatory bodies. HP NonStop?

Agile 120
article thumbnail

Software Craftsmanship

My Agile Partner

Software Craftsmanship: Rooted in the Agile Manifesto Written in 2001, the Agile Manifesto was crafted by 17 recognized specialists in the world of software development. A book titled “Software Craftsmanship” was published in 2001 to differentiate between developers confined to an industrial mindset and agile developers.

Agile 52
article thumbnail

Agile Methodology vs Framework vs. Toolkit – Does it Really Matter Eddie?

Vitality Chicago

Not that long ago, the Disciplined Agile people underwent a change where they stopped referring to DA as a “process decision framework” and began calling Disciplined Agile a toolkit. Those of us who remember Cheap Trick will likely remember that the early agile enthusiasts were referred to as lightweights.

Agile 74
article thumbnail

Agile vs. Scrum: what’s the difference?

Monday

Project management experts refer to Agile as a project management methodology, and Scrum as a framework. Traditional Waterfall approaches also rely heavily on documentation, which tended to slow everything down. This resulted in the “Agile Manifesto,” in which the anarchists documented the 4 values you’ll see in the next section.

Agile 52