Extreme Programming

Publish in

Documents

1,346 views

Please download to get full document.

View again

of 12
All materials on our website are shared by users. If you have any questions about copyright issues, please report us to resolve them. We are always happy to assist you.
Share
Description
Extreme Programming. Alexander Kanavin Lappeenranta University of Technology. Some background. Lightweight vs heavyweight methodologies Software Engineering Institute Capability Maturity Model (SEI CMM) Extreme Programming. Basic ideas.
Transcript
Extreme ProgrammingAlexander KanavinLappeenranta University of TechnologySome background
  • Lightweight vs heavyweight methodologies
  • Software Engineering Institute Capability Maturity Model (SEI CMM)
  • Extreme Programming
  • Basic ideas
  • Was put together as a response to the increasing difficulty of practicing heavyweight methodologies, especially in medium and small projects
  • Has very few rules and practices
  • Rules
  • Fall into four categories
  • Planning
  • Design
  • Coding
  • Testing
  • Rules for planning
  • User stories are written
  • Release planning creates the schedule
  • Make frequent small releases
  • The project velocity is measured
  • The project is divided into iterations
  • Iteration planning starts each iteration
  • Rules for planning 2
  • Move people around
  • A stand-up meeting starts each day
  • Fix XP when it breaks
  • Design rules
  • Simplicity
  • Choose a system metaphor
  • Use CRC cards for design sessions
  • Create spike solutions to reduce risk
  • No functionality is added early
  • Refactor whenever possible
  • Coding rules
  • The customer is always available
  • Code must be written to agreed standards
  • Code the unit test first
  • All code is pair programmed
  • Only one pair integrates code at a time
  • Integrate often
  • Coding rules 2
  • Use collective code ownership
  • Leave optimization till last
  • No overtime work
  • Testing
  • All code must have unit tests
  • All code must pass unit tests before it can be released
  • When a bug is found tests are created
  • Acceptance tests are run often and the results are published
  • Weaknesses of XP
  • Outstanding abilities of the team
  • Having customer on site
  • Doesn’t work in a large environment, with no contracting customer, few experts or simultaneous hardware development
  • Going further
  • http://www.extremeprogramming.org
  • Books: Amazon, Books.ru
  • Related Search
    We Need Your Support
    Thank you for visiting our website and your interest in our free products and services. We are nonprofit website to share and download documents. To the running of this website, we need your help to support us.

    Thanks to everyone for your continued support.

    No, Thanks