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?
Connect your Facebook account to Prezi and let your likes appear on your timeline.
You can change this under Settings & Account at any time.
Transcript of GPR2016
Introducción a las
Short term vs Long term
Code quality inspectors
CI integration (automation)
Clear roles (PO, SM, ST)
GPR2016: Metodologías ágiles
By Agustín Yagüe (2016)
Individuals and interactions
People are not components or Id
Empower people to be proactive
People more important than tools
To promote positive conflict:
Documents are not executable
Documents are needed but only:
the required by customers
the required to maintenance
Enroll Product Owner
Product Owner all over the process
Product Owner availability
Responding to change
Requirements always change
Driven by business value
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.
Simplicity--the art of maximizing the amount of work not done--is essential.
The best architectures, requirements, and designs emerge from self-organizing teams.
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.
Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
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.
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.