In Agile, it seems like everybody (testers, developers, customers, project manager, dba) is working closer together.  It seems like business analysts are becoming a catalyst instead of an intermediary between developers and customers.  As the software architecture is developed incrementally, do we still need an architect?  What if we would replace the term architect by a team culture?  Could we set a culture embraced by everybody?  Would we empower team members if they could influence the day-to-day architecture?  

Should we all keep those titles when moving into an Agile project?  Is a software developer still a software developer even if he’s writing unit tests and talking with the customer on a weekly basis?  If a developer is monitoring the continuous integration process, is he a build master as well?  Do we have to ask for new skills set for our developers?  Or should we rename the title software developer to something broader to encompass what this person is doing?  As an example, Scrum seems to give new titles to people in a software team (Scrum master and Product Owner).  And what about tests?  Should we still call them tests?  Traditionnaly, people have this conception that tests have to be done at the end of the software development cycle.  In Agile, it's done during each iteration where they take an active part in the process.

While Agile is redefining how software is made, should we also redefine the roles and titles of those who produce software?