Successfully reported this slideshow.
Your SlideShare is downloading. ×

Extreme Programming (XP) for Dummies

Ad

Extreme Programming
(XP) for Dummies
Jon McNestrie

Ad

Extreme Programming (XP) was
conceived and developed to
address the specific needs of
software development conducted
by sm...

Ad

Let’s Do AGILE!
• The solution to all of your problems?
• The reason for things getting worse?
• A mirror showing the ugly...

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Ad

Upcoming SlideShare
XP In 10 slides
XP In 10 slides
Loading in …3
×

Check these out next

1 of 14 Ad
1 of 14 Ad

Extreme Programming (XP) for Dummies

Good software engineering practices are key to building quality and in this talk we’ll have a whistle stop tour of a range of techniques that often sit under the ‘XP’ umbrella such as TDD (Test Driven Development), Pair Programming, BDD (Behaviour Driven Development) and more generally Continuous Delivery.

Good software engineering practices are key to building quality and in this talk we’ll have a whistle stop tour of a range of techniques that often sit under the ‘XP’ umbrella such as TDD (Test Driven Development), Pair Programming, BDD (Behaviour Driven Development) and more generally Continuous Delivery.

Advertisement
Advertisement

More Related Content

Advertisement

Extreme Programming (XP) for Dummies

  1. 1. Extreme Programming (XP) for Dummies Jon McNestrie
  2. 2. Extreme Programming (XP) was conceived and developed to address the specific needs of software development conducted by small teams in the face of vague and changing requirements. I'm not a great programmer; I'm just a good programmer with great habits. - Kent Beck
  3. 3. Let’s Do AGILE! • The solution to all of your problems? • The reason for things getting worse? • A mirror showing the ugly truth… Scrum can help you build crap software very very quickly - Jon McNestrie
  4. 4. Great Habits • Fast Feedback • Test First Development • Software Engineering / Craftsmanship
  5. 5. Code Reviews • A ‘quality gate’? • Who should do code reviews? • Why? HOURS
  6. 6. Pair Programming • Twice the effort? • Driving and Navigating • Shared understanding SECONDS
  7. 7. Unit Testing • Isolated testing of the smallest ‘units’ of the application • Easily automated, repeatable • Confidence when refactoring? MINUTES
  8. 8. Test Driven Development (TDD) • Red -> Green -> Refactor • It’s about Design • Tests are a happy side effect MINUTES
  9. 9. Behaviour Driven Development (BDD) • Gherkin / Cucumber • User readable tests • Backed by ‘Step definitions’ (code) MINUTES
  10. 10. Acceptance Test Driven Development • Test first BDD • The missing link between user stories and the product • Documentation? HOURS
  11. 11. Continuous Integration • Automated build and test • Hooked up to source control • Confidence in the codebase MINUTES
  12. 12. Continuous Delivery • An automated build, test and deployment pipeline • Frequent production releases • The end of the fear HOURS
  13. 13. Shorter and shorter feedback loops Improved flow and realisation of value Quality is a happy accident

×