Download to read offline
![[XPday.vn] is XP still eXtreme? {keynote talk} (at) [XP Day Vietnam 2015]](https://cdn.slidesharecdn.com/ss_thumbnails/xpday-150421042802-conversion-gate02-thumbnail.jpg?width=640&height=640&fit=bounds)
Extreme programming practices ( xp )
- 1.
- 2. About Me • KapilRaj Nakhwa Shrestha • Co-founder of Jyaasa Technologies Pvt ltd. • 9 years experience working with Ruby and Ruby and rails • kapil@jyaasa.com
- 3. Origins •March 6th, 1996, Chrysler Comprehensive CompensationSystem ( C3) . •Kent Beck Kent Beck when he was young ( Not me )
- 4. • Instead ofdelivering 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. Xp Project Heartbeat Type toenter a caption.
- 6. XP values • Communication •Simplicity • Feedback • Respect • Courage
- 7. Xp Rules (Practices) • Planning • Managing • Designing • Coding • Testing
- 8. Planning • User Stories •Release Plan • Iteration Plan
- 9.
- 10. Managing • Sustainable Pace •Daily Stand up • Measure Project Velocity • Move people around • Fix Xp when It breaks
- 11. Designing • Simplicity (TUBE ) • Choose a system metaphor • CRC cards for system design • Use Spike to reduce risk • YAGNI • Refactor Mercilessly
- 12. Coding • Customer isalways available • Write code to agreed standard • Write unit tests first • Pair Program • Sequential Integration • Collective Ownership
- 13. Customer is alwaysavailable
- 14. Testing • All codemust 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.
- 16.
- 17.
- 18. The paradox ofa 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. Want to discussmore on XP? • kapil@jyaasa.com • twitter: xecutioner303