Matt McLarty wrote: For more info...
Follow me on Twitter
See our website
May. 2, 2012 03:40 PM EDT
| By Jeremy Geelan | Article Rating: |
|
| May 17, 2008 06:15 AM EDT | Reads: |
33,855 |
“Developers need to realize that Automated Defect Prevention benefits them," says Parasoft co-founder & CEO Dr Adam Kolawa in this Exclusive Q&A with SYS-CON Media's Java Developer's Journal. 
"But they won’t start recognizing this until they see that they have less work," Kolawa continues. The key to success, he adds, is to have an infrastructure handle as much work as possible. "This way, developers have time to focus on the creative tasks they enjoy most...the ones that truly require human intelligence."
View Dr Kolawa on SYS-CON.TVRead Dr Kolawa's Articles
“Developers need to realize that [ADP] benefits them. But they won’t start recognizing this until they see that they have less work.”
Dr Adam Kolawa is the coauthor of the recently published Automated Defect Prevention: Best Practices in Software Management (Wiley & Sons, 2007). He is the co-founder & CEO of Parasoft, a leading provider of Automated Error Prevention software solutions. Aside from additionally co-authoring Bulletproofing Web Applications, Dr Kolawa has contributed to or written more than 100 commentary pieces and technical papers, and has coauthored numerous scientific papers.-- Dr Adam Kolawa, Co-Founder & CEO of Parasoft
Java Developer’s Journal: How realistic is it to seek to modify the development process in the entire software life cycle to reduce opportunities for mistakes? Is Automated Defect Prevention simply too much for IT organizations to take on board?
Dr Adam Kolawa: It’s not very realistic. That’s why we’re not trying to modify the development process. Rather, we’re trying to improve it. There’s a big difference. We learned that it’s critical to take it slow. In the book, we discuss this under ADP Principle 6: Incremental Implementation of ADP’s Practices and Policies. In a nutshell, you never want to attack the process as a whole. Instead, start by going after a few “low-hanging fruits”— relatively simple changes that will yield significant gains. Then, keep moving forward.
Dr Adam Kolawa: It’s not very realistic. That’s why we’re not trying to modify the development process. Rather, we’re trying to improve it. There’s a big difference. We learned that it’s critical to take it slow. In the book, we discuss this under ADP Principle 6: Incremental Implementation of ADP’s Practices and Policies. In a nutshell, you never want to attack the process as a whole. Instead, start by going after a few “low-hanging fruits”— relatively simple changes that will yield significant gains. Then, keep moving forward.
CIO, CTO & Developer Resources
It is too much to expect that you can get the entire organization on board at once. That’s why you need you introduce it incrementally, winning over one group at a time. It typically takes years to extend it across the entire organization.
Java Developer’s Journal: Is it possible to quantify what proportion of getting ADP into the DNA of developers and managers is a software development challenge and what proportion is a human or change-management challenge?
AK: I really think that this is all a human and change management challenge. Developers need to realize that this benefits them. But they won’t start recognizing this until they see that they have less work. The key to success here to have an infrastructure handle as much work as possible. This way, developers have time to focus on the creative tasks they enjoy most… the ones that truly require human intelligence.
Next Page: Dr Kolawa on the Future of Technology
Next Page: Dr Kolawa on the Future of Technology
- Cloud Expo New York: Why PostgreSQL is the Database for the Cloud
- Cloud Expo New York Speaker Profile: Dave Linthicum – Blue Mountain Labs
- Agile Adoption – Crossing the Chasm
- Cloud Expo New York: The Java EE 7 Platform - Developing for the Cloud
- Write Once Run Anywhere or Cross Platform Mobile Development Tools
- Cross-Platform Mobile Website Development – a Tool Comparison
- Cloud Expo New York: Cloud Architectures Require Scale-Out Storage
- Cloud Expo New York: The Growing Big Data Tools Landscape
- Architecture Governance – the TOGAF Way
- Big Data – A Sea Change of Capabilities in IT
- Cloud Expo New York: Cloud Computing and Healthcare
- Cloud Expo New York: Mobilizing Enterprise Applications for the Cloud
- Cloud Expo New York: Why PostgreSQL is the Database for the Cloud
- Cloud Expo New York Speaker Profile: Dave Linthicum – Blue Mountain Labs
- Agile Adoption – Crossing the Chasm
- Red Hat Executive Appointed to Technology Services Industry Association (TSIA) Support Services Advisory Board
- Graal, a Dynamic Java Compiler in the Works
- Cloud Expo New York: The Java EE 7 Platform - Developing for the Cloud
- Write Once Run Anywhere or Cross Platform Mobile Development Tools
- Cross-Platform Mobile Website Development – a Tool Comparison
- Cloud Expo New York: Cloud Architectures Require Scale-Out Storage
- What Motivates Open Standards in the Cloud?
- Cloud Expo New York: The Growing Big Data Tools Landscape
- Architecture Governance – the TOGAF Way
- The i-Technology Right Stuff
- The Top 150 Players in Cloud Computing
- Who Are The All-Time Heroes of i-Technology?
- Where Are RIA Technologies Headed in 2008?
- Get the Message
- ESB Myth Busters: 10 Enterprise Service Bus Myths Debunked
- i-Technology Viewpoint: Is Web 2.0 the Global SOA?
- i-Technology Viewpoint: Thinking Outside the VC Box
- i-Technology Viewpoint: When to Leave Your First IT Job
- SOA Web Services Edge Conference Coverage on SYS-CON.TV
- SYS-CON.TV's "SOA Web Services" and "Enterprise Open Source" Programs To Air in December
- Five Reasons Why Web 2.0 Matters
Subscribe to SOA World Magazine Email News Alerts
Subscribe via RSS
