Hacker News new | past | comments | ask | show | jobs | submit login

While this document starts strong and has some good points, it strongly conflates “scrum” with “agile” and goes downhill pretty quickly.

> wrong answer: what’s a sprint cycle?

You don’t have to have sprints to be agile. What’s important are the four values.

The manifesto says, “Individuals and interactions over process and tools” but this document then goes on to talk a lot about specific processes and tools.

It’s a trap!




A trap every freaking "Agile" company falls into. Don't get me started on fixed scope + fixed timeline that they all still do anyway, only now broken into "sprints".




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: