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
Job Description for Senior Software Engineer: • Software development experience using traditional software development life cycle methodologies (covering requirements, design, development, testing...
For more info on latest job openings and other career related information visit my site
Now that I’m starting to appreciate agile, and before I do a massive editing session on my CV to reflect all of those agile projects I worked on but didn’t realise it, I’ve started to wonder how those wonderful institutions EDS and Accenture are going to be affected by it.
Firstly EDS. Not sure how it’s going to affect this shower as they still develop software like it’s the 1980’s anyway. They probably do some waterfall with their development. Can’t see them doing any Prince 2 though. I’d imagine if you mentioned the word agile to EDS, you’d get some very blank looks. All EDS has to do is read some some agile documentation, amend some mission statement docs and they’re set.
Accenture. The company that creates software by committee and has a lot of meetings, very Prince 2. This bunch love the Prince 2 stuff and always prefer those kind of people. If you know Prince 2 OK you’ll be one of the good guys here. Raw develo
Now that I’m starting to appreciate agile, and before I do a massive editing session on my CV to reflect all of those agile projects I worked on but didn’t realise it, I’ve started to wonder how those wonderful institutions EDS and Accenture are going to be affected by it.
Firstly EDS. Not sure how it’s going to affect this shower as they still develop software like it’s the 1980’s anyway. They probably do some waterfall with their development. Can’t see them doing any Prince 2 though. I’d imagine if you mentioned the word agile to EDS, you’d get some very blank looks. All EDS has to do is read some some agile documentation, amend some mission statement docs and they’re set.
Accenture. The company that creates software by committee and has a lot of meetings, very Prince 2. This bunch love the Prince 2 stuff and always prefer those kind of people. If you know Prince 2 OK you’ll be one of the good guys here. Raw develo
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
