3 ms·
It's still relevant - I doubt that 2% of teams do all 12 (mostly it's the pair programming) but it is without a doubt the seminal work on software in business o
by lifeisstillgood 13y ago
It's still relevant - I doubt that 2% of teams do all 12 (mostly it's the pair programming) but it is without a doubt the seminal work on software in business of the last 15 years.
- pjmlp 13y agoIn the enterprise world I move on, it is mostly a checklist to say a project is agile. Many companies are still run waterfall like, or without any kind of process. When we bring in agile methodologies into the project, it starts slowly, but eventually everything is in place and everyone is doing it in an agile way (XP, SCRUM, whatever). When the first project escalation arrives, or the deadlines are not possible to be achieved, the developers start slowly going back to the original way of working. In the end you get mini-waterfall projects with a sprint duration, but the management puts agile on the project bullet points.
- lifeisstillgood 13y agoI know the feeling - and my view is a bit brutal - but it's down to tools and people. For most enterprises automated build, test, deploy (ie CI/CD) is the one missing tool and one absolutely necessary tool to capture and keep benefits of agile - it's capital. And also for most enterprises you could lose 1/3 of the IT staff without noticing.
- henrik_w 13y agoAs edw519 tweeted: (Great Process + Average People) < (Average Process + Great People)
- pjmlp 13y agoFully agree. In the end what we get from those projects is waterfall with CI, which is still better than how things used to be on the old days. Although, one has this feeling of playing Quixote all the time.