1 / 13

Agile Manifesto

Agile Manifesto. http://agilemanifesto.org/principles.html February, 2001 XP, SCRUM, DSDM, Adaptive Software Development, Crystal, Feature-Driven Development, Pragmatic Programming. Continuous Delivery.

larrycarter
Télécharger la présentation

Agile Manifesto

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Agile Manifesto • http://agilemanifesto.org/principles.html • February, 2001 • XP, SCRUM, DSDM, Adaptive Software Development, Crystal, Feature-Driven Development, Pragmatic Programming ã 2007, Spencer Rugaber

  2. Continuous Delivery • Our highest priority is to satisfy the customer through early and continuous delivery of valuable software • Sustainable process • Feature boxed ã 2007, Spencer Rugaber

  3. Changing Requirements • Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage • Particularly appropriate for situations with volatile requirements ã 2007, Spencer Rugaber

  4. Frequent Delivery • Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale • Very small increments • Implies increased release overhead ã 2007, Spencer Rugaber

  5. Customer Involvement • Business people and developers must work together daily throughout the project • Implies identified customer (or surrogate) • And big-time customer commitment • Suitable for in-house projects ã 2007, Spencer Rugaber

  6. Motivated Participants • Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done • All processes want motivated individuals • Agile office design ã 2007, Spencer Rugaber

  7. Meetings • The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. • Questionable • Have to identify who should be attending ã 2007, Spencer Rugaber

  8. Software Focus • Working software is the primary measure of progress • Deemphasis of infrastructure, both architectural and process ã 2007, Spencer Rugaber

  9. Sustainability • Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely • All processes would like this • No crises requiring overtime ã 2007, Spencer Rugaber

  10. Amortization • Continuous attention to technical excellence and good design enhances agility • Amortization of design and quality activities throughout development • Localizes design decisions ã 2007, Spencer Rugaber

  11. Simplicity • Simplicity--the art of maximizing the amount of work not done--is essential • Avoid generalizing ã 2007, Spencer Rugaber

  12. Self Organization • The best architectures, requirements, and designs emerge from self-organizing teams • Conway's law ã 2007, Spencer Rugaber

  13. Reflection • At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly • Amortization of process ã 2007, Spencer Rugaber

More Related