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

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. Plans will change – expect it! They estimate, plan, develop, test and deploy the solution. Are you just getting started with Agile and Scrum?

Agile 103
Insiders

Sign Up for our Newsletter

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

article thumbnail

In Appreciation of the Agile Manifesto

Vitality Chicago

I was busy in 2001 with the challenges of delivering technology solutions using the waterfall approach that was dominant at that time. The waterfall approach was heavy on process and documentation and light on success rates. The meeting in 2001 represented a crystallization of great ideas from different approaches.

Agile 52
article thumbnail

The Complete History of Agile Software Development

Agilemania

They would identify problems and work to create a plan that solves the problem. This waterfall approach needs you to stick to the plan set at the very beginning of your project. Now, this created a lot of havoc since a fixed plan could be inconvenient. Working software over comprehensive documentation. Build the product.

Agile 98
article thumbnail

Agile vs. Scrum: what’s the difference?

Monday

Traditional Waterfall approaches also rely heavily on documentation, which tended to slow everything down. A group of these managers, dubbing themselves “organizational anarchists,” got together in 2001 for a now-legendary meeting at a ski lodge. Working software over comprehensive documentation. Get started.

Agile 52
article thumbnail

6 Reason to choose Agile Project Management over Traditional Project Management

Agilemania

This rigid, top-down approach contains some fixed stages, such as plan, design, build, testing, user acceptance, deployment, release, etc. Unlike agile, traditional project management plans everything beforehand and not empirically. But, in today’s first pace world, it’s impossible to plan out everything traditionally.

article thumbnail

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

Vitality Chicago

At the time, Highsmith called it the best supported training and documentation of any of the ecosystems. FDD consists of a minimalist, five-step process that focused on developing an overall object model, features list and then planning iterative design and build steps. Beedle tragically passed away in March of 2018. Lean Development.

Agile 74