1 / 13

Extreme Programming and Agile Methodologies - Experiences and Expectations

Workshop: Cagliari 04/10/2002. Extreme Programming and Agile Methodologies - Experiences and Expectations. Why XP and AM?. Atlantis is an industrial research laboratory. Its aim is to become an international Innovation Excellence Centre specialised in Territorial Development

bryant
Télécharger la présentation

Extreme Programming and Agile Methodologies - Experiences and Expectations

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Workshop: Cagliari 04/10/2002 Extreme Programming and Agile Methodologies - Experiences and Expectations XP and AM experiences and expectations

  2. Why XP and AM? • Atlantis is an industrial research laboratory. Its aim is to become an international Innovation Excellence Centre specialised in Territorial Development • XP and AM are changing the way of planning, developing and managing a project XP and AM experiences and expectations

  3. Why XP in our firm? • Need of a people oriented process • Need to introduce agile guidelines of development into a young enviroment • Need of small releases (minimum time to market) XP and AM experiences and expectations

  4. XP introduction in the firm • Two pilots research projects: E_Marketplace portal E_Government system XP and AM experiences and expectations

  5. XP introduction • A successful adoption of XP E_marketplace project based on J2EE architecture Open source components XP and AM experiences and expectations

  6. XP Introduction • A successful adoption of XP E_Government System: Business Process Reengineering based on Java Swing Costs & Performances based on J2EE Architecture XP and AM experiences and expectations

  7. XP Introduction • Gradual introduction of XP Practices At first Planning game Testing Coding standards All practices (except for the Metaphor) since the beginning of the project XP and AM experiences and expectations

  8. XP Installed • Accepted by programmers XP is centered on the developer troubles: Skill of programmers XP and AM experiences and expectations

  9. XP Installed • XP practices adopted planning game & user stories on-site customercontinuous testing short releasessimple designrefactoringpair programmingcontinuous integrationcollective code ownershipno overtimecoding standards • XP Practices not adopted • Metaphor XP and AM experiences and expectations

  10. XP Installed • Benefits • People involvement • Putting people first: • Traditional methodologies consider people as replaceable parts (process-oriented) • Improved software development quality • Control of the process development • Satisfaction of all interested parties • Success factors • XP is able to motivate people XP and AM experiences and expectations

  11. XP installed • The impact on business • Actually it’s difficult to calculate, but we can observe the first good results in research projects • It’s considered an investment compatible with Atlantis mission: research XP and AM experiences and expectations

  12. XP Future • Objectives • A standard process • Tools for managing XP • Scrum introduction? • XP and Quality Certification • Customer focus • Involvement of people • Continual improvement XP and AM experiences and expectations

  13. XP Impact end evolution • Strong Impact on specific research areas • Component Development • Frameworks • Open source • Need of agile and integrated tools XP and AM experiences and expectations

More Related