Pain Relievers for Continuous Integration and Agile Development
Date: Thursday, August 14, 2008
Time: 2:00 PM Eastern; 11:00 AM Pacific
About the Webcast:
Do you need:
Faster builds?
Trouble-free merges?
Reliable builds to test against?
You’re the build manager. You actually build the product that ships, yet get no respect. You’re on your own to build your toolset.
You’re expected to prov
Summary
In this interview taken during the Agile 2007 conference, James Shore, a prominent figure of the Agile community, talks about the book "The Art of Agile Development" he and Shane Warden wrote. The book was not yet published at the time when the interview was made, and James offers a valuable introduction to the book touching various aspects of Agile development.
Bio
James is a prominen
Boy do they do Agile development here. Incremental releases all over the place. Changes to requirements coded at the drop of a hat. They do Scrum too. Quick little chatty meetings, ‘you finished that code you were going to write yesterday?’, ’can you do that amendment by tomorrow?’. This is developers heaven.
Not that anybody on the development team knows they are doing Agile. They almost certainly haven’t even heard of it. Scrum? That’s a rugby thing, right? No this is development from 20 years ago which just sounds like Agile and Scrum.
When a program has got some unexpected features then the documentation is amended to justify these features. Even though it’s baselined. They find an excuse to review the baselined document and make all sorts of amendments to justify all of the odd behaviours. Not that they will let you know that the documentation has been changed. In fact that’s the last thing they want, you kept in the loop. No it&r
Boy do they do Agile development here. Incremental releases all over the place. Changes to requirements coded at the drop of a hat. They do Scrum too. Quick little chatty meetings, ‘you finished that code you were going to write yesterday?’, ’can you do that amendment by tomorrow?’. This is developers heaven.
Not that anybody on the development team knows they are doing Agile. They almost certainly haven’t even heard of it. Scrum? That’s a rugby thing, right? No this is development from 20 years ago which just sounds like Agile and Scrum.
When a program has got some unexpected features then the documentation is amended to justify these features. Even though it’s baselined. They find an excuse to review the baselined document and make all sorts of amendments to justify all of the odd behaviours. Not that they will let you know that the documentation has been changed. In fact that’s the last thing they want, you kept in the loop. No it&r
