Agile Processes in Software Engineering and Extreme Programming- P3:“The Program Commitee of XP 2000 invites you to participate in this meeting of software development researchers, professionals, educators, managers, and students. The conference brings together people from industry and academia to share experiences and ideas and to provide an archival source for important papers on flexible process-related topics. | 48 A. Elshamy and A. Elssamadisy Overall BAs or customers are responsible for creating integration and no-coding stories between sub projects. QAs have to test these stories and create test scenarios that will flow across project boundaries. Overall developers architects are responsible for identifying integration points between projects and to work on or reassign defects to sub teams. Only overall project manager is required all the time once there are sub teams Overall BAs QAs anddeveloperscan Ise assigned on as needed bases and rotate from different sub teams. Developers on the brain team will maintain a master continuous integration build. They are also responsible for migratingDB end c ede chaneesto the metier beild. Issues with this build man benesolveh withnub-teamg. 5 Under the Hood A rchitect There is no traditional architect role in mob agile development methodologies. The design evolves through test driven Ocvclopiiiciii which invcla afoam af continuoot design. Unfortunately subteams frequentfy caese a rcinvanting of tgf wherl. Hi ffaCt-tional projects this wtt attved wittupfroct design. Uefront dtoigr is looked down upon see a discussion below in Refactoring and Design Ahead . With small teams the architect role is frequently dropped. In large teams however it is often beneficial to reintroduce a modifiedversionof two successful versions we have seen practiced are Keeper of the Theore tqC tie Code Tlie archittre ta e memte og tho tern otiO1 afgg mficant design and drvetopmeol tatoni and eopencnco. A iffd moi at a theatcfttoate role is to understand tOe wholeapphcavon cefe-ravC _ieohtre yhs de-eeady pairs with others on OhefopntitqunoPy enPwittbo aporiiripantmmtnp aftle mad-eling design sessions aeflie wlncho-rdt Tho .mcdtra0ih relsît _yle thtoay ol the code and can help guida oüierronnew droeirpmant to t moeth y thev ft of how the part they f e workineonfits in the whole. This helps keep away redundancies and gives the code-base a .
