{ "success": true, "comment": "\x3cdiv class=\"comment comment-published odd\"\x3e\n\n  \x3cdiv class=\"clear-block\"\x3e\n      \x3cspan class=\"submitted\"\x3eMon, 2009/03/09 - 6:12pm — \x3ca href=\"/users/ksu257\" title=\"View user profile.\"\x3eKSU257\x3c/a\x3e\x3c/span\x3e\n  \n  \n  \x3cdiv class=\"comment-score-div\"\x3e\n      \x3cspan class=\"comment-score-label\"\x3eScore: \x3c/span\x3e\x3cspan class=\"comment-score\"\x3e-4\x3c/span\x3e\n    \x3c/div\x3e\n\n  \x3cdiv class=\"comment-voting-controls\"\x3e\n    \x3cspan class=\"comment-promote\"\x3e\x3c/span\x3e \x3cspan class=\"comment-bury\"\x3e\x3c/span\x3e\n  \x3c/div\x3e\n\n  \n    \x3ch3\x3eNo, I am in the 2K\'s\x3c/h3\x3e\n\n    \x3cdiv class=\"content\"\x3e\n      I know about eXtreme Programing and I think that it is a good idea. \"Agile Software Development\" appears to be similar.  XP requires that you \"Release early, release often\"\r\n\x3cp\x3e\r\nHowever, these good ideas are not an excuse for  writing code without designing it first (hacking) and the poor design that is the usual result.  XP and ASD do not mean that we should discard the traditional engineering cycle (analyze, design, implement), rather they require that the cycle is done many times on a small part of the project rather than the inefficient old school method of doing it once for the whole project.\x3c/p\x3e\x3cp\x3eIs the KDE project actually meeting the goals stated in the ASD manifesto?\x3c/p\x3e\x3cp\x3e\r\nhttp://agilemanifesto.org/\r\n\x3c/p\x3e\x3cp\x3e\r\nWorking software?\r\n\x3c/p\x3e\x3cp\x3e\r\nCustomer collaboration?\r\n\x3c/p\x3e\x3cp\x3e\r\nIf not, perhaps we need to refine our development methods.\r\n          \x3c/div\x3e\n  \x3c/div\x3e\n\n  \x3c/div\x3e\n" }