Loading presentation...

Present Remotely

Send the link below via email or IM


Present to your audience

Start remote presentation

  • Invited audience members will follow you as you navigate and present
  • People invited to a presentation do not need a Prezi account
  • This link expires 10 minutes after you close the presentation
  • A maximum of 30 users can follow your presentation
  • Learn more about this feature in our knowledge base article

Do you really want to delete this prezi?

Neither you, nor the coeditors you shared it with will be able to recover it again.


Agile Presentation

No description

Ryan Causey

on 26 February 2013

Comments (0)

Please log in to add your comment.

Report abuse

Transcript of Agile Presentation

Agile Software Development A presentation by Ryan Causey The Agile Manifesto Individuals and interactions OVER processes and tools Customer collaboration OVER contract negotiation Responding to change OVER following a plan Working software OVER comprehensive documentation That is, while there is value in the items on
the right, we value the items on the left more. Agile is NOT: Agile is: an excuse to stop producing documentation A chance to question the need for the document and eliminate anything that doesn't make sense, isn't useful, or isn't valuable a chance to eliminate planning Planning that does not hinder your project because it is lightweight, iterative, and efficient a wide open door for feature creep Transparent and flexible to allow stakeholders to request changes be made while still taking the tradeoffs into consideration An Agile Process What is Agile? Agile is a term that is an umbrella under which development methodologies like SCRUM, Extreme Programming, Crystal, and others fall. Brief history of Agile 1990's saw a pushback against the 'Heavyweight' software development methodology, mainly Waterfall
Many 'Lightweight' methodologies were emerging at this time such as SCRUM
February 2001: 17 software developers met at the Snowbird resort in Utah and created the Manifesto for Agile Software Development 12 Principles of Agile Software Development 1. Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.
2. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.
3. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.
4. Business people and developers must work together daily throughout the project.
5. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
6. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. 7. Working software is the primary measure of progress.
8. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely.
9. Continuous attention to technical excellence and good design enhances agility.
10. Simplicity--the art of maximizing the amount of work not done--is essential.
11. The best architectures, requirements, and designs emerge from self-organizing teams.
12. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. Useful Links http://agilemanifesto.org/ http://www.agilealliance.org/ http://www.agile-process.org/ Questions?
Full transcript