definición y priorización del alcance de proyectos a través de wbs

Bogotá,  20  de  marzo  de  2015  

Fuente:  2015  Chaos  Report.  Project  Smart.  h=p://www.projectsmart.co.uk/docs/chaos-­‐report.pdf    

Fuente:  2015  Chaos  Report.  Project  Smart.  h=p://www.projectsmart.co.uk/docs/chaos-­‐report.pdf    

Fuente:  2015  Chaos  Report.  Project  Smart.  h=p://www.projectsmart.co.uk/docs/chaos-­‐report.pdf    

• 

• • • 

• 

• 

Nivel  1   Nivel  2  

1.  XIII  Jornadas   1.1  Web  1.2  Ponentes  1.3  Asistentes  1.4  Infraestructura  

• • • 

• 

• 

• 

Verbo NombreDiseñar  un  sito  web Diseño  del  siSo  web

Seleccionar  herramientas Selección  de  herramientas  

Escribir  capítulo  4 Capítulo  4

Integrar Integración

P

• 

• 

² ² 

² ² ² 

• 

• 

• • • 

Out of Scope for this timeframe

Must Have

Should Have

Could Have

Won’t have this time

Maybe next time

Requirements that cannot be de-scoped without causing the project to fail

Minimum Usable SubseTGuaranteedNo more than 60% effort

Work arounds difficult/costly

Requirements that can be de-scoped as a last resort to keep the project on track

Expected@ 20% effort

Work around easy/cheap

Requirements that can be de-scoped without causing significant problems

Possibly@ 20% effort

Fuente:    h=p://growingagile.co.za/2013/07/importance-­‐versus-­‐value/?utm_source=rss&utm_medium=rss&utm_campaign=importance-­‐versus-­‐value    

Diagrama  de  una  bicicleta.  Autor:  Al2