Conceptos de Metodologias Agiles
Transcript of Conceptos de Metodologias Agiles
-
8/13/2019 Conceptos de Metodologias Agiles
1/30
Conceptos de las Metodologas
Agiles para la Administracin de
Proyectos
-
8/13/2019 Conceptos de Metodologias Agiles
2/30
Los problemas ms habituales que provocan fracasos
Estudio Ao 1995, The Chaos Report, Standish Group International
(Muestra: 365 IT managers de 8380 aplicaciones de diversas industrias en empresas de
diferente envergadura)
31.1% de los proyectos fueron cancelados antes de terminarse
52.7% de los proyectos superaron el tiempo estimado, requirieron mayores
presupuestos y no ofrecieron la funcionalidad pautada.
16.2% de los proyectos se finalizaron en tiempo y con el presupuesto estimado.
16
27
26
28
53
33
46
49
31
40
28
23
0% 20% 40% 60% 80% 100%
1994
1996
1998
2000
Exitosos
Superados
Fracasados
-
8/13/2019 Conceptos de Metodologias Agiles
3/30
Cmo reducir estos problemas ? Factores de xito
35124
Participacin del Usuario
RespaldoGerencial
Requerimientos y
objetivos claros yprecisos
Planificacionadecuada
Expectativasrealsticas / Fijaralcance / Etapas
cortas
-
8/13/2019 Conceptos de Metodologias Agiles
4/30
Chaos 2004
People know that the more
common scenario in our
industry is still: over budget,over time, and with fewer
features than planned.Most of the comments I get on
that are: "I don't have ANY that
come in on time..."
Jim Johnson is the founder and chairman of
the Standish Group, a globally respected
source of independent primary research and
analysis of IT project performance.
http://www.infoq.com/articles/Interview-Johnson-
Standish-CHAOS
http://www.standishgroup.com/http://www.standishgroup.com/ -
8/13/2019 Conceptos de Metodologias Agiles
5/30
Standish Group, 2006: Factores de xito
-
8/13/2019 Conceptos de Metodologias Agiles
6/30
Standish Group, 2006
A big problem was project bloat, causing projects to go over time,over budget, and creating features and functions not
required. Especially in government. Agile really helps this - smallincrements. You know: they say "I need this", but by next sprint: "it's
not as important as I originally thought it was."
GD: Yes, prioritizing features helps... always asking: what's the
business advantage? Identifying low value items and putting them at
the end... and then maybe the project never gets there, so you didn't
need them after all.
-
8/13/2019 Conceptos de Metodologias Agiles
7/30
-
8/13/2019 Conceptos de Metodologias Agiles
8/30
De qu hablamos cuando hablamos de agilidad ?
1 - Ligero, rpido
2 - Moverse con soltura
-
8/13/2019 Conceptos de Metodologias Agiles
9/30
Qu entendemos por Cambios ?
-
8/13/2019 Conceptos de Metodologias Agiles
10/30
-
8/13/2019 Conceptos de Metodologias Agiles
11/30
-
8/13/2019 Conceptos de Metodologias Agiles
12/30
-
8/13/2019 Conceptos de Metodologias Agiles
13/30
-
8/13/2019 Conceptos de Metodologias Agiles
14/30
-
8/13/2019 Conceptos de Metodologias Agiles
15/30
-
8/13/2019 Conceptos de Metodologias Agiles
16/30
-
8/13/2019 Conceptos de Metodologias Agiles
17/30
-
8/13/2019 Conceptos de Metodologias Agiles
18/30
-
8/13/2019 Conceptos de Metodologias Agiles
19/30
-
8/13/2019 Conceptos de Metodologias Agiles
20/30
-
8/13/2019 Conceptos de Metodologias Agiles
21/30
-
8/13/2019 Conceptos de Metodologias Agiles
22/30
-
8/13/2019 Conceptos de Metodologias Agiles
23/30
Traditionally, users are educated that its much more expensive tochange or add requirements during or after the software is built.
Some organisations quote some impressive statistics designed tofrighten users into freezing the scope. The result: It becomesimperative to include everything they can think ofin fact everythingthey ever dreamed of!
And whats more, its all important for the first release, because we allknow Phase 2s are invariably hard to get approved once 80% of thebenefits have been realised from Phase 1.
Ironically, users may actually use only a tiny proportion of any softwareproduct, perhaps as low as 20% or less, yet many projects start life witha bloated scope. In part, this is because no-one is really sure at the
outset which 20% of the product their users will actually use.
Equally, even if the requirements are carefully analysed and prioritised,it is impossible to think of everything, things change, and things areunderstood differently by different people.
-
8/13/2019 Conceptos de Metodologias Agiles
24/30
Agile Development works on a completely different premise.Agile Development works on the premise that
requirements emerge and evolve, and that howevermuch analysis and design you do, this will always be the casebecause you cannot really know for sure what youwant until you see and use the software. And in thetime you would have spent analysing and reviewingrequirements and designing a solution, external conditions could
also have changed.
So if you believe that pointthat no-one can really knowwhat the right solution is at the outset when therequirements are writtenits inherently difficult, perhapseven practically impossible, to build the right solution using
a traditional approach to software development.
-
8/13/2019 Conceptos de Metodologias Agiles
25/30
-
8/13/2019 Conceptos de Metodologias Agiles
26/30
-
8/13/2019 Conceptos de Metodologias Agiles
27/30
-
8/13/2019 Conceptos de Metodologias Agiles
28/30
-
8/13/2019 Conceptos de Metodologias Agiles
29/30
-
8/13/2019 Conceptos de Metodologias Agiles
30/30