Which best describes your current position?,How many years of experience in IT do you have?,What is the total number of people in your organization?,Where are you based?,Which sector is your organization primarily in?,What is your experience with Acceptance TDD?,What is your experience with Developer TDD?,What is your personal belief in the effectiveness of Acceptance TDD?,What is your personal belief in the effectiveness of Developer TDD?,"What benefits of Acceptance TDD have you ACTUALLY experienced (check all that apply, if any)?",,,,,,"What benefits of Developer TDD have you ACTUALLY experienced (check all that apply, if any)?",,,,,,What is the support for Acceptance TDD within your organization?,What is the support for Developer TDD within your organization?,"Of the people who should be doing Acceptance TDD, what is the adoption rate within your organization?","Of the people who should be doing Developer TDD, what is the adoption rate within your organization?","When it comes to adopting TDD within your organization, how are the potential challenges affecting you?",,,,What is your opinion about ease of learning Acceptance TDD?,,What is your opinion about ease of learning Developer TDD?,,"Based on your experience, how effective are the following strategies for learning Acceptance TDD?",,,,,,,,"Based on your experience, how effective are the following strategies for learning Developer TDD?",,,,,,,,Size of the project team?,What is the level of application of TDD?,"What other forms of testing is your team doing? (select all that apply, if any)",,,,,"Who is writing tests and when are they doing it?  (check all that apply, if any)",,,,"How is your team capturing requirements specifications? (check all that apply, if any)",,,,,,,,,,"How are you capturing design specifications? (check all that apply, if any)",,,,,,,,
Response,Response,Response,Response,Response,Response,Response,Response,Response,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Response,Response,Response,Response,Lack of skills,Lack of training/education,Lack of regression test suite(s) for existing systems,Waterfall culture,Response,Any experiences you would like to share:,Response,Any experiences you would like to share:,Pair with TDD experienced person,Pair with another TDD learner,Training in TDD,Reading a TDD book,Reading articles about TDD,Discussing TDD on online forums,Teaching it to yourself,Mentoring by someone with TDD experience,Pair with TDD experienced person,Pair with another TDD learner,Training in TDD,Reading a TDD book,Reading articles about TDD,Discussing TDD on online forums,Teaching it to yourself,Mentoring by someone with TDD experience,Response,Response,End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,Developer regression testing,Independent regression testing,Reviews/inspections of work products,Analysts write tests before developers write production code,Developers write tests before writing production code,Developers write tests after writing production code,Testers write tests after developers write production code,Customer/acceptance tests,"Defect management tool (e.g. Bugzilla, ChangeQuest)","Diagrams in drawing tools (e.g. Visio, PowerPoint)",Digital snapshots of whiteboard sketches,"Paper models (cards, ...)","Requirements management tool (e.g. Doors, ReqPro)","Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",Whiteboard sketches,Wiki,Word processor/text editor,"Defect management tool (e.g. Bugzilla, ChangeQuest)",Developer tests,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",Digital snapshots of whiteboard sketches,"Paper models (cards, ...)","Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",Whiteboard sketches,Wiki,Word processor/text editor
IT Management,21+ years,"1,001 to 10,000",North America,IT Services,I have read about it but not tried it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,"Management wants IT to adopt this practice, but is not providing resources",Management is willing to fund training and education for this practice,1% to 20%,1% to 20%,Large Impact,Some Impact,Large Impact,Large Impact,Difficult,,Neutral,,Very Effective,Effective,No Opinion,Neutral,Neutral,Neutral,No Opinion,No Opinion,Very Effective,Effective,No Opinion,Neutral,Neutral,Neutral,No Opinion,Very Effective,6 to 10,Both Acceptance and Developer TDD,,Parallel testing by independent test team throughout the lifecycle,,,,,Developers write tests before writing production code,,Testers write tests after developers write production code,Customer/acceptance tests,,"Diagrams in drawing tools (e.g. Visio, PowerPoint)",,"Paper models (cards, ...)",,,Whiteboard sketches,,Word processor/text editor,,Developer tests,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",,"Paper models (cards, ...)",,Whiteboard sketches,Wiki,Word processor/text editor
Developer,2 to 5 years,101 to 1000,South & Central America,Software,I haven’t heard about it before now,I have experimented with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Don’t know,Management is actively against this practice,Don’t know,0%,Large Impact,Large Impact,Large Impact,Large Impact,No Opinion,,Difficult,,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Very Effective,Effective,Effective,Effective,Effective,Effective,Effective,Very Effective,1 to 5,None,End of lifecycle testing by independent QA/Test Team,,Developer regression testing,,Reviews/inspections of work products,,Developers write tests before writing production code,,Testers write tests after developers write production code,,,,,,,,,,Word processor/text editor,,,,,,,,,Word processor/text editor
Other,11 to 20 years,11 to 100,Europe,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Increased quality,Increased ability of developers to safely change software,,,,,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,41% to 60%,61% to 80%,Large Impact,Large Impact,No Impact,Some Impact,Very Difficult,,Difficult,,Very Effective,Effective,Effective,Effective,Neutral,Neutral,Neutral,Effective,Very Effective,Very Effective,Very Effective,Effective,Effective,Effective,Effective,Effective,11 to 20,Just Developer TDD,End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,Developer regression testing,,,,Developers write tests before writing production code,Developers write tests after writing production code,Testers write tests after developers write production code,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,"Requirements management tool (e.g. Doors, ReqPro)",,,,Word processor/text editor,,,,,,,,,Word processor/text editor
Developer,11 to 20 years,11 to 100,South & Central America,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,6 to 10 years,11 to 100,Europe,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,61% to 80%,61% to 80%,Some Impact,Some Impact,Large Impact,No Impact,Neutral,,Easy,,Very Effective,Effective,Effective,Neutral,Neutral,Effective,Effective,Effective,Very Effective,Effective,Effective,Effective,Effective,Effective,Effective,Effective,1 to 5,Both Acceptance and Developer TDD,,,Developer regression testing,,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,,Customer/acceptance tests,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,Digital snapshots of whiteboard sketches,"Paper models (cards, ...)",,,Whiteboard sketches,Wiki,,,Developer tests,,Digital snapshots of whiteboard sketches,"Paper models (cards, ...)",,Whiteboard sketches,,
IT Management,6 to 10 years,11 to 100,South & Central America,Retail,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,6 to 10 years,101 to 1000,North America,Financial,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,"Management wants IT to adopt this practice, but is not providing resources","Management wants IT to adopt this practice, but is not providing resources",Over 80%,Over 80%,Some Impact,Some Impact,Some Impact,Large Impact,Difficult,"FitNesse is a great tool for Acceptance testing.  Our business analysts write our specifications as FitNesse tests, and we execute our code against the tests.  It works great.",Difficult,Pair Programming makes a huge difference; I highly recommend it to ramp up on the steep learning curve.,Very Effective,Very Effective,Effective,Effective,Effective,Effective,Effective,Very Effective,Very Effective,Very Effective,Effective,Effective,Effective,Effective,Effective,Very Effective,6 to 10,Both Acceptance and Developer TDD,End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,Developer regression testing,Independent regression testing,Reviews/inspections of work products,Analysts write tests before developers write production code,Developers write tests before writing production code,Developers write tests after writing production code,,Customer/acceptance tests,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,"Paper models (cards, ...)",,,,,,,Developer tests,,,,,Whiteboard sketches,Wiki,
Developer,11 to 20 years,11 to 100,Europe,Software,I am experienced with it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,Increased ability of developers to safely change software,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,"Management wants IT to adopt this practice, but is not providing resources","Management wants IT to adopt this practice, but is not providing resources",1% to 20%,1% to 20%,Large Impact,Large Impact,Some Impact,Some Impact,Difficult,"There is no ""real progress"" made while setting up the aceptance TDD environment (if nothing exist). This is making people reluctant in using acceptance TDD",Easy,,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Effective,No Opinion,No Opinion,No Opinion,No Opinion,Effective,Effective,Effective,Very Effective,No Opinion,11 to 20,Don’t know,End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,Developer regression testing,,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,Testers write tests after developers write production code,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,"Requirements management tool (e.g. Doors, ReqPro)",,,,,,,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",,,,,,Word processor/text editor
Developer,6 to 10 years,11 to 100,Europe,Financial,I have experimented with it,I have experimented with it,Has the potential for significant quality improvement,Has some potential for quality improvement,,,,,,Improved chance of keeping specifications in sync with the code,,,,,,,"Management wants IT to adopt this practice, but is not providing resources","Management wants IT to adopt this practice, but is not providing resources",1% to 20%,1% to 20%,Large Impact,Large Impact,Large Impact,No Impact,Neutral,,Difficult,To do TDD means a complete change in design of the architecture of our systems.,Effective,Neutral,No Opinion,Neutral,Neutral,Effective,Neutral,Very Effective,Effective,No Opinion,Neutral,Neutral,Neutral,Effective,Neutral,Very Effective,1 to 5,None,,,,,Reviews/inspections of work products,,,,,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,,,Word processor/text editor,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,,,
Developer,6 to 10 years,"1,001 to 10,000",Asia,Software,I have read about it but not tried it,I am experienced with it,No opinion,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Don’t know,"Management wants IT to adopt this practice, but is not providing resources",Don’t know,1% to 20%,Some Impact,Some Impact,Large Impact,Large Impact,Neutral,"Although I have read about it, I have yet to try it out. It has been really really difficult to get buy in from the stakeholders.",Difficult,"Its difficult because it requires a change in mindset. In India, developers are not very forthcoming about their inabilities because its very competitive out here. Most of the developers/programmers I know of are of the opinion that TDD will expose them as bad programmers and therefore are not even willing to try it. Besides that I doubt, they even know what real TDD is all about.",Effective,Effective,Neutral,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Very Effective,Very Effective,Neutral,Effective,Effective,Effective,Neutral,Effective,51 to 100,Regression Testing (non-TDD),End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,Developer regression testing,,Reviews/inspections of work products,Analysts write tests before developers write production code,,Developers write tests after writing production code,,,"Defect management tool (e.g. Bugzilla, ChangeQuest)","Diagrams in drawing tools (e.g. Visio, PowerPoint)",,,"Requirements management tool (e.g. Doors, ReqPro)",,,,,,,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",,,,,,
Developer,2 to 5 years,101 to 1000,Australia & New Zealand,IT Services,I have read about it but not tried it,I have experimented with it,No opinion,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,"Management wants IT to adopt this practice, but is not providing resources","Management wants IT to adopt this practice, but is not providing resources",0%,1% to 20%,Large Impact,Large Impact,Some Impact,Some Impact,No Opinion,,Difficult,"It is a struggle to break out of the coding for codes sake mentality. If TDD was taught at University in the first programming language students ever had, then this would resolve A LOT of the pain, A LOT. ( I truely believe that if anything should be taught, appart from algorthims, maths, and the underlying stuff, if anything of ""coding"" should be taught it should start with TDD, but most ""professors\academics"" aren't professional coders so I doubt they will be driven to do this)",No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Effective,No Opinion,Very Effective,Effective,Effective,Effective,Effective,Effective,Effective,Very Effective,1 to 5,Just Developer TDD,End of lifecycle testing by independent QA/Test Team,,,,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,Testers write tests after developers write production code,,,,,,,,,,Word processor/text editor,,Developer tests,,,,,,,Word processor/text editor
Developer,21+ years,101 to 1000,Australia & New Zealand,Other,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Don’t know,"Management wants IT to adopt this practice, but is not providing resources",1% to 20%,1% to 20%,Large Impact,Large Impact,Some Impact,No Impact,Difficult,"1. Using FIT with MS-Word was described by my customer as a real pain compared with her running the software and eyeballing the results.    2. My use of selenium-IDE to record ""through the browser"" tests of a website with AJAX controls from Telerik has been hard work compared to writing NUnits on plain old .NET classes.",Difficult,"Thinking about why colleagues don't ...    There's lots to learn: how to use NUnit, how to design so it's testable, how to work in small steps. The last 2 can be big changes for people.    There's some acts of faith: I can get through the work fast enough if I write tests too, there's more value in spending time writing a test now than ib moving on to next feature.",No Opinion,No Opinion,No Opinion,Effective,Effective,No Opinion,Effective,No Opinion,Effective,Effective,No Opinion,Effective,Effective,Effective,Effective,No Opinion,1 to 5,Both Acceptance and Developer TDD,,,,,,,Developers write tests before writing production code,Developers write tests after writing production code,,,,,,"Paper models (cards, ...)",,,,,Word processor/text editor,,,,,"Paper models (cards, ...)",,,,Word processor/text editor
Developer,6 to 10 years,101 to 1000,North America,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,6 to 10 years,"1,001 to 10,000",North America,Software,I have read about it but not tried it,I have experimented with it,No opinion,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Don’t know,"Management wants IT to adopt this practice, but is not providing resources",Don’t know,1% to 20%,Some Impact,Some Impact,Large Impact,Large Impact,No Opinion,,Difficult,It requires a change in thinking and overcoming the view that unit tests mean X% less features.,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Very Effective,Effective,Effective,Effective,Effective,Very Effective,Very Effective,Very Effective,1 to 5,None,End of lifecycle testing by independent QA/Test Team,,,,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,Testers write tests after developers write production code,Customer/acceptance tests,,"Diagrams in drawing tools (e.g. Visio, PowerPoint)",,,,,Whiteboard sketches,,Word processor/text editor,,,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",,,,Whiteboard sketches,,Word processor/text editor
IT Management,11 to 20 years,101 to 1000,North America,Software,I have read about it but not tried it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,,Don’t know,"Management wants IT to adopt this practice, but is not providing resources",1% to 20%,61% to 80%,Some Impact,Some Impact,Large Impact,Some Impact,Neutral,,Neutral,,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Very Effective,Effective,Effective,Neutral,Neutral,Neutral,Neutral,Very Effective,6 to 10,Just Developer TDD,End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,Developer regression testing,Independent regression testing,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,Testers write tests after developers write production code,Customer/acceptance tests,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,,,Word processor/text editor,"Defect management tool (e.g. Bugzilla, ChangeQuest)",Developer tests,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",,,,,,
Developer,11 to 20 years,11 to 100,North America,Software,I have experimented with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,,,,Improved chance of keeping specifications in sync with the code,"Management wants IT to adopt this practice, but is not providing resources","Management wants IT to adopt this practice, but is not providing resources",1% to 20%,1% to 20%,Some Impact,Some Impact,Large Impact,Large Impact,No Opinion,"We develop distributed systems software, so acceptance testing scenarios can be quite complex; not having acceptance testing in place before the system was developed means that it is much harder than it otherwise could have been, because of seemingly unimportant design/architectural decisions. This in turn acts as an obstacle to introducing effective acceptance testing now.",Neutral,"The practices are easy, IMO (though language choice and support tools are importan). More difficult is rigorously following them; what makes this worse is legacy-code.",No Opinion,No Opinion,Effective,Effective,Effective,Effective,Effective,Effective,No Opinion,No Opinion,Effective,Effective,Effective,Effective,Effective,Effective,21 to 50,Don’t know,,Parallel testing by independent test team throughout the lifecycle,Developer regression testing,,,,Developers write tests before writing production code,Developers write tests after writing production code,Testers write tests after developers write production code,Customer/acceptance tests,,,,,"Requirements management tool (e.g. Doors, ReqPro)",,,,,,Developer tests,,,"Paper models (cards, ...)",,Whiteboard sketches,Wiki,
Quality Assurance/Tester,11 to 20 years,"10,001 to 100,000",North America,Software,I have read about it but not tried it,I have read about it but not tried it,Has some potential for quality improvement,Has some potential for quality improvement,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,21+ years,1 to 10,North America,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,Over 80%,Over 80%,No Impact,No Impact,No Impact,No Impact,Difficult,"Design skills are one bottleneck, a culture of ""quality is QAs problem"" is the other.",Difficult,,Very Effective,Effective,Effective,Effective,Neutral,Effective,Effective,Very Effective,Very Effective,Effective,Effective,Effective,Neutral,Effective,Effective,Very Effective,1 to 5,Both Acceptance and Developer TDD,,,,Independent regression testing,Reviews/inspections of work products,Analysts write tests before developers write production code,Developers write tests before writing production code,,,Customer/acceptance tests,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,,,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",Developer tests,,,,,,,
Developer,11 to 20 years,1 to 10,North America,Manufacturing,I have read about it but not tried it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,,,,,,Increased ability of developers to safely change software,,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Don’t know,Don’t know,0%,21% to 40%,Large Impact,Large Impact,No Impact,Don't Know,No Opinion,,Very Difficult,Must unlearn coding practices that have been in use for a long time.,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Very Effective,Neutral,Neutral,Effective,Effective,Effective,Effective,Very Effective,1 to 5,Just Developer TDD,,,Developer regression testing,,,,Developers write tests before writing production code,Developers write tests after writing production code,,,,,,,,,Whiteboard sketches,,,,Developer tests,,,,,Whiteboard sketches,,
IT Management,6 to 10 years,101 to 1000,North America,Financial,I have read about it but not tried it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Don’t know,Management is willing to fund training and education for this practice,0%,41% to 60%,Large Impact,Large Impact,No Impact,Large Impact,Difficult,,Neutral,,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Effective,Effective,Effective,Effective,No Opinion,1 to 5,Just Developer TDD,,,,,,,,Developers write tests after writing production code,,,"Defect management tool (e.g. Bugzilla, ChangeQuest)","Diagrams in drawing tools (e.g. Visio, PowerPoint)",,,,,Whiteboard sketches,,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",Developer tests,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",,,,Whiteboard sketches,,
Developer,Less than 2 years,1 to 10,Europe,IT Services,I have experimented with it,I have experimented with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,,,,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,"Management wants IT to adopt this practice, but is not providing resources","Management wants IT to adopt this practice, but is not providing resources",1% to 20%,1% to 20%,Large Impact,Large Impact,Large Impact,No Impact,Neutral,,Neutral,,No Opinion,Effective,No Opinion,No Opinion,No Opinion,No Opinion,Effective,No Opinion,No Opinion,No Opinion,No Opinion,Effective,Neutral,Neutral,Effective,No Opinion,1 to 5,Just Developer TDD,,,Developer regression testing,Independent regression testing,,,Developers write tests before writing production code,Developers write tests after writing production code,,,"Defect management tool (e.g. Bugzilla, ChangeQuest)","Diagrams in drawing tools (e.g. Visio, PowerPoint)",,,,,Whiteboard sketches,,Word processor/text editor,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",,,,Whiteboard sketches,,Word processor/text editor
Other,21+ years,1 to 10,North America,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,11 to 20 years,"Over 100,000",North America,Software,I have read about it but not tried it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,"Management wants IT to adopt this practice, but is not providing resources",Management is willing to fund training and education for this practice,1% to 20%,21% to 40%,Some Impact,Large Impact,Large Impact,Some Impact,Difficult,,Difficult,"BTW the problem isn't so much a lack of training as the followup. Once people have learned the basics they need support: mentors, pair partners, coding dojos, etc.",Very Effective,Effective,Effective,Effective,Effective,Effective,Ineffective,Very Effective,Very Effective,Effective,Effective,Effective,Effective,Effective,Ineffective,Very Effective,6 to 10,Regression Testing (non-TDD),End of lifecycle testing by independent QA/Test Team,,Developer regression testing,,,,,Developers write tests after writing production code,Testers write tests after developers write production code,,,,,,,,,,Word processor/text editor,,Developer tests,,,,,,,
Developer,11 to 20 years,"10,001 to 100,000",Europe,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,,,,,Increased quality,Increased ability of developers to safely change software,,,,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,21% to 40%,1% to 20%,Some Impact,Large Impact,Large Impact,Some Impact,Difficult,,Easy,,Very Effective,Effective,Effective,Effective,Effective,Effective,Neutral,Effective,Very Effective,Effective,Effective,Very Effective,Effective,Effective,Effective,Very Effective,6 to 10,Just Acceptance TDD,End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,,Independent regression testing,,Analysts write tests before developers write production code,Developers write tests before writing production code,,,Customer/acceptance tests,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,,,Word processor/text editor,,,,,,,,,Word processor/text editor
Quality Assurance/Tester,6 to 10 years,101 to 1000,South & Central America,Government,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,11 to 20 years,101 to 1000,North America,Software,I have experimented with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,Improved chance of keeping specifications in sync with the code,Don’t know,Management is willing to fund training and education for this practice,Don’t know,61% to 80%,Some Impact,Some Impact,Large Impact,Some Impact,No Opinion,,Neutral,,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Very Effective,Neutral,Effective,Effective,Neutral,Neutral,Ineffective,Very Effective,11 to 20,Just Developer TDD,End of lifecycle testing by independent QA/Test Team,,Developer regression testing,Independent regression testing,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,Digital snapshots of whiteboard sketches,,,"Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",Whiteboard sketches,Wiki,Word processor/text editor,,Developer tests,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",Digital snapshots of whiteboard sketches,,"Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",Whiteboard sketches,Wiki,Word processor/text editor
Project Manager,11 to 20 years,1 to 10,North America,Software,I have read about it but not tried it,I am experienced with it,Has little to offer,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Don’t know,Management is willing to fund training and education for this practice,0%,Over 80%,No Impact,No Impact,Some Impact,Some Impact,No Opinion,,Difficult,,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Very Effective,Effective,Effective,Neutral,Neutral,Neutral,Effective,Very Effective,1 to 5,None,,,,,,,Developers write tests before writing production code,Developers write tests after writing production code,,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,,,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,,,
Developer,2 to 5 years,101 to 1000,Europe,Software,I have read about it but not tried it,I have read about it but not tried it,Has some potential for quality improvement,Has some potential for quality improvement,,,,,,,,,,,,,Don’t know,Don’t know,Don’t know,Don’t know,No Impact,No Impact,No Impact,Some Impact,Neutral,,Neutral,,Very Effective,Effective,Effective,Neutral,Neutral,Ineffective,Neutral,Neutral,Very Effective,Effective,Effective,Neutral,Neutral,Ineffective,Neutral,Neutral,1 to 5,None,,,,,Reviews/inspections of work products,,,Developers write tests after writing production code,,Customer/acceptance tests,,,,"Paper models (cards, ...)",,"Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",,,Word processor/text editor,,,,,"Paper models (cards, ...)",,,,
Developer,6 to 10 years,"10,001 to 100,000",North America,Software,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,2 to 5 years,"1,001 to 10,000",Asia,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,Improved chance of keeping specifications in sync with the code,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,11 to 20 years,11 to 100,Europe,Software,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,Less than 2 years,"1,001 to 10,000",Europe,Other,I have read about it but not tried it,I have experimented with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Don’t know,"Management wants IT to adopt this practice, but is not providing resources",Don’t know,41% to 60%,Large Impact,Large Impact,Large Impact,Large Impact,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,6 to 10 years,11 to 100,Asia,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,Over 80%,Over 80%,Some Impact,Large Impact,Large Impact,No Impact,Difficult,,Very Difficult,During my work Ive expereinced numerous companies which claimed that one of the main obstacles for adopting TDD methodologies were the need to handle legacy systems.,Very Effective,Neutral,Effective,Effective,Neutral,Neutral,Neutral,Very Effective,Very Effective,Neutral,Effective,Effective,Neutral,Neutral,Effective,Very Effective,6 to 10,Both Acceptance and Developer TDD,,,Developer regression testing,,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,,Customer/acceptance tests,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,Whiteboard sketches,,,,Developer tests,,,,,,,
Developer,11 to 20 years,101 to 1000,Europe,Financial,I have read about it but not tried it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Don’t know,Management is willing to fund training and education for this practice,Don’t know,1% to 20%,Large Impact,No Impact,No Impact,Large Impact,Neutral,,Neutral,It's not the ease of learning its the realising it's a good idea in the first place.,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Neutral,Neutral,Neutral,Ineffective,Effective,No Opinion,Neutral,Very Effective,11 to 20,Regression Testing (non-TDD),,Parallel testing by independent test team throughout the lifecycle,,,,,,Developers write tests after writing production code,Testers write tests after developers write production code,,,,,,,"Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",,,Word processor/text editor,,Developer tests,,,,"Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",,Wiki,
Developer,6 to 10 years,11 to 100,Africa,Financial,I have experimented with it,I am experienced with it,No opinion,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,Don’t know,Over 80%,Some Impact,No Impact,No Impact,Large Impact,No Opinion,,Difficult,Senior developers with entrenched thinking patterns have a very hard time thinking incrementally.,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Very Effective,No Opinion,No Opinion,Effective,Effective,No Opinion,Ineffective,Very Effective,1 to 5,Just Developer TDD,,Parallel testing by independent test team throughout the lifecycle,,,,,Developers write tests before writing production code,,Testers write tests after developers write production code,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,"Paper models (cards, ...)",,,Whiteboard sketches,,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,"Paper models (cards, ...)",,,,
Developer,21+ years,1 to 10,Europe,Manufacturing,I have experimented with it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,,,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Don’t know,Management is actively against this practice,Don’t know,Don’t know,No Impact,Large Impact,No Impact,Large Impact,No Opinion,,Easy,"It's an attitude / cultural problem, not a technical problem.",No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Effective,Very Effective,Effective,Very Effective,Very Effective,Very Effective,No Opinion,1 to 5,None,,,Developer regression testing,,Reviews/inspections of work products,,,,,,,,Digital snapshots of whiteboard sketches,,,,Whiteboard sketches,,Word processor/text editor,,,,Digital snapshots of whiteboard sketches,"Paper models (cards, ...)",,Whiteboard sketches,,
Developer,21+ years,11 to 100,Europe,Software,I have read about it but not tried it,I have experimented with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Don’t know,Management is actively against this practice,0%,1% to 20%,Large Impact,Large Impact,Large Impact,Some Impact,No Opinion,,Difficult,"The thought required, and changes to ways of thinking, make tdd seem to add to development time",No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Effective,Effective,Effective,Effective,Effective,Effective,Effective,Effective,11 to 20,Just Developer TDD,End of lifecycle testing by independent QA/Test Team,,,Independent regression testing,Reviews/inspections of work products,,Developers write tests before writing production code,,,Customer/acceptance tests,,,,,,,,,,,,,,,,,,Word processor/text editor
Developer,21+ years,"10,001 to 100,000",Europe,Software,I have experimented with it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,Increased ability of developers to safely change software,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,Improved chance of keeping specifications in sync with the code,Don’t know,"Management wants IT to adopt this practice, but is not providing resources",Don’t know,1% to 20%,Large Impact,Large Impact,Some Impact,Some Impact,No Opinion,,Difficult,"It takes a mind shift to even think about trying it - then it takes good design experience to see that it is worthwhile, otherwise the practise is discarded as being 'more work'",Effective,Neutral,Effective,No Opinion,No Opinion,No Opinion,No Opinion,Effective,Effective,Effective,Neutral,Neutral,Neutral,Neutral,Neutral,Effective,11 to 20,Regression Testing (non-TDD),,Parallel testing by independent test team throughout the lifecycle,Developer regression testing,,,,,Developers write tests after writing production code,Testers write tests after developers write production code,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,,,Word processor/text editor,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",,,,Whiteboard sketches,Wiki,Word processor/text editor
Developer,11 to 20 years,101 to 1000,North America,IT Services,I have experimented with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,Increased ability of developers to safely change software,,,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,61% to 80%,61% to 80%,Some Impact,Some Impact,Large Impact,Some Impact,Neutral,,Easy,,Very Effective,Effective,Neutral,Ineffective,Ineffective,No Opinion,Effective,Very Effective,Very Effective,Effective,Neutral,Ineffective,Ineffective,No Opinion,Effective,Very Effective,1 to 5,Both Acceptance and Developer TDD,,,,,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,,,,,,,,,,,Word processor/text editor,,Developer tests,,,,,Whiteboard sketches,,Word processor/text editor
Developer,2 to 5 years,101 to 1000,North America,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,61% to 80%,Over 80%,Some Impact,Some Impact,Large Impact,No Impact,Neutral,,Neutral,,Neutral,Very Effective,Effective,Effective,Effective,Effective,Effective,Effective,Neutral,Very Effective,Effective,Effective,Effective,Effective,Effective,Effective,1 to 5,Both Acceptance and Developer TDD,End of lifecycle testing by independent QA/Test Team,,,,,Analysts write tests before developers write production code,Developers write tests before writing production code,,Testers write tests after developers write production code,Customer/acceptance tests,,,,,,,,,Word processor/text editor,,Developer tests,,,,,Whiteboard sketches,,
Other,11 to 20 years,101 to 1000,North America,Other,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,Over 80%,Over 80%,Some Impact,No Impact,Some Impact,No Impact,Neutral,,Neutral,,Very Effective,Very Effective,Very Effective,Very Effective,Very Effective,Very Effective,Very Effective,Very Effective,Very Effective,Very Effective,Very Effective,Very Effective,Very Effective,Very Effective,Very Effective,Very Effective,6 to 10,Both Acceptance and Developer TDD,,Parallel testing by independent test team throughout the lifecycle,,,,Analysts write tests before developers write production code,Developers write tests before writing production code,Developers write tests after writing production code,,Customer/acceptance tests,,,,,"Requirements management tool (e.g. Doors, ReqPro)",,,,,,,,,,,,,
Developer,6 to 10 years,101 to 1000,South & Central America,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,,Increased quality,Increased ability of developers to safely change software,,,,,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,Over 80%,Over 80%,Large Impact,Some Impact,Some Impact,Don't Know,Neutral,,Very Difficult,,Very Effective,Neutral,Neutral,Neutral,Neutral,Effective,Effective,Very Effective,Very Effective,Effective,Effective,Neutral,Neutral,Effective,Effective,Very Effective,51 to 100,Both Acceptance and Developer TDD,,Parallel testing by independent test team throughout the lifecycle,,,,Analysts write tests before developers write production code,Developers write tests before writing production code,,,Customer/acceptance tests,,,,"Paper models (cards, ...)",,,,Wiki,,,Developer tests,,,"Paper models (cards, ...)",,,Wiki,
Developer,6 to 10 years,101 to 1000,South & Central America,Other,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,61% to 80%,Over 80%,Large Impact,Some Impact,Large Impact,Some Impact,Easy,,Very Difficult,,Effective,Neutral,Effective,Effective,Neutral,Effective,Very Effective,Very Effective,Very Effective,Effective,Very Effective,Neutral,Effective,Effective,Effective,Very Effective,51 to 100,Both Acceptance and Developer TDD,,Parallel testing by independent test team throughout the lifecycle,Developer regression testing,,,Analysts write tests before developers write production code,Developers write tests before writing production code,,,Customer/acceptance tests,,,,"Paper models (cards, ...)",,,Whiteboard sketches,,,,Developer tests,,,"Paper models (cards, ...)",,Whiteboard sketches,,
Developer,11 to 20 years,11 to 100,Europe,Software,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,11 to 20 years,"1,001 to 10,000",South & Central America,Government,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,Improved chance of keeping specifications in sync with the code,"Management wants IT to adopt this practice, but is not providing resources","Management wants IT to adopt this practice, but is not providing resources",1% to 20%,1% to 20%,Large Impact,Large Impact,Some Impact,Some Impact,Neutral,,Difficult,,Very Effective,Very Effective,Effective,Effective,Effective,Effective,Neutral,Effective,Very Effective,Very Effective,Effective,Effective,Effective,Effective,Neutral,Effective,1 to 5,Both Acceptance and Developer TDD,,,Developer regression testing,,,Analysts write tests before developers write production code,Developers write tests before writing production code,,,Customer/acceptance tests,,,,,,,Whiteboard sketches,,Word processor/text editor,,Developer tests,,,,,Whiteboard sketches,,Word processor/text editor
Project Manager,6 to 10 years,11 to 100,South & Central America,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,61% to 80%,61% to 80%,Large Impact,Some Impact,Some Impact,Some Impact,Easy,,Very Difficult,,Very Effective,Effective,Effective,Effective,Effective,Effective,Neutral,Very Effective,Very Effective,Effective,Effective,Neutral,Neutral,Effective,Very Effective,Very Effective,6 to 10,Both Acceptance and Developer TDD,,,,,,Analysts write tests before developers write production code,Developers write tests before writing production code,,,Customer/acceptance tests,,,,"Paper models (cards, ...)",,,,,,,Developer tests,,,"Paper models (cards, ...)",,,,
Developer,2 to 5 years,101 to 1000,South & Central America,Government,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,Over 80%,Over 80%,Large Impact,Some Impact,Large Impact,Don't Know,Easy,,Very Difficult,,Effective,Neutral,Very Effective,Effective,Effective,Effective,Effective,Effective,Very Effective,Neutral,Effective,Effective,Effective,Effective,Very Effective,Very Effective,11 to 20,Both Acceptance and Developer TDD,,Parallel testing by independent test team throughout the lifecycle,,,,Analysts write tests before developers write production code,Developers write tests before writing production code,,,Customer/acceptance tests,,,Digital snapshots of whiteboard sketches,"Paper models (cards, ...)",,,Whiteboard sketches,Wiki,,,,,Digital snapshots of whiteboard sketches,"Paper models (cards, ...)",,Whiteboard sketches,Wiki,
Developer,2 to 5 years,"1,001 to 10,000",Asia,Software,I have read about it but not tried it,I have read about it but not tried it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,,,,,,,,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,2 to 5 years,"1,001 to 10,000",Asia,IT Services,I haven’t heard about it before now,I am experienced with it,No opinion,Has the potential for significant quality improvement,,,,,Increased amount of specification,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Don’t know,"Management wants IT to adopt this practice, but is not providing resources",1% to 20%,21% to 40%,Large Impact,Some Impact,Large Impact,Large Impact,Neutral,,Difficult,,Effective,Effective,Neutral,Ineffective,Neutral,Ineffective,Very Effective,Effective,Very Effective,Effective,Neutral,Ineffective,Ineffective,Ineffective,Effective,Effective,11 to 20,Just Developer TDD,End of lifecycle testing by independent QA/Test Team,,,,Reviews/inspections of work products,,,Developers write tests after writing production code,,Customer/acceptance tests,,,,,,,,,Word processor/text editor,,,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",Digital snapshots of whiteboard sketches,,,Whiteboard sketches,,
Developer,11 to 20 years,1 to 10,Australia & New Zealand,Software,I am experienced with it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,"Management wants IT to adopt this practice, but is not providing resources","Management wants IT to adopt this practice, but is not providing resources",1% to 20%,1% to 20%,Large Impact,Some Impact,Large Impact,No Impact,Neutral,,Difficult,Takes skill and experience to do it well over the long term,Very Effective,Ineffective,No Opinion,Effective,Effective,No Opinion,Effective,Very Effective,Very Effective,Ineffective,No Opinion,Effective,Effective,No Opinion,Effective,Very Effective,6 to 10,Both Acceptance and Developer TDD,,,,,,,Developers write tests before writing production code,Developers write tests after writing production code,,,,,,,,,,Wiki,Word processor/text editor,,,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",,,,,Wiki,Word processor/text editor
Developer,21+ years,101 to 1000,Europe,Software,I have read about it but not tried it,I have experimented with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,,,,,,Increased ability of developers to safely change software,,,,,Don’t know,Management is willing to fund training and education for this practice,Don’t know,Don’t know,Some Impact,Some Impact,Large Impact,Large Impact,No Opinion,,Neutral,,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,1 to 5,Regression Testing (non-TDD),End of lifecycle testing by independent QA/Test Team,,Developer regression testing,,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,,,,,,,,,,,Word processor/text editor,,,,,,,,,
IT Management,11 to 20 years,"1,001 to 10,000",Europe,Software,I have read about it but not tried it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Don’t know,"Management wants IT to adopt this practice, but is not providing resources",0%,1% to 20%,Large Impact,Some Impact,Some Impact,Large Impact,Easy,,Easy,,Very Effective,Neutral,Effective,Effective,Effective,Ineffective,Effective,Very Effective,Very Effective,Neutral,Effective,Effective,Effective,Ineffective,Effective,Very Effective,6 to 10,Just Developer TDD,End of lifecycle testing by independent QA/Test Team,,,,Reviews/inspections of work products,,Developers write tests before writing production code,,,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,Digital snapshots of whiteboard sketches,,,,,,Word processor/text editor,,,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",Digital snapshots of whiteboard sketches,,,,Wiki,Word processor/text editor
Developer,2 to 5 years,101 to 1000,Europe,Manufacturing,I have read about it but not tried it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,,,,Improved chance of keeping specifications in sync with the code,Don’t know,"Management wants IT to adopt this practice, but is not providing resources",0%,1% to 20%,Some Impact,Large Impact,Large Impact,Large Impact,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,21+ years,"10,001 to 100,000",North America,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,1% to 20%,1% to 20%,Some Impact,Some Impact,Large Impact,Large Impact,Very Easy,,Very Easy,"I think about the second or third unit test I wrote I was completely sold on the idea, and I haven't looked back since.",Very Effective,Ineffective,Effective,Effective,Neutral,Neutral,Neutral,Effective,Very Effective,Ineffective,Effective,Neutral,Neutral,Ineffective,Neutral,Effective,11 to 20,Both Acceptance and Developer TDD,,,Developer regression testing,,,,Developers write tests before writing production code,,,Customer/acceptance tests,,,,"Paper models (cards, ...)",,,,,,,Developer tests,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",Digital snapshots of whiteboard sketches,"Paper models (cards, ...)",,,,
Developer,2 to 5 years,11 to 100,South & Central America,Software,I have read about it but not tried it,I have experimented with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,,Improved specification accuracy,,,Don’t know,"Management wants IT to adopt this practice, but is not providing resources",1% to 20%,21% to 40%,Some Impact,Large Impact,Large Impact,Some Impact,Neutral,,Neutral,,Very Effective,Effective,Neutral,Neutral,Ineffective,Ineffective,Ineffective,No Opinion,Very Effective,Effective,Neutral,Neutral,Ineffective,Ineffective,Ineffective,No Opinion,6 to 10,Just Developer TDD,End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,Developer regression testing,,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,Testers write tests after developers write production code,,"Defect management tool (e.g. Bugzilla, ChangeQuest)","Diagrams in drawing tools (e.g. Visio, PowerPoint)",,,,,,,Word processor/text editor,,,,,,,,,Word processor/text editor
Developer,21+ years,11 to 100,North America,Government,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,,,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,"Management wants IT to adopt this practice, but is not providing resources",Management is willing to fund training and education for this practice,41% to 60%,61% to 80%,Some Impact,Large Impact,Some Impact,No Impact,Easy,"Seems quite natural to people doing use cases, as it's like what they've been doing, but a bit more precise.  There are technological, architectural and organizational issues to getting end-to-end acceptance tests running; lack of tools is an issue; control of the stored data is also often an issue.",Difficult,Easy to learn.  Difficult to do well.  Difficult to get developers past the hump where they'll start to believe that it can actually work.  Difficult to get through the technological and application architecture issues that make TDD difficult.,Very Effective,Neutral,Very Effective,Effective,Effective,Neutral,Effective,Very Effective,Very Effective,Effective,Very Effective,Effective,Neutral,Effective,Effective,Very Effective,6 to 10,Just Developer TDD,,Parallel testing by independent test team throughout the lifecycle,Developer regression testing,Independent regression testing,,,Developers write tests before writing production code,Developers write tests after writing production code,Testers write tests after developers write production code,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,,,Word processor/text editor,,,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",Digital snapshots of whiteboard sketches,,,Whiteboard sketches,,
Project Manager,21+ years,"1,001 to 10,000",Asia,Retail,I have read about it but not tried it,I have read about it but not tried it,Has some potential for quality improvement,Has some potential for quality improvement,,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,41% to 60%,21% to 40%,Some Impact,Large Impact,No Impact,Large Impact,Neutral,,Neutral,,Very Effective,Ineffective,Very Effective,Neutral,Neutral,Neutral,Ineffective,Effective,Very Effective,Effective,Very Effective,Neutral,Neutral,Neutral,Ineffective,Effective,51 to 100,Both Acceptance and Developer TDD,,,,,Reviews/inspections of work products,,Developers write tests before writing production code,,,,,"Diagrams in drawing tools (e.g. Visio, PowerPoint)",,,"Requirements management tool (e.g. Doors, ReqPro)","Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",,Wiki,Word processor/text editor,,Developer tests,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",,,"Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",,Wiki,Word processor/text editor
Developer,11 to 20 years,11 to 100,North America,Financial,I have read about it but not tried it,I have experimented with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,,,,,Management is actively against this practice,Management is actively against this practice,0%,0%,Large Impact,Large Impact,Large Impact,Large Impact,Easy,,Easy,,No Opinion,No Opinion,No Opinion,Neutral,Neutral,Neutral,Neutral,No Opinion,No Opinion,Ineffective,No Opinion,Neutral,Neutral,Neutral,Neutral,No Opinion,6 to 10,Regression Testing (non-TDD),End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,,,,,,,Testers write tests after developers write production code,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,"Requirements management tool (e.g. Doors, ReqPro)",,,,Word processor/text editor,,,,,,,,,Word processor/text editor
Developer,Less than 2 years,1 to 10,South & Central America,Software,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Project Manager,11 to 20 years,11 to 100,North America,Software,I have experimented with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,,Improved specification accuracy,Increased amount of specification,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Don’t know,"Management wants IT to adopt this practice, but is not providing resources",1% to 20%,1% to 20%,Some Impact,Some Impact,Some Impact,Some Impact,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,11 to 20 years,101 to 1000,North America,Other,I am experienced with it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,Increased ability of developers to safely change software,,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,61% to 80%,Over 80%,Some Impact,No Impact,Some Impact,No Impact,Difficult,,Difficult,,Very Effective,Ineffective,Effective,Neutral,Neutral,Effective,Effective,Effective,Very Effective,Ineffective,Effective,Neutral,Neutral,Neutral,Effective,Neutral,1 to 5,Both Acceptance and Developer TDD,End of lifecycle testing by independent QA/Test Team,,Developer regression testing,,,,Developers write tests before writing production code,Developers write tests after writing production code,,Customer/acceptance tests,,,,,,,,,,,,,,,,Whiteboard sketches,,
Other,6 to 10 years,"Over 100,000",South & Central America,Software,I have read about it but not tried it,I am experienced with it,Has little to offer,Has the potential for significant quality improvement,,,,Improved specification accuracy,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Don’t know,Management is willing to fund training and education for this practice,Don’t know,41% to 60%,Large Impact,Some Impact,Some Impact,Large Impact,No Opinion,,Difficult,"Test First is very difficult at the begining, but after a month Developers start loving it.  Dependency Management is the hardest part with Legacy Code mainly.",No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Very Effective,No Opinion,Effective,Very Effective,Neutral,Ineffective,Effective,Very Effective,21 to 50,Just Developer TDD,End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,,Independent regression testing,Reviews/inspections of work products,Analysts write tests before developers write production code,,,Testers write tests after developers write production code,Customer/acceptance tests,"Defect management tool (e.g. Bugzilla, ChangeQuest)","Diagrams in drawing tools (e.g. Visio, PowerPoint)",Digital snapshots of whiteboard sketches,"Paper models (cards, ...)","Requirements management tool (e.g. Doors, ReqPro)","Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",Whiteboard sketches,Wiki,Word processor/text editor,,,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",,,"Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",,Wiki,
Developer,2 to 5 years,101 to 1000,North America,Other,I have experimented with it,I have experimented with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,61% to 80%,61% to 80%,No Impact,Some Impact,Some Impact,No Impact,Neutral,,Neutral,,Effective,Effective,Neutral,Neutral,Neutral,Neutral,Neutral,Neutral,Effective,Effective,Neutral,Neutral,Neutral,Neutral,Neutral,Neutral,6 to 10,Both Acceptance and Developer TDD,End of lifecycle testing by independent QA/Test Team,,,,,,Developers write tests before writing production code,,,Customer/acceptance tests,,,,,,,Whiteboard sketches,Wiki,,,Developer tests,,,,,Whiteboard sketches,Wiki,
Developer,2 to 5 years,101 to 1000,North America,Retail,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Management is willing to fund training and education for this practice,Management is actively against this practice,41% to 60%,Over 80%,No Impact,No Impact,No Impact,Some Impact,Very Easy,,Neutral,,Very Effective,Effective,Effective,Neutral,Neutral,Neutral,Effective,Effective,Very Effective,Effective,Effective,Neutral,Neutral,Neutral,Effective,Effective,6 to 10,Both Acceptance and Developer TDD,,,Developer regression testing,,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,,Customer/acceptance tests,,,,"Paper models (cards, ...)","Requirements management tool (e.g. Doors, ReqPro)",,,,,,Developer tests,,,,,Whiteboard sketches,,
Developer,6 to 10 years,1 to 10,Asia,Software,I have experimented with it,I have experimented with it,Has the potential for significant quality improvement,Has some potential for quality improvement,,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Don’t know,Don’t know,0%,0%,Some Impact,No Impact,No Impact,No Impact,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,11 to 20 years,101 to 1000,North America,Other,I am experienced with it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,,,,,Don’t know,"Management wants IT to adopt this practice, but is not providing resources",0%,1% to 20%,Large Impact,Some Impact,No Impact,Large Impact,Difficult,The tools suck,Difficult,,No Opinion,No Opinion,No Opinion,Effective,No Opinion,No Opinion,Effective,Effective,Effective,No Opinion,No Opinion,Ineffective,Ineffective,No Opinion,Neutral,Effective,1 to 5,Regression Testing (non-TDD),End of lifecycle testing by independent QA/Test Team,,,,Reviews/inspections of work products,,,,Testers write tests after developers write production code,,,"Diagrams in drawing tools (e.g. Visio, PowerPoint)",,,,,,,Word processor/text editor,,,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",,,,Whiteboard sketches,,
Developer,11 to 20 years,101 to 1000,North America,Software,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,6 to 10 years,11 to 100,North America,Retail,I have experimented with it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Management is actively against this practice,"Management wants IT to adopt this practice, but is not providing resources",0%,0%,Large Impact,Large Impact,Large Impact,Large Impact,Very Difficult,,Very Difficult,,Very Effective,Effective,Effective,Effective,Effective,Effective,Effective,Very Effective,Very Effective,Effective,Effective,Effective,Effective,Effective,Effective,Very Effective,11 to 20,None,End of lifecycle testing by independent QA/Test Team,,,,,,,,,,"Defect management tool (e.g. Bugzilla, ChangeQuest)","Diagrams in drawing tools (e.g. Visio, PowerPoint)",,,,,,,Word processor/text editor,,,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",,,"Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",,,Word processor/text editor
Developer,21+ years,11 to 100,Europe,Other,I have experimented with it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,,,Improved specification accuracy,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,Improved chance of keeping specifications in sync with the code,"Management wants IT to adopt this practice, but is not providing resources",Management is willing to fund training and education for this practice,1% to 20%,Over 80%,Some Impact,Some Impact,Some Impact,No Impact,Difficult,"We have found that it is relatively easy for developers (especially those familiar with Developer TDD) to accept and understand Acceptance TDD, but it seems much harder for professional testers to make the move from after-the-fact planning and testing to building tests and test cases at the story stage, before any code exists.",Difficult,"We have a very strong culture of Developer TDD, which makes learning by osmosis from other team members easy. However, it becomes very difficult to train, mentor and encourage remote and offshore developers to make use of this technique.",Very Effective,Ineffective,No Opinion,Neutral,Ineffective,Effective,Neutral,Very Effective,Very Effective,Neutral,No Opinion,Effective,Neutral,Effective,Effective,Very Effective,6 to 10,Just Developer TDD,End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,,,Reviews/inspections of work products,,Developers write tests before writing production code,,Testers write tests after developers write production code,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,"Paper models (cards, ...)",,,,,Word processor/text editor,,Developer tests,,,,,Whiteboard sketches,Wiki,
Developer,21+ years,1 to 10,North America,Software,I have experimented with it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,Increased quality,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Don’t know,"Management wants IT to adopt this practice, but is not providing resources",0%,21% to 40%,Some Impact,Some Impact,Some Impact,Large Impact,Difficult,,Difficult,,No Opinion,No Opinion,No Opinion,Neutral,Neutral,No Opinion,Ineffective,No Opinion,No Opinion,No Opinion,No Opinion,Neutral,Neutral,No Opinion,Ineffective,No Opinion,1 to 5,Just Developer TDD,,,,,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,,,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,,,
Developer,11 to 20 years,101 to 1000,North America,Other,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,41% to 60%,61% to 80%,No Impact,No Impact,Some Impact,No Impact,Difficult,,Difficult,,Effective,Effective,Neutral,Effective,Effective,Effective,Very Effective,Effective,Effective,Effective,Neutral,Effective,Effective,Effective,Very Effective,Effective,1 to 5,Both Acceptance and Developer TDD,,,Developer regression testing,,Reviews/inspections of work products,,Developers write tests before writing production code,,,Customer/acceptance tests,,,,"Paper models (cards, ...)",,,,,,,Developer tests,,,"Paper models (cards, ...)",,,,
Developer,11 to 20 years,101 to 1000,North America,Other,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,61% to 80%,Over 80%,Large Impact,Some Impact,Large Impact,Some Impact,Difficult,"The concepts aren't complex, but you have to retrain and override years of experience doing without it.  It's very easy for teams to slip back into the old ways of doing things.",Easy,,Very Effective,Neutral,Effective,Effective,Effective,Neutral,Effective,Effective,Very Effective,Ineffective,Effective,Effective,Neutral,Neutral,Neutral,Effective,6 to 10,Both Acceptance and Developer TDD,,,Developer regression testing,Independent regression testing,,,Developers write tests before writing production code,Developers write tests after writing production code,,Customer/acceptance tests,,,,"Paper models (cards, ...)",,,Whiteboard sketches,Wiki,,,Developer tests,,,"Paper models (cards, ...)",,Whiteboard sketches,Wiki,
Developer,6 to 10 years,101 to 1000,Europe,IT Services,I have read about it but not tried it,I have experimented with it,Has some potential for quality improvement,Has some potential for quality improvement,,,,,,,,,,,,,Management is actively against this practice,Management is actively against this practice,0%,0%,Some Impact,Some Impact,Some Impact,Large Impact,Neutral,,Neutral,,Very Effective,Very Effective,Effective,Ineffective,Ineffective,Neutral,Neutral,Effective,Very Effective,Very Effective,Effective,Ineffective,Ineffective,Neutral,Neutral,Effective,21 to 50,None,End of lifecycle testing by independent QA/Test Team,,,,Reviews/inspections of work products,,Developers write tests before writing production code,,,,,,,,,,,,Word processor/text editor,,,,,,,,,Word processor/text editor
Developer,6 to 10 years,1 to 10,Europe,Software,I have read about it but not tried it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,2 to 5 years,"1,001 to 10,000",North America,Retail,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,Less than 2 years,101 to 1000,North America,Retail,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,61% to 80%,Over 80%,Some Impact,Some Impact,Large Impact,Some Impact,Neutral,"It is most difficult learning WHAT to test, instead of how to test.",Neutral,"It makes coding in pairs natural and fun.  The hardest part would include knowing when to mock, and how to test some particularly complex cases",Neutral,Ineffective,Very Effective,Effective,Effective,Neutral,Ineffective,Very Effective,Very Effective,Neutral,Very Effective,Effective,Neutral,Neutral,Neutral,Very Effective,1 to 5,Both Acceptance and Developer TDD,,,,,,,Developers write tests before writing production code,Developers write tests after writing production code,,Customer/acceptance tests,,,,"Paper models (cards, ...)",,,Whiteboard sketches,Wiki,Word processor/text editor,,Developer tests,,,"Paper models (cards, ...)",,Whiteboard sketches,Wiki,Word processor/text editor
Developer,2 to 5 years,11 to 100,North America,Other,I am experienced with it,I am experienced with it,Has little to offer,Has the potential for significant quality improvement,,,,,Increased amount of specification,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,,Management is actively against this practice,Management is willing to fund training and education for this practice,Don’t know,Over 80%,Some Impact,Some Impact,No Impact,No Impact,Difficult,We used the FITnesse architecture and found it to be be very useful for setting up first time specifications but incredibly painful when it came to changing requirements.  The cost of maintaining the tests simply became too much to add any significant value to our processes.  We are currently exploring alternative acceptance testing methods.,Easy,We only had one developer who had difficulty and it was a personal aversion to adopting TDD rather than any difficulty with the tools or the concepts.,Effective,Ineffective,Neutral,Ineffective,Ineffective,Neutral,Neutral,No Opinion,Very Effective,Effective,Neutral,Effective,Effective,Neutral,Neutral,No Opinion,1 to 5,Just Developer TDD,End of lifecycle testing by independent QA/Test Team,,,,Reviews/inspections of work products,,Developers write tests before writing production code,,,,,,,"Paper models (cards, ...)",,,Whiteboard sketches,,,,Developer tests,,Digital snapshots of whiteboard sketches,"Paper models (cards, ...)",,Whiteboard sketches,Wiki,
Developer,6 to 10 years,101 to 1000,North America,Other,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,21+ years,101 to 1000,North America,Other,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,41% to 60%,61% to 80%,Some Impact,No Impact,Some Impact,Large Impact,Easy,,Easy,,Very Effective,Very Ineffective,Effective,Effective,Effective,Effective,Neutral,Very Effective,Very Effective,Very Ineffective,Effective,Effective,Effective,Effective,Ineffective,Very Effective,11 to 20,Both Acceptance and Developer TDD,,,Developer regression testing,Independent regression testing,,Analysts write tests before developers write production code,Developers write tests before writing production code,,,Customer/acceptance tests,,,,,,,,,,,Developer tests,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",,"Paper models (cards, ...)","Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",,,
Developer,11 to 20 years,"Over 100,000",North America,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,41% to 60%,41% to 60%,Large Impact,Some Impact,Some Impact,Some Impact,Neutral,,Neutral,,Very Effective,Very Effective,Effective,Effective,Effective,No Opinion,Effective,Very Effective,Very Effective,Very Effective,Effective,Effective,Effective,No Opinion,Effective,Very Effective,51 to 100,Both Acceptance and Developer TDD,End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,Developer regression testing,,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,Testers write tests after developers write production code,,,,,,,,,,Word processor/text editor,,,,,,,,,Word processor/text editor
IT Management,6 to 10 years,101 to 1000,North America,Software,I have read about it but not tried it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,Improved chance of keeping specifications in sync with the code,Don’t know,Management is willing to fund training and education for this practice,0%,Over 80%,No Impact,No Impact,Some Impact,No Impact,Easy,"I think it would be easy to do, however our hurdle has been getting our customers over the roadblock of actually writing the tests.",Neutral,,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Very Effective,Ineffective,Effective,Neutral,Neutral,Neutral,Ineffective,Very Effective,6 to 10,Just Developer TDD,,,,,,,Developers write tests before writing production code,,,Customer/acceptance tests,,,,,,,,,,,Developer tests,,,,,,,
Developer,2 to 5 years,101 to 1000,North America,Retail,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has some potential for quality improvement,Increased quality,Increased ability of developers to safely change software,,Improved specification accuracy,Increased amount of specification,,Increased quality,Increased ability of developers to safely change software,,,,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,61% to 80%,Over 80%,Some Impact,Some Impact,Large Impact,Some Impact,Neutral,"Once you understand how to interact with the system and write Conditions of Satisfaction into tests, its relatively easy.",Easy,,Very Effective,Very Effective,Effective,No Opinion,No Opinion,No Opinion,No Opinion,Neutral,Effective,Effective,Effective,Ineffective,No Opinion,Effective,No Opinion,Neutral,6 to 10,Both Acceptance and Developer TDD,End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,Developer regression testing,,Reviews/inspections of work products,Analysts write tests before developers write production code,Developers write tests before writing production code,,,Customer/acceptance tests,,,,,"Requirements management tool (e.g. Doors, ReqPro)",,,,,,,,,"Paper models (cards, ...)",,Whiteboard sketches,,
Developer,11 to 20 years,101 to 1000,North America,Other,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,,Don’t know,Don’t know,1% to 20%,21% to 40%,Large Impact,Large Impact,Large Impact,Large Impact,Difficult,,Difficult,,Very Effective,Effective,Neutral,Ineffective,Ineffective,Neutral,Neutral,Very Effective,Very Effective,Effective,Neutral,Ineffective,Ineffective,Neutral,Neutral,Very Effective,1 to 5,Just Developer TDD,,,,,,,Developers write tests before writing production code,,,,,,,"Paper models (cards, ...)",,,,,,,Developer tests,,,"Paper models (cards, ...)",,,,
Developer,11 to 20 years,"10,001 to 100,000",North America,Other,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Don’t know,"Management wants IT to adopt this practice, but is not providing resources",1% to 20%,1% to 20%,Large Impact,Large Impact,Large Impact,Large Impact,Neutral,,Easy,,Very Effective,Very Effective,Effective,Effective,Effective,Neutral,Very Effective,Very Effective,Very Effective,Very Effective,Very Effective,Very Effective,Very Effective,Very Effective,Very Effective,Very Effective,1 to 5,Just Developer TDD,,,Developer regression testing,Independent regression testing,,,Developers write tests before writing production code,,,,,"Diagrams in drawing tools (e.g. Visio, PowerPoint)",,"Paper models (cards, ...)",,,Whiteboard sketches,,Word processor/text editor,,,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",Digital snapshots of whiteboard sketches,,,Whiteboard sketches,Wiki,
Developer,11 to 20 years,1 to 10,North America,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,"Management wants IT to adopt this practice, but is not providing resources","Management wants IT to adopt this practice, but is not providing resources",41% to 60%,41% to 60%,Some Impact,Some Impact,Large Impact,Some Impact,Difficult,Developers personalities play a big factor in their initial steps into TDD as well as their level of adoption.,Difficult,,Very Effective,Ineffective,Effective,Effective,Effective,Neutral,Effective,Very Effective,Very Effective,Ineffective,Effective,Effective,Effective,Neutral,Effective,Very Effective,6 to 10,Both Acceptance and Developer TDD,,,Developer regression testing,,,,Developers write tests before writing production code,,,Customer/acceptance tests,,,,"Paper models (cards, ...)",,,,,,,Developer tests,,,"Paper models (cards, ...)",,Whiteboard sketches,Wiki,
Developer,21+ years,101 to 1000,North America,IT Services,I have experimented with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Management is willing to fund training and education for this practice,"Management wants IT to adopt this practice, but is not providing resources",21% to 40%,21% to 40%,Large Impact,Large Impact,Some Impact,No Impact,Very Easy,"Learning the basic concepts goes well, but adding them to your daily practice takes some work.  It is more difficult to get the team to accept executable specs than it is to get them accustomed to ""development TDD"".",Easy,"Learning the basics is easy, but gaining proficiency is more time-consuming than with some other practices.  I have been doing ""development"" TDD for several years now yet don't consider myself especially good at it.",No Opinion,Effective,Effective,Neutral,Neutral,Effective,Neutral,Effective,Very Effective,Effective,Effective,Effective,Effective,Effective,Neutral,Effective,6 to 10,Just Developer TDD,,Parallel testing by independent test team throughout the lifecycle,Developer regression testing,Independent regression testing,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,Testers write tests after developers write production code,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,"Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",Whiteboard sketches,Wiki,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",Developer tests,,,,,Whiteboard sketches,Wiki,
Developer,6 to 10 years,101 to 1000,North America,IT Services,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,Over 80%,Over 80%,Some Impact,No Impact,Large Impact,Some Impact,Neutral,"The biggest challenge is finding the balance between customer and developer responsibilities when writing tests. Customers frequently don't think of everything that could possibly break, but developers frequently don't think of all the business requirements.",Neutral,Good TDD is easy to learn when pairing with people who practice it. It would be more difficult to learn in an organization that's not doing it.,Very Effective,Neutral,Effective,Effective,Effective,No Opinion,Neutral,Very Effective,Very Effective,Neutral,Effective,Effective,Effective,No Opinion,Neutral,Very Effective,1 to 5,Both Acceptance and Developer TDD,,,,,,,Developers write tests before writing production code,,,Customer/acceptance tests,,"Diagrams in drawing tools (e.g. Visio, PowerPoint)",,"Paper models (cards, ...)",,,Whiteboard sketches,,Word processor/text editor,,,,,,,Whiteboard sketches,Wiki,
Developer,21+ years,"1,001 to 10,000",North America,Other,I have experimented with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,,,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,Improved chance of keeping specifications in sync with the code,Management is actively against this practice,Management is actively against this practice,0%,1% to 20%,Some Impact,Some Impact,Large Impact,Large Impact,Neutral,,Neutral,,No Opinion,No Opinion,No Opinion,Effective,Effective,Effective,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Effective,Effective,Effective,Effective,No Opinion,1 to 5,None,,,Developer regression testing,Independent regression testing,Reviews/inspections of work products,,,,Testers write tests after developers write production code,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,,,Word processor/text editor,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,,,Word processor/text editor
Developer,2 to 5 years,101 to 1000,North America,Retail,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,21% to 40%,Over 80%,Some Impact,No Impact,Large Impact,No Impact,Difficult,"Even a simple scripting language can be unintelligible to customers.  Acceptance TDD needs a QA specialist to bridge the gap, which my company sometimes doesn't have",Easy,,Very Effective,Ineffective,Very Effective,Very Effective,Effective,Effective,Effective,Very Effective,Very Effective,Ineffective,Very Effective,Very Effective,Effective,Effective,Effective,Very Effective,1 to 5,Just Developer TDD,,,Developer regression testing,,,,Developers write tests before writing production code,,,,,,,,"Requirements management tool (e.g. Doors, ReqPro)",,,,,,Developer tests,,,,,Whiteboard sketches,Wiki,
Developer,11 to 20 years,101 to 1000,North America,Other,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,41% to 60%,Over 80%,Some Impact,No Impact,Large Impact,No Impact,Difficult,,Difficult,,Effective,Effective,Effective,Effective,Neutral,Neutral,Neutral,Very Effective,Effective,Effective,Effective,Effective,Neutral,Neutral,Neutral,Very Effective,6 to 10,Both Acceptance and Developer TDD,,,Developer regression testing,,,,Developers write tests before writing production code,,,Customer/acceptance tests,,,,,"Requirements management tool (e.g. Doors, ReqPro)",,,,,,Developer tests,,,,,,,
Developer,11 to 20 years,101 to 1000,North America,IT Services,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Data Professional,21+ years,101 to 1000,North America,Software,I am experienced with it,I am experienced with it,Has some potential for quality improvement,Has some potential for quality improvement,Increased quality,,,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,,Increased ability of developers to safely change software,,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,61% to 80%,Over 80%,No Impact,No Impact,No Impact,Some Impact,Very Difficult,,Very Difficult,TDD often does ***NOT*** take into consoderation personalities!  THIS NEEDS TO BE INCLUDED IN THE TDD CULTURE.  MY EXPERIENCES HAVE SHOWN THAT PERSONALITY CONFLICTS WILL AND DO NEGATE ALL THE POSITIVES OF TDD AND AGILE!  THE FACT THAT MANAGEMENT AND YOU GURUS IGNORE THIS PISSES ME OFF!,Ineffective,Neutral,Neutral,Ineffective,Neutral,Ineffective,Effective,Effective,Ineffective,Neutral,Neutral,Neutral,Neutral,Neutral,Effective,Effective,6 to 10,Don’t know,,,,,Reviews/inspections of work products,Analysts write tests before developers write production code,Developers write tests before writing production code,Developers write tests after writing production code,Testers write tests after developers write production code,Customer/acceptance tests,"Defect management tool (e.g. Bugzilla, ChangeQuest)","Diagrams in drawing tools (e.g. Visio, PowerPoint)",Digital snapshots of whiteboard sketches,"Paper models (cards, ...)","Requirements management tool (e.g. Doors, ReqPro)","Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",Whiteboard sketches,Wiki,Word processor/text editor,"Defect management tool (e.g. Bugzilla, ChangeQuest)",Developer tests,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",Digital snapshots of whiteboard sketches,"Paper models (cards, ...)","Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",Whiteboard sketches,Wiki,Word processor/text editor
Developer,2 to 5 years,101 to 1000,North America,Other,I have experimented with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,Increased ability of developers to safely change software,,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,61% to 80%,Over 80%,Large Impact,Some Impact,Some Impact,Some Impact,Neutral,,Easy,,Very Effective,Very Effective,Neutral,Effective,Effective,No Opinion,No Opinion,Effective,Very Effective,Very Effective,Effective,Effective,Effective,No Opinion,Effective,Effective,1 to 5,Both Acceptance and Developer TDD,,,Developer regression testing,Independent regression testing,,Analysts write tests before developers write production code,Developers write tests before writing production code,,,Customer/acceptance tests,,,,,,,,Wiki,,,Developer tests,,,,,,Wiki,
Quality Assurance/Tester,6 to 10 years,101 to 1000,North America,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,,,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,Over 80%,Over 80%,Large Impact,Large Impact,Large Impact,Large Impact,Easy,,Easy,,Very Effective,Ineffective,Effective,Neutral,Neutral,Neutral,Ineffective,Very Effective,Very Effective,Ineffective,Effective,Neutral,Neutral,Neutral,Ineffective,Very Effective,1 to 5,Both Acceptance and Developer TDD,,,Developer regression testing,,Reviews/inspections of work products,Analysts write tests before developers write production code,Developers write tests before writing production code,,,Customer/acceptance tests,,,,"Paper models (cards, ...)","Requirements management tool (e.g. Doors, ReqPro)",,Whiteboard sketches,Wiki,Word processor/text editor,,Developer tests,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",,,,Whiteboard sketches,Wiki,Word processor/text editor
Developer,2 to 5 years,101 to 1000,South & Central America,Software,I have read about it but not tried it,I have experimented with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,,Improved specification accuracy,Increased amount of specification,,Increased quality,Increased ability of developers to safely change software,,,,,"Management wants IT to adopt this practice, but is not providing resources","Management wants IT to adopt this practice, but is not providing resources",0%,1% to 20%,Large Impact,Large Impact,Large Impact,Large Impact,Difficult,,Difficult,,Ineffective,Ineffective,Effective,Neutral,Neutral,Neutral,Very Effective,Very Effective,Ineffective,Ineffective,Effective,Neutral,Neutral,Neutral,Very Effective,Very Effective,6 to 10,None,End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,,Independent regression testing,,,,Developers write tests after writing production code,Testers write tests after developers write production code,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,"Requirements management tool (e.g. Doors, ReqPro)",,,Wiki,Word processor/text editor,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,,Wiki,
Developer,11 to 20 years,11 to 100,Europe,Software,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,6 to 10 years,11 to 100,Europe,Retail,I have experimented with it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,Increased ability of developers to safely change software,,Improved specification accuracy,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,,"Management wants IT to adopt this practice, but is not providing resources",Management is willing to fund training and education for this practice,1% to 20%,21% to 40%,Some Impact,Large Impact,No Impact,No Impact,Very Difficult,,Difficult,,Very Effective,Neutral,Effective,Neutral,Effective,Effective,Neutral,Effective,Very Effective,Neutral,Effective,Effective,Effective,Effective,Effective,Very Effective,11 to 20,Just Developer TDD,,,Developer regression testing,,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,,,,,,"Paper models (cards, ...)",,,,Wiki,,,Developer tests,,Digital snapshots of whiteboard sketches,,,,Wiki,
Developer,6 to 10 years,"1,001 to 10,000",Europe,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,,,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,1% to 20%,21% to 40%,Some Impact,Some Impact,No Impact,No Impact,Difficult,,Difficult,,Very Effective,Neutral,Effective,Effective,Effective,Neutral,Neutral,Very Effective,Very Effective,Neutral,Effective,Effective,Effective,Neutral,Neutral,Very Effective,11 to 20,Just Developer TDD,,,Developer regression testing,Independent regression testing,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,Testers write tests after developers write production code,Customer/acceptance tests,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,,Wiki,Word processor/text editor,"Defect management tool (e.g. Bugzilla, ChangeQuest)",Developer tests,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",Digital snapshots of whiteboard sketches,,,Whiteboard sketches,Wiki,Word processor/text editor
Developer,21+ years,101 to 1000,Europe,Software,I have read about it but not tried it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Don’t know,Don’t know,Don’t know,Over 80%,Some Impact,No Impact,Some Impact,No Impact,No Opinion,"I haven't 'learned' Acceptance TDD, so I can't express an opinion on how hard/easy it is.",Neutral,"Learning is easy, the associated culture shift from non-TDD development practices is harder.",No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Very Effective,Effective,No Opinion,Effective,Effective,Effective,Neutral,Effective,6 to 10,Just Developer TDD,End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,,,,,Developers write tests before writing production code,,,,,,,,,,Whiteboard sketches,,,,Developer tests,,,,,,,
Developer,11 to 20 years,11 to 100,Asia,Software,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Other,11 to 20 years,1 to 10,Europe,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,Over 80%,Over 80%,Large Impact,Some Impact,Some Impact,Large Impact,Difficult,,Neutral,,Effective,Neutral,Very Effective,Very Effective,Very Effective,Ineffective,Effective,Effective,Effective,Neutral,Very Effective,Very Effective,Very Effective,Neutral,Effective,Effective,6 to 10,Both Acceptance and Developer TDD,End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,Developer regression testing,Independent regression testing,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,Testers write tests after developers write production code,Customer/acceptance tests,"Defect management tool (e.g. Bugzilla, ChangeQuest)","Diagrams in drawing tools (e.g. Visio, PowerPoint)",Digital snapshots of whiteboard sketches,"Paper models (cards, ...)","Requirements management tool (e.g. Doors, ReqPro)",,Whiteboard sketches,Wiki,Word processor/text editor,"Defect management tool (e.g. Bugzilla, ChangeQuest)",Developer tests,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",Digital snapshots of whiteboard sketches,,"Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",Whiteboard sketches,Wiki,Word processor/text editor
Developer,6 to 10 years,101 to 1000,Europe,IT Services,I have read about it but not tried it,I have experimented with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Don’t know,"Management wants IT to adopt this practice, but is not providing resources",0%,1% to 20%,Large Impact,Large Impact,Large Impact,Large Impact,Very Difficult,,Difficult,,Very Effective,Neutral,Effective,Effective,Effective,Neutral,Neutral,Very Effective,Very Effective,Neutral,Effective,Effective,Effective,Effective,Effective,Very Effective,6 to 10,Just Developer TDD,End of lifecycle testing by independent QA/Test Team,,Developer regression testing,,,,Developers write tests before writing production code,Developers write tests after writing production code,,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,"Paper models (cards, ...)",,,,Wiki,,,Developer tests,,,,,,Wiki,
Developer,11 to 20 years,101 to 1000,Europe,Financial,I have experimented with it,I have experimented with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,Increased ability of developers to safely change software,,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Don’t know,"Management wants IT to adopt this practice, but is not providing resources",0%,1% to 20%,Large Impact,Some Impact,Some Impact,Large Impact,Difficult,,Very Difficult,,Very Effective,Effective,Effective,No Opinion,No Opinion,Neutral,Ineffective,Very Effective,Very Effective,Effective,Effective,Neutral,Ineffective,Ineffective,Neutral,Very Effective,6 to 10,Regression Testing (non-TDD),End of lifecycle testing by independent QA/Test Team,,Developer regression testing,Independent regression testing,,,,,Testers write tests after developers write production code,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,,,Word processor/text editor,,Developer tests,,,,"Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",,,Word processor/text editor
Developer,11 to 20 years,11 to 100,Europe,Software,I have read about it but not tried it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,,,,,,,Increased ability of developers to safely change software,,Improved specification accuracy,,,Don’t know,Don’t know,Don’t know,1% to 20%,Some Impact,Large Impact,Some Impact,No Impact,Difficult,,Difficult,,Very Effective,Neutral,Effective,Effective,Effective,Effective,Neutral,No Opinion,Very Effective,Neutral,Effective,Effective,Effective,Effective,Neutral,No Opinion,6 to 10,Regression Testing (non-TDD),,,Developer regression testing,,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,,,,,,"Paper models (cards, ...)",,,,Wiki,,,Developer tests,,Digital snapshots of whiteboard sketches,,,Whiteboard sketches,Wiki,
Developer,6 to 10 years,1 to 10,Europe,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,Over 80%,Over 80%,Large Impact,Some Impact,Large Impact,No Impact,Difficult,,Very Difficult,,Very Effective,Ineffective,Effective,Effective,Effective,Effective,Neutral,Effective,Very Effective,Ineffective,Effective,Effective,Effective,Effective,Neutral,Effective,1 to 5,Both Acceptance and Developer TDD,End of lifecycle testing by independent QA/Test Team,,,,,,Developers write tests before writing production code,,,Customer/acceptance tests,,,,"Paper models (cards, ...)",,,Whiteboard sketches,,,,,,,"Paper models (cards, ...)",,Whiteboard sketches,,Word processor/text editor
Developer,6 to 10 years,"1,001 to 10,000",Europe,Other,I have read about it but not tried it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,,Improved specification accuracy,,,Don’t know,Management is willing to fund training and education for this practice,1% to 20%,21% to 40%,Large Impact,Some Impact,Large Impact,Some Impact,Difficult,"Difficulties range from technical to attitudes (""that's never gonna work!""). It's tricky on a number of levels.",Neutral,"If developers are unwilling to engage, read about developer testing and try to improve their abilities, it's really difficult. If one can just do it, it's not so bad.",No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Effective,Neutral,Neutral,Effective,Effective,Effective,Effective,Effective,6 to 10,Regression Testing (non-TDD),End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,Developer regression testing,,,,Developers write tests before writing production code,Developers write tests after writing production code,Testers write tests after developers write production code,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,"Paper models (cards, ...)",,,,,,,Developer tests,,,,,Whiteboard sketches,,
Project Manager,2 to 5 years,1 to 10,Asia,Software,I have read about it but not tried it,I am experienced with it,Has little to offer,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,,,,,"Management wants IT to adopt this practice, but is not providing resources",Management is willing to fund training and education for this practice,0%,Over 80%,Large Impact,Some Impact,No Impact,No Impact,Difficult,,Neutral,,Very Effective,No Opinion,No Opinion,Effective,No Opinion,No Opinion,No Opinion,Very Effective,Very Effective,No Opinion,Neutral,Effective,Effective,Ineffective,Effective,Very Effective,1 to 5,Just Developer TDD,,,Developer regression testing,,Reviews/inspections of work products,,Developers write tests before writing production code,Developers write tests after writing production code,,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,Whiteboard sketches,,Word processor/text editor,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",,,,Whiteboard sketches,,Word processor/text editor
Developer,2 to 5 years,"Over 100,000",Europe,Other,I have experimented with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,,,,,"Management wants IT to adopt this practice, but is not providing resources","Management wants IT to adopt this practice, but is not providing resources",1% to 20%,1% to 20%,Large Impact,Large Impact,Large Impact,Large Impact,No Opinion,,Easy,"The concepts are relatively easy to grasp, but when you get back to work, thinking up small enough tests to lead you is very difficult indeed.",Very Effective,Neutral,Effective,Neutral,Neutral,Effective,Neutral,Very Effective,Very Effective,Neutral,Effective,Neutral,Neutral,Effective,Neutral,Very Effective,11 to 20,Regression Testing (non-TDD),End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,,,,,,Developers write tests after writing production code,Testers write tests after developers write production code,Customer/acceptance tests,"Defect management tool (e.g. Bugzilla, ChangeQuest)","Diagrams in drawing tools (e.g. Visio, PowerPoint)",,,"Requirements management tool (e.g. Doors, ReqPro)",,,Wiki,Word processor/text editor,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",,,"Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",,,
IT Management,11 to 20 years,101 to 1000,North America,Government,I have experimented with it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,,,Improved specification accuracy,Increased amount of specification,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Don’t know,Management is willing to fund training and education for this practice,Don’t know,Over 80%,Some Impact,Some Impact,Large Impact,Some Impact,Neutral,,Easy,,No Opinion,No Opinion,Effective,No Opinion,No Opinion,No Opinion,No Opinion,Very Effective,Very Effective,Effective,Effective,Effective,Effective,Neutral,Effective,Very Effective,6 to 10,Just Developer TDD,,,,,Reviews/inspections of work products,,Developers write tests before writing production code,,,,,,Digital snapshots of whiteboard sketches,,"Requirements management tool (e.g. Doors, ReqPro)",,Whiteboard sketches,,,,,,Digital snapshots of whiteboard sketches,,,Whiteboard sketches,,
IT Management,21+ years,101 to 1000,North America,Other,I have experimented with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,"Management wants IT to adopt this practice, but is not providing resources","Management wants IT to adopt this practice, but is not providing resources",1% to 20%,1% to 20%,Large Impact,Large Impact,Large Impact,Large Impact,Neutral,It is difficult for business owners to grasp their role in writing acceptance tests.    Waterfall trained QA testers have resisted Acceptance TDD,Easy,"Much easier when developing new code in a new system.    More challenging when enhancing existing code in a Legacy system, (using Legacy defined as code without tests).",No Opinion,No Opinion,Neutral,Neutral,Neutral,Neutral,Neutral,No Opinion,Very Effective,Effective,Effective,Effective,Effective,Effective,Effective,Very Effective,1 to 5,Just Developer TDD,End of lifecycle testing by independent QA/Test Team,,Developer regression testing,,Reviews/inspections of work products,,,Developers write tests after writing production code,Testers write tests after developers write production code,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,Digital snapshots of whiteboard sketches,"Paper models (cards, ...)",,,Whiteboard sketches,Wiki,Word processor/text editor,"Defect management tool (e.g. Bugzilla, ChangeQuest)",Developer tests,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",Digital snapshots of whiteboard sketches,,,Whiteboard sketches,Wiki,Word processor/text editor
Data Professional,21+ years,1 to 10,North America,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,,,,,Increased quality,Increased ability of developers to safely change software,,,,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,Over 80%,Over 80%,Some Impact,Some Impact,Large Impact,Large Impact,Difficult,,Difficult,,Very Effective,Effective,Effective,Effective,Effective,Effective,Very Effective,Very Effective,Very Effective,Effective,Effective,Effective,Effective,Effective,Very Effective,Very Effective,6 to 10,Both Acceptance and Developer TDD,,,Developer regression testing,,,,Developers write tests before writing production code,Developers write tests after writing production code,,Customer/acceptance tests,,,Digital snapshots of whiteboard sketches,,,,Whiteboard sketches,,,,Developer tests,,Digital snapshots of whiteboard sketches,,,Whiteboard sketches,,
Developer,6 to 10 years,101 to 1000,Australia & New Zealand,Other,I have experimented with it,I have experimented with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,,,,Increased amount of specification,,Increased quality,Increased ability of developers to safely change software,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,6 to 10 years,"10,001 to 100,000",North America,Manufacturing,I have experimented with it,I am experienced with it,Has little to offer,Has the potential for significant quality improvement,,,,,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,"Management wants IT to adopt this practice, but is not providing resources",Don’t know,1% to 20%,1% to 20%,Some Impact,Large Impact,Some Impact,Large Impact,Difficult,,Easy,,Very Effective,Effective,Ineffective,Effective,Effective,Neutral,Effective,Effective,Very Effective,Effective,Neutral,Effective,Effective,Effective,Effective,Effective,1 to 5,Both Acceptance and Developer TDD,,,,,Reviews/inspections of work products,Analysts write tests before developers write production code,,Developers write tests after writing production code,Testers write tests after developers write production code,,,,Digital snapshots of whiteboard sketches,,,,Whiteboard sketches,,Word processor/text editor,"Defect management tool (e.g. Bugzilla, ChangeQuest)",Developer tests,"Diagrams in drawing tools (e.g. Visio, Powerpoint)",,"Paper models (cards, ...)",,Whiteboard sketches,Wiki,Word processor/text editor
Operations/Support Staff,2 to 5 years,101 to 1000,South & Central America,Retail,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
IT Management,21+ years,11 to 100,North America,Software,I have experimented with it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,,,Improved specification accuracy,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,"Management wants IT to adopt this practice, but is not providing resources",Management is willing to fund training and education for this practice,1% to 20%,61% to 80%,No Impact,No Impact,Some Impact,Some Impact,Neutral,,Neutral,,Effective,Effective,Neutral,Neutral,Neutral,Neutral,Neutral,Effective,Very Effective,Effective,Effective,Neutral,Effective,Neutral,Effective,Very Effective,6 to 10,Just Developer TDD,,Parallel testing by independent test team throughout the lifecycle,Developer regression testing,,,,Developers write tests before writing production code,Developers write tests after writing production code,,,,"Diagrams in drawing tools (e.g. Visio, PowerPoint)",Digital snapshots of whiteboard sketches,,,,,,Word processor/text editor,"Defect management tool (e.g. Bugzilla, ChangeQuest)",Developer tests,,Digital snapshots of whiteboard sketches,,,,,Word processor/text editor
IT Management,21+ years,101 to 1000,North America,Retail,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,,Improved chance of keeping specifications in sync with the code,Management is willing to fund training and education for this practice,Management is willing to fund training and education for this practice,61% to 80%,61% to 80%,Some Impact,Some Impact,Some Impact,Some Impact,Easy,,Easy,,Effective,Effective,Effective,Effective,Effective,Effective,Effective,Effective,Effective,Effective,Effective,Effective,Effective,Effective,Effective,Effective,6 to 10,Both Acceptance and Developer TDD,End of lifecycle testing by independent QA/Test Team,Parallel testing by independent test team throughout the lifecycle,Developer regression testing,,,,Developers write tests before writing production code,Developers write tests after writing production code,Testers write tests after developers write production code,Customer/acceptance tests,,,,"Paper models (cards, ...)",,,Whiteboard sketches,Wiki,Word processor/text editor,,Developer tests,,,"Paper models (cards, ...)",,Whiteboard sketches,Wiki,Word processor/text editor
Developer,2 to 5 years,1 to 10,Asia,IT Services,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,11 to 20 years,11 to 100,Europe,Software,I have experimented with it,I am experienced with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,,,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,,,,Improved chance of keeping specifications in sync with the code,Don’t know,Don’t know,1% to 20%,1% to 20%,Some Impact,Large Impact,No Impact,Large Impact,Neutral,,Easy,,Effective,Neutral,Neutral,Neutral,Ineffective,Neutral,Neutral,Effective,Very Effective,Effective,Neutral,Effective,Ineffective,Neutral,Neutral,Effective,1 to 5,Regression Testing (non-TDD),,,Developer regression testing,,Reviews/inspections of work products,,,Developers write tests after writing production code,,,,,,"Paper models (cards, ...)",,,,Wiki,,,,,,"Paper models (cards, ...)",,,Wiki,
Other,21+ years,"1,001 to 10,000",North America,Manufacturing,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
Developer,11 to 20 years,101 to 1000,North America,Software,I am experienced with it,I am experienced with it,Has the potential for significant quality improvement,Has the potential for significant quality improvement,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,Improved specification accuracy,Increased amount of specification,Improved chance of keeping specifications in sync with the code,"Management wants IT to adopt this practice, but is not providing resources","Management wants IT to adopt this practice, but is not providing resources",1% to 20%,1% to 20%,Large Impact,Large Impact,Some Impact,No Impact,Difficult,too much get it done,Very Difficult,human flaws,Very Effective,Neutral,Neutral,Neutral,Neutral,Neutral,Effective,Very Effective,Very Effective,Neutral,Neutral,Effective,Effective,Neutral,Very Effective,Very Effective,6 to 10,Both Acceptance and Developer TDD,,,,,,,Developers write tests before writing production code,Developers write tests after writing production code,Testers write tests after developers write production code,,,,,,"Requirements management tool (e.g. Doors, ReqPro)",,,,,,Developer tests,,,,,,,
Developer,6 to 10 years,"Over 100,000",North America,IT Services,I have read about it but not tried it,I have experimented with it,Has some potential for quality improvement,Has the potential for significant quality improvement,,,,,,,Increased quality,Increased ability of developers to safely change software,Increased ability to react to changing stakeholder needs,,,,Management is actively against this practice,Management is actively against this practice,0%,1% to 20%,No Impact,Some Impact,Large Impact,Large Impact,Difficult,"Acceptance TDD still feels like it's way out in front on the bleeding edge. Developer TDD is still revolutionary for most of the people I encounter - many have never even heard of it. I think we are seeing agile practices stratify IT/software organizations into those that change and learn, and those that don't. We can say that we need to wait on acceptance TDD until developer TDD has a higher penetration level - or we can accept that some organizations are just not interested in improving by adopting new techniques, and let them fail.",Easy,"It's easy to start, but hard to master. I'm still working on the 'where to go next' problem and the 'best way to test integration of classes' problem.",No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,No Opinion,Very Effective,Effective,Effective,Effective,Effective,Neutral,Neutral,Neutral,11 to 20,None,,,Developer regression testing,,,,,,,,"Defect management tool (e.g. Bugzilla, ChangeQuest)",,,,,,,,,,,,,,"Software-Based Modeling Tool models (e.g. ErWin, RSA, Enterprise Architect)",,,