1 / 15

NAME, Sheffield 2002

NAME, Sheffield 2002. Ivan Moore Connextra, London ivan@tadmad.com. Are you interested in XP and/or AMs? Why?. Yes. Unproductive work experience no methodology Can work for an individual but not in a team traditional methodology Worked better but was still low productivity

ovid
Download Presentation

NAME, Sheffield 2002

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. NAME, Sheffield 2002 Ivan Moore Connextra, London ivan@tadmad.com

  2. Are you interested in XP and/or AMs? Why? • Yes. • Unproductive work experience • no methodology • Can work for an individual but not in a team • traditional methodology • Worked better but was still low productivity • Mismatch between University taught methodologies and reality • Experience of having been productive by "hacking"

  3. What have been your motivations to explore and experience XP? • After discouraging work experiences, back to University • MSc using Smalltalk – Object-Revelation • PhD on automated refactoring • Job in team using continuous integration (ENVY) • continuous integration-Revelation • But code quality problems • Job in team using Java and JUnit • Automated Unit Testing-Revelation

  4. And then... • Introduced to XP • Included practices that I had learnt worked • Recommended and used by people I respected • Included other practices I was initially sceptical about • Tried XP • Only methodology I had heard about that contained practices that I knew worked and were different than "traditional" methodologies

  5. Are you working for a company doing some sort of XP? • Yes (Connextra) • Employees • Attend XP conferences and events • Write papers • Give talks • Do some XP consulting • Work on XP related open source projects

  6. How has such company introduced XP and/or AMs? • Company was setup doing XP from the start • All development work uses XP

  7. What XP practices has the company adopted? How? Why? • All white-book practices from the start • Use many practices not in white-book but very common in XP teams • TDD (not just test-last) and Mock Objects • Iteration Retrospectives • Gold Cards • Customer written acceptance tests before story estimation

  8. How successful has the company been in ... introducing XP? • XP style approaches have infiltrated other areas of company and to some extent our clients • Developers very keen on XP • Senior managers in company understand and appreciate XP, but not all sales people.

  9. What is the impact of XP and/or AMs on its business? • XP approach in development has enabled large change in direction of company's business • Company has done some XP consulting

  10. What are the long term goals of ... thecompany with respect to XP ... ? • XP here to stay • Continuous evolution of details of practices and new practices • TDD (rather than test-last) • Gold Cards • Relationship with clients

  11. What are your expectations on the future evolution of XP ... ? • Expect some practices to become "de rigueur" that weren't always before • Automated Unit Testing • Continuous Integration • Don't expect all practices to become "main stream" • Pair programming • Resistance from developers as well as managers • Planning Game • Fixed-price, fixed-scope contracts won't disappear

  12. Interaction with other research areas? • Many open source development projects already embracing many XP practices • Expect resurgence/rediscovery of research in some areas, e.g. • Testing • Source control systems • (Evolutionary) Software design

  13. Education, education, education • Higher percentage of new software developers have done "computer science" degrees than previously, so University courses more important than ever • CS graduates need to know • How to program! (e.g. OO, logic and functional programming) • How to work with other people's code (e.g. debugging) • How to work in a team (e.g. source control)

  14. The Future of Agile • New ways needed of working with external clients • New ways to design/develop software for evolutionary approaches • multi-version components/libraries • Effects on design • Effects on tools

  15. Contact http://www.connextra.com • ivan@tadmad.com

More Related