Introduction to Agile

  • 1,512 views
Uploaded on

Basic introduction to Agile given by Andy Mayer ofrom Yoomee on 12th October 2010 at the first Yoomee-versity session.

Basic introduction to Agile given by Andy Mayer ofrom Yoomee on 12th October 2010 at the first Yoomee-versity session.

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
  • Basic introduction to Agile given by Andy Mayer from Yoomee on 12th October 2010 at the first Yoomee-versity session.
    Are you sure you want to
    Your message goes here
No Downloads

Views

Total Views
1,512
On Slideshare
0
From Embeds
0
Number of Embeds
4

Actions

Shares
Downloads
0
Comments
1
Likes
5

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Basic intro to Agile
  • 2. agile ≠ Agile
  • 3. Agile ≠ agile
  • 4. Michael McIntyre on “agile”
  • 5. Agile software development is a group of software development methodologies based on iterative and incremental development, where requirements and solutions evolve through collaboration between self-organizing, cross- functional teams.
  • 6. Waterfall methodology
  • 7. Sign off Specification Sign off Design Sign off Build Sign off Testing Go live Waterfall model
  • 8. Waterfall methodology
  • 9. Scope Time Cost ✓ ✓ ? Waterfall costing
  • 10. “ The only constant is change, continuing change, inevitable change, that is the dominant factor in society today. — Isaac Asimov
  • 11. Feedback Feedback Feedback Feedback Specification Design Build Testing Go live Insights Insights Insights Insights Agile model
  • 12. Scope Time Cost ? ✓ ✓ Agile costing
  • 13. 12 Principles of Agile
  • 14. 1 Deliver software “ Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
  • 15. 2 Love change “ Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
  • 16. 3 Show often “ Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
  • 17. 4 Regular contact “ Business people and developers must work together daily throughout the project.
  • 18. 5 Great environment “ Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  • 19. 6 Face time “ The most efficient and effective method of conveying information to and within a development team is face-to-face conversation.
  • 20. 7 Minimise waste “ Working software is the primary measure of progress.
  • 21. 8 Sustainable “ Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely
  • 22. 9 Technical excellence “ Continuous attention to technical excellence and good design enhances agility.
  • 23. 10 Keep it simple “ Simplicity--the art of maximizing the amount of work not done--is essential.
  • 24. 11 Bottom up “ The best architectures, requirements, and designs emerge from self- organizing teams.
  • 25. 12 Self healing team “ At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
  • 26. Scrum is an iterative, incremental methodology for project management often seen in agile software development.
  • 27. Scrum
  • 28. XP is an Agile engineering methodology, focused on delivering usable software iteratively in projects that are expected to change as time goes on.
  • 29. Scrum ≠ XP ≠ Agile