Search for Podcasts
Trumix.com
Our New Site
Internet Radio
Podcasts
Create a Playlist


Podcast Directory:
Browse Podcasts
Add your Podcast
Remove a Podcast
Search for Podcasts
Podcast Directory
by Country
by Language
by Buzz
by Popularity
by Category
by Tags
by Region
by City
on a Google Map



Podcast Help:
What is Podcasting
Creating an XML
Podcast Hosting
Podcast Software
Firefox Plugin
Podcast Hardware




About Us:
Podcast Advertising
Contact Us
Copyright Issues
Help Wanted




Internet Radio:
Find
State
Country
Language
Music
Sports
Regions
Popularity

Discount Gold Offer

Stiletto New Price

Free Graphics


QA Podcast #9: Extreme Programming and QA With Kent Beck Episode

PodcastDirectory / Technology / Technology
PodcastDirectory / Regions / NA / Canada
QA Podcast

Expert Conversations about Software Quality Assurance

Primary Format :
Technology

Also Listed as:

User Tags:

User Votes:

RSS Feed
Website

Visit Trumix.com for the most recent listings of:

QA Podcast #9: Extreme Programming and QA With Kent Beck

Play Now -->


QA Podcast #9: Extreme Programming and QA With Kent Beck

DATE : Wed, 30 Nov 2005 21:57:35 -0800
Entered in Database : 2005-12-01 05:57:35
length : 15436898
Link to the Show / Show Notes

On today's show we're onthe phone with the creator ofExtremeProgramming(XP) and one of the founders of theAgile Manifesto,KentBeck. Kent and Wolfgang discuss the relationship between XP and QA.

This will be our final podcast of 2005. Stay tuned, as we'll be returning inJanuary with more testing topics. As always, if you've got feedback or a suggestionfor a future episode, leave a comment ordropus an email.

Here are some quotes from today's show:

"10 years ago, when I started talking about the precursors to XP, programmersweren't writing tests, ever. But, there are a couple of trends that contributeto changing this. One is shorter and shorter software release cycles. If youhave to release software once a month, you don't have time for a two-monthQA cycle...The other large-scale trend is toward asking for more visibilityand accountability in the software development process."

"In XP-style development, two people typically write code together. They'rehaving a conversation--the keyboard is going back and forth. So you alreadyhave that second set of eyes looking at the code. Say you're workingon thecode, I might be thinking about the next test that we could be writing."

"You can't know what you don't know. Part of the XP philosophy is keepingyour options open as long as possible. Rather than having a big architecturedeveloped up front. In XP, you would develop the architecture along with thecode along with the tests for the non-functional requirements."

Links for this conversation's topic:

Technorati tags:


Play in your Iphone