05 3-caelum-ramiro carballo cmmi-contexto-agile-v2-reduc

9
CMMI ® SCAMPI en un contexto ÁGIL VIII Semana del CMMI 2013. Madrid, 12-13 de Nov. de 2013 Ramiro Carballo. Certified SCAMPI Lead Appraiser Caelum Information & Quality Technologies, S. L

Transcript of 05 3-caelum-ramiro carballo cmmi-contexto-agile-v2-reduc

Page 1: 05 3-caelum-ramiro carballo cmmi-contexto-agile-v2-reduc

CMMI® SCAMPI en un contexto ÁGIL

VIII Semana del CMMI 2013.

Madrid, 12-13 de Nov. de 2013

Ramiro Carballo. Certified SCAMPI Lead Appraiser

Caelum Information & Quality Technologies, S. L

Page 2: 05 3-caelum-ramiro carballo cmmi-contexto-agile-v2-reduc

© Caelum, - VIII Semana CMMI 2013 Pág. 2

The following service marks and registered marks are used in this document:

Capability Maturity Model. Carnegie Mellon, CERT, CMM, CMMI, CMM Integration, IDEALSM , SCAMPISM,

CMMI, CMM, CERT, CMM Integration, Carnegie Mellon, and Capability Maturity Model are registered in the U.S. Patent and Trademark Office.

SCAMPI and IDEAL are service marks of Carnegie Mellon University.

CMMI® for Development, Version 1.3, was published by Software Engineering Institute in the report CMU/SEI-2010-TR-033, under the Software Engineering Process Management Program. Unlimited distribution subject to the copyright.

Copyright 2010 Carnegie Mellon University. NO WARRANTY: THIS CARNEGIE MELLON UNIVERSITY AND SOFTWARE ENGINEERING INSTITUTE MATERIAL IS FURNISHED ON AN “AS-IS” BASIS. CARNEGIE MELLON UNIVERSITY MAKES NO WARRANTIES OF ANY KIND, EITHER EXPRESSED OR IMPLIED, AS TO ANY MATTER INCLUDING, BUT NOT LIMITED TO, WARRANTY OF FITNESS FOR PURPOSE OR MERCHANTABILITY, EXCLUSIVITY, OR RESULTS OBTAINED FROM USE OF THE MATERIAL. CARNEGIE MELLON UNIVERSITY DOES NOT MAKE ANY WARRANTY OF ANY KIND WITH RESPECT TO FREEDOM FROM PATENT, TRADEMARK, OR COPYRIGHT INFRINGEMENT.

Use of any trademarks in the report CMU/SEI-2010-TR-033 is not intended in any way to infringe on the rights of the trademark holder. Internal use. Permission to reproduce this document and to prepare derivative works from this document for internal use is granted, provided the copyright and “No Warranty” statements are included with all reproductions and derivative works. External use. This document may be reproduced in its entirety, without modification, and freely distributed in written or electronic form without requesting formal permission. Permission is required for any other external and/or commercial use. Requests for permission should be directed to the Software Engineering Institute at [email protected].

CMMI was created in the performance of Federal Government Contract Number FA8721-05-C-0003 with Carnegie Mellon University for the operation of the Software Engineering Institute, a federally funded research and development center. The Government of the United States has a royalty-free government-purpose license to use, duplicate, or disclose the work, in whole or in part and in any manner, and to have or permit others to do so, for government purposes pursuant to the copyright license under the clause at 252.227-7013. For information about SEI publications, please visit the library on the SEI website (www.sei.cmu.edu/library).

Page 3: 05 3-caelum-ramiro carballo cmmi-contexto-agile-v2-reduc

© Caelum, - VIII Semana CMMI 2013 Pág. 3

Cuestión de negocio…

Director Comercial de una organización ágil:

EL CLIENTE NOS HA PEDIDO…

…CMMI300 evaluaciones CMMI en España hasta Junio 20134ª posición a nivel mundial tras China, USA e India

Page 4: 05 3-caelum-ramiro carballo cmmi-contexto-agile-v2-reduc

© Caelum, - VIII Semana CMMI 2013 Pág. 4

Sin miedo: Nuestra experiencia …

En las organizaciones con cultura ágil, encontramos menos debilidades

al evaluar sus procesos

En las organizaciones con procesos “pesados”, la adherencia a los

proyectos es incompleta

Page 5: 05 3-caelum-ramiro carballo cmmi-contexto-agile-v2-reduc

© Caelum, - VIII Semana CMMI 2013 Pág. 5

Nuestra recomendación …

Si un cliente es competitivo antes de “llegar CMMI”, no lo debería ser menos

después

Si no te es útil, seguro que hay otra manera de hacerlo

Page 6: 05 3-caelum-ramiro carballo cmmi-contexto-agile-v2-reduc

© Caelum, - VIII Semana CMMI 2013 Pág. 6

Requirement Management (REQM)Propósito

Manage requirements of the project’s products and product components and to ensure alignment between those requirements and the project’s plans and work products.

Objetivos y Prácticas Específicos

SG1 Manage Requirements

SP 1.1 Understand Requirements SP 1.2 Obtain Commitment to RequirementsSP 1.3 Manage Requirements Changes SP 1.4 Maintain Bidirectional Traceability of RequirementsSP 1.5 Ensure Alignment Between Project Work and Requirements

EJEMPLO:

Área de Proceso

Propósito

Meta

Prácticas

Page 7: 05 3-caelum-ramiro carballo cmmi-contexto-agile-v2-reduc

© Caelum, - VIII Semana CMMI 2013 Pág. 7

Ejemplos de la evaluación de un cliente ágil (I)

PP SP 1.1 Estimate the Scope of the ProjectSe utiliza el product backlog para relacionar tareas pendientes, soportado por la herramienta JIRA, y se utiliza para estimar.

Se mide el tamaño funcional en puntos historia.

PP SP 1.2 Establish Estimates of WP and Task Attributes

Se lleva a cabo la imputación directa de los recursos a las tareas en JIRA, lo que permite monitorizar los valores reales de los parámetros de planificación del proyecto frente al plan. Permite identificar las desviaciones significativas.

PMC SP 1.1 Monitor Project Planning Parameters

Page 8: 05 3-caelum-ramiro carballo cmmi-contexto-agile-v2-reduc

© Caelum, - VIII Semana CMMI 2013 Pág. 8

Ejemplos de la evaluación de un cliente ágil (II)

PMC SP 1.6 Conduct Progress ReviewsPMC SP 2.1 Analyze Issues

PMC SP 2.2 Take Corrective Action

PMC SP 2.3 Manage Corrective Actions

Se documenta la retrospectiva, donde se reflejan las incidencias o problemas detectados durante el seguimiento del proyecto.

Se definen acciones correctivas que pretenden solucionar las incidencias del proyecto y se dejan reflejadas en JIRA como una tarea.

El seguimiento periódico incluye la revisión de las acciones correctivas incorporadas en la retrospectiva para asegurar su cierre.

Se utiliza un plugin de pizarra en JIRA que permite registrar el estado de las peticiones de cambio y las clasifica en evolutivas o correctivas.

REQM SP 1.3 Manage Requirements Changes CM SP 2.1 Track Change Requests

Page 9: 05 3-caelum-ramiro carballo cmmi-contexto-agile-v2-reduc

© Caelum, - VIII Semana CMMI 2013 Pág. 9

Ramiro Carballo Gutiérrez Certified SCAMPI v.1.3 Lead Appraiser( ID# 1201018-03 )CMMI for DevelopmentCMMI for [email protected]óv.: 639078817

www.linkedin.com/in/ramirocarballo

Caelum Information & Quality Technologies, S. L.Paseo de las Delicias 38, 1º Dcha.28045 Madridwww.caelum.eswww.CalidaddelSoftware.comTlf.: 918312029