Send the link below via email or IMCopy
Present to your audienceStart 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.
Make your likes visible on Facebook?
You can change this under Settings & Account at any time.
Agile Values, Principles and Practices
Transcript of Agile Values, Principles and Practices
& Practices Individuals and interactions over processes and tools
Working software over comprehensive documentation
Customer collaboration over contract negotiation
Responding to change over following a plan Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in
development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a
couple of weeks to a couple of months, with a
preference to the shorter timescale. Business people and developers must work
together daily throughout the project. Build projects around motivated individuals.
Give them the environment and support they need, and trust them to get the job done. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence
and good design enhances agility. Simplicity --
the art of maximizing the amount of work not done
-- is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly. That is, while there is value in the items on
the right, we value the items on the left more. Agile Manifesto In Feburary 2001 seventeen thought leaders in the software industry got together to identify what produces the most successful software development projects. Test Driven Development Continuous Integration Pair Programming Customer Collaboration Continious Code Improvements
(refactoring) Short Release Cycle Coding Standards Collective Code Ownership Simple Design Sustainable Pace Demo of Pivotal Tracker Planning
Determine delivery based on velocity