PUBLIC MARKS with tags agile & software

I’ve written previously about my allergic reaction to process maturity models for Agile development. Based on 5 years of empirical feedback being a part of or watching what  succeeds versus falls back, I do not believe their is a “cookbook” for Agile adoption

no cookbook

The Chicken Test

If it walks like chicken and clucks like a chicken, it probably is a chicken. And if the team is treating you like a chicken, then you are probably acting like a chicken.

WAgile, as all know, stands for "Waterfall-Agile", and is the pinnacle of dysfunctional development methodologies.

Great software requires collaboration and communication. Fit is a tool for enhancing collaboration in software development. It's an invaluable way to collaborate on complicated problems--and get them right--early in development.

Fit allows customers, testers, and programmers to learn what their software should do and what it does do. It automatically compares customers' expectations to actual results.

How this can work with some web app requirements?

Using Evidence-Based Scheduling is pretty easy: it will take you a day or two at the beginning of every iteration to produce detailed estimates, and it’ll take a few seconds every day to record when you start working on a new task on a timesheet. The benefits, though, are huge: realistic schedules.

Realistic schedules are the key to creating good software. It forces you to do the best features first and allows you to make the right decisions about what to build. Which makes your product better, your boss happier, delights your customers, and—best of all—lets you go home at five o’clock.

A more general approach that the SCRUM one I got so far.