Comments on: Agile MythBusters http://blogs.agilefaqs.com/2007/11/12/agile-mythbusters/ Naresh Jain's Random Thoughts on Software Development and Adventure Sports Tue, 10 Jan 2012 14:24:00 +0000 hourly 1 http://wordpress.org/?v= By: Naresh Jain » Agile FAQs Blog » Managed Chaos » Sirf Maal; No Bakwas: Agile Bootcamp http://blogs.agilefaqs.com/2007/11/12/agile-mythbusters/comment-page-1/#comment-14136 Naresh Jain » Agile FAQs Blog » Managed Chaos » Sirf Maal; No Bakwas: Agile Bootcamp Mon, 27 Apr 2009 16:06:23 +0000 http://blogs.agilefaqs.com/2007/11/12/agile-mythbusters/#comment-14136 [...] Agile Myth Busters [...] [...] Agile Myth Busters [...]

]]> By: Cambell’s Blog - Developing Thoughts http://blogs.agilefaqs.com/2007/11/12/agile-mythbusters/comment-page-1/#comment-3400 Cambell’s Blog - Developing Thoughts Fri, 23 Nov 2007 07:59:23 +0000 http://blogs.agilefaqs.com/2007/11/12/agile-mythbusters/#comment-3400 [...] Agile FAQs Blog: Managed Chaos » Blog Archive » Agile MythBusters Up? [...] [...] Agile FAQs Blog: Managed Chaos » Blog Archive » Agile MythBusters Up? [...]

]]> By: Mark http://blogs.agilefaqs.com/2007/11/12/agile-mythbusters/comment-page-1/#comment-2349 Mark Thu, 15 Nov 2007 20:33:56 +0000 http://blogs.agilefaqs.com/2007/11/12/agile-mythbusters/#comment-2349 Great article. Someone else I've been following quite a bit is Damon Poole from Accurev. This is a great first read on Agile for those who have misconceptions about it, and thought you may also find this one of interest after reading this blog post: http://www.accurev.com/whitepaper/breaking_release_habit.htm His blog is here: http://www.accurev.com/forums.htm Thank you again. Mark Great article. Someone else I’ve been following quite a bit is Damon Poole from Accurev. This is a great first read on Agile for those who have misconceptions about it, and thought you may also find this one of interest after reading this blog post:

http://www.accurev.com/whitepaper/breaking_release_habit.htm

His blog is here: http://www.accurev.com/forums.htm

Thank you again.

Mark

]]> By: Mark http://blogs.agilefaqs.com/2007/11/12/agile-mythbusters/comment-page-1/#comment-15512 Mark Thu, 15 Nov 2007 20:33:00 +0000 http://blogs.agilefaqs.com/2007/11/12/agile-mythbusters/#comment-15512 Great article. Someone else I've been following quite a bit is Damon Poole from Accurev. This is a great first read on Agile for those who have misconceptions about it, and thought you may also find this one of interest after reading this blog post: http://www.accurev.com/whitepaper/breaking_release_habit.htm His blog is here: http://www.accurev.com/forums.htm Thank you again. Mark Great article. Someone else I’ve been following quite a bit is Damon Poole from Accurev. This is a great first read on Agile for those who have misconceptions about it, and thought you may also find this one of interest after reading this blog post:

http://www.accurev.com/whitepaper/breaking_release_habit.htm

His blog is here: http://www.accurev.com/forums.htm

Thank you again.

Mark

]]> By: Paul http://blogs.agilefaqs.com/2007/11/12/agile-mythbusters/comment-page-1/#comment-2185 Paul Wed, 14 Nov 2007 19:06:09 +0000 http://blogs.agilefaqs.com/2007/11/12/agile-mythbusters/#comment-2185 as for #1, TDD also stands for Test Driven Development. This is where a developer starts implementing a feature by first writing a test that proves the feature works. of course the Test fails, so then the implement just enough of the feature to make the test pass. Then they write more tests and refactor the feature until you have a robust test suite covering all conceivable scenarios for the feature. It is this development style that makes people think that they can bypass traditional QA testing of a feature. as for #1, TDD also stands for Test Driven Development. This is where a developer starts implementing a feature by first writing a test that proves the feature works. of course the Test fails, so then the implement just enough of the feature to make the test pass. Then they write more tests and refactor the feature until you have a robust test suite covering all conceivable scenarios for the feature. It is this development style that makes people think that they can bypass traditional QA testing of a feature.

]]> By: Paul http://blogs.agilefaqs.com/2007/11/12/agile-mythbusters/comment-page-1/#comment-15511 Paul Wed, 14 Nov 2007 19:06:00 +0000 http://blogs.agilefaqs.com/2007/11/12/agile-mythbusters/#comment-15511 as for #1, TDD also stands for Test Driven Development. This is where a developer starts implementing a feature by first writing a test that proves the feature works. of course the Test fails, so then the implement just enough of the feature to make the test pass. Then they write more tests and refactor the feature until you have a robust test suite covering all conceivable scenarios for the feature. It is this development style that makes people think that they can bypass traditional QA testing of a feature. as for #1, TDD also stands for Test Driven Development. This is where a developer starts implementing a feature by first writing a test that proves the feature works. of course the Test fails, so then the implement just enough of the feature to make the test pass. Then they write more tests and refactor the feature until you have a robust test suite covering all conceivable scenarios for the feature. It is this development style that makes people think that they can bypass traditional QA testing of a feature.

]]> By: Top Agile Myths » Blog Archive http://blogs.agilefaqs.com/2007/11/12/agile-mythbusters/comment-page-1/#comment-1879 Top Agile Myths » Blog Archive Mon, 12 Nov 2007 13:53:23 +0000 http://blogs.agilefaqs.com/2007/11/12/agile-mythbusters/#comment-1879 [...] Naresh Jain has an excellent post on the top agile myths. Thought agile software development meant no QA and no contracts? Or that agile teams are never distributed? Think again. Naresh lists eleven myths of agile software development including myths about process, tools, documentation, testing and a lot more. Check out the whole article here. Working in an Agile team? Silver Catalyst is a lightweight project management tool for agile teams. Download now! [...] [...] Naresh Jain has an excellent post on the top agile myths. Thought agile software development meant no QA and no contracts? Or that agile teams are never distributed? Think again. Naresh lists eleven myths of agile software development including myths about process, tools, documentation, testing and a lot more. Check out the whole article here. Working in an Agile team? Silver Catalyst is a lightweight project management tool for agile teams. Download now! [...]

]]>