Created
May 20, 2009 17:13
-
-
Save littlemove/114950 to your computer and use it in GitHub Desktop.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
“You can take a group of idiots that maybe even didn’t go to school, don’t understand computer science, don’t understand software development engineering techniques, hate each other, don’t understand the business domains, have lousy engineering tools and uniformly, they will produce CRAP every increment.“ | |
Ken Schwaber - “Scrum et al.“@ Google Tech Talks | |
Talking about Waterfall Vs SCRUM Software Development Process | |
¿Qué es "Agil"? | |
Individuals and interactions over processes and tools | |
Working software over comprehensive documentation | |
Customer collaboration over contract negotiation | |
Responding to change over following a plan | |
Algunos principios del "Agile Manifesto": | |
"Deliver working software frequently, from a | |
couple of weeks to a couple of months, with a | |
preference to the shorter timescale." | |
"Continuous attention to technical excellence | |
and good design enhances agility." | |
"Simplicity--the art of maximizing the amount | |
of work not done--is essential." | |
"At regular intervals, the team reflects on how | |
to become more effective, then tunes and adjusts | |
its behavior accordingly." | |
¿De dónde viene? | |
(1986) Product development - Japón - Rugby - EEUU - Top Gun (2001) | |
Componentes | |
Roles: Cerdos, Gallinas | |
Reuniones: Scrum(15 min), Sprint Planning(8 h), Sprint | |
Review(4 h), Sprint Retrospective(3 h) | |
Artefactos: Product Backlog, Sprint Backlog, Defect Backlog, Burn down chart | |
"Dame una estimación... my ass" | |
Product Backlog: Colección de "features". El Product Owner selecciona | |
cuales de esas features van a estar en determinada release. | |
Release Backlog: Se priorizan las features y se estiman (en unidades | |
de 4 horas) -> | |
Sprints: Milestones periódicos. Duración: entre 3 y 30 días (mínimo 4?). Conjunto de features | |
(subproducto) 100% funcional. Monitorización. | |
Burn down chart: demo. | |
¿Cómo se adapta al cambio? | |
Los sprints son la clave (creo) | |
Problemas Simplelogicos | |
"Equipos de un solo hombre" | |
Mantenimientos | |
TCK | |
Ellos hablan con el cliente | |
¿Qué hace un jefe de proyecto? ¿Qué queremos que haga? | |
Hablemos de las estimaciones | |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment