Diese Präsentation wurde erfolgreich gemeldet.
Wir verwenden Ihre LinkedIn Profilangaben und Informationen zu Ihren Aktivitäten, um Anzeigen zu personalisieren und Ihnen relevantere Inhalte anzuzeigen. Sie können Ihre Anzeigeneinstellungen jederzeit ändern.

Extreme programming practices ( xp )

256 Aufrufe

Veröffentlicht am

Extreme programming, founded by Kent Beck one of the original signatories of Agile Manifesto is a lightweight agile methodology of agile software development and engineering .

Veröffentlicht in: Software
  • Als Erste(r) kommentieren

Extreme programming practices ( xp )

  1. 1. Extreme Programming Practices
  2. 2. About Me • Kapil Raj Nakhwa Shrestha • Co-founder of Jyaasa Technologies Pvt ltd. • 9 years experience working with Ruby and Ruby and rails • kapil@jyaasa.com
  3. 3. Origins •March 6th, 1996, Chrysler Comprehensive Compensation System ( C3) . •Kent Beck Kent Beck when he was young ( Not me )
  4. 4. • Instead of delivering everything you could possible want on some date in future, Xp delivers the software as you want it. • Simple yet effective environment for enabling teams to become highly productive. • Improves the way we develop software in 5 key aspects.
  5. 5. Xp Project Heartbeat Type to enter a caption.
  6. 6. XP values • Communication • Simplicity • Feedback • Respect • Courage
  7. 7. Xp Rules ( Practices) • Planning • Managing • Designing • Coding • Testing
  8. 8. Planning • User Stories • Release Plan • Iteration Plan
  9. 9. Planning
  10. 10. Managing • Sustainable Pace • Daily Stand up • Measure Project Velocity • Move people around • Fix Xp when It breaks
  11. 11. Designing • Simplicity ( TUBE ) • Choose a system metaphor • CRC cards for system design • Use Spike to reduce risk • YAGNI • Refactor Mercilessly
  12. 12. Coding • Customer is always available • Write code to agreed standard • Write unit tests first • Pair Program • Sequential Integration • Collective Ownership
  13. 13. Customer is always available
  14. 14. Testing • All code must have unit tests • All tests must pass before production • When bug is found , Create a test • Acceptance tests are run often and metrics provided to the team.
  15. 15. XP FlowChart
  16. 16. Iteration FlowChart
  17. 17. FeedBack Loops in XP
  18. 18. The paradox of a process If you do not use your process, It will not help you. If your process does not help you, You would not use it.
  19. 19. Want to discuss more on XP? • kapil@jyaasa.com • twitter: xecutioner303

×