> First of all, both agile manifesto and this new one annoy me, mostly because the statements are far too open ended and vague to be of use.
The Agile Manifsto isn't supposed to be "of use" in the sense of a canned methodology, its supposed to be a starting point for thinking about what works for you rather than adopting canned methodologies. So, that's as designed.
(The Async Manifesto doesn't really seem vague -- it dictates specific practices as well as general principles. So I think its unfair to ding it for vagueness, and better to ding it for the specific practices being generally ill-conceived.)
The Agile Manifsto isn't supposed to be "of use" in the sense of a canned methodology, its supposed to be a starting point for thinking about what works for you rather than adopting canned methodologies. So, that's as designed.
(The Async Manifesto doesn't really seem vague -- it dictates specific practices as well as general principles. So I think its unfair to ding it for vagueness, and better to ding it for the specific practices being generally ill-conceived.)