espanolObjetivo: Presentar un modelo de referencia que facilite la comprension e inplementacion de Scrum en las organizaciones software. Metodologia o metodo: El diseno del modelo se fundamento a partir de la comparacion e identificacion de los elementos fundamentales de las guias agiles existentes mas utilizadas en la industria de software. Se utilizo tambien el paradigma GQM (Goal-Question-Metric), este permitio detallar el modelo de referencia a traves de un conjunto claro y completo de elementos de proceso, asi como: fases, actividades, roles, resultados esperados/satisfactorios y flujos de proceso en BPMN. Usar el paradigma GQM permite que el modelo sea extendido en un futuro con el diseno de un instrumento de valoracion/evaluacion que permita medir el grado del cumplimiento de Scrum. La evaluacion del modelo se llevo a cabo a traves de un grupo focal, donde se evaluo la pertinencia, claridad y completitud de la propuesta, el grupo focal estuvo conformado por participantes expertos en Scrum. Resultados: Se evidencio que los participantes consideran que el modelo propuesto es completo, idoneo y claro, y que este facilitaria la comprension, adopcion y evaluacion de Scrum. Conclusiones: En definitiva, se propone un modelo que sugiere seis (6) fases, veintinueve (29) actividades, cinco (5) roles y otros elementos de proceso que permitirian guiar a los profesionales y organizaciones a minimizar la subjetividad en la comprension y adopcion de Scrum. Como trabajo futuro, se espera definir un instrumento de evaluacion basado en el modelo de referencia aqui presentado, que permita evaluar el grado de cumplimiento de Scrum. EnglishObjective: Present a reference model that facilitates the understanding and implementation of Scrum in software organizations. Methodology or method: The design of the model was based on the comparison and identification of the fundamental elements of the existing agile guides most used in the software industry. Likewise, the GQM (Goal-Question-Metric) paradigm was used, which allowed detailing the reference model through a clear and complete set of process elements, as well as: phases, activities, roles, expected / satisfactory results and flows process in BPMN. Using the GQM paradigm allows the model to be extended in the future with the design of an assessment / evaluation instrument that allows measuring the degree of Scrum compliance. The evaluation of the model was carried out through a focus group, where the relevance, clarity and completeness of the proposal was evaluated, the focus group was made up of participants who are experts in Scrum. Results: It was evident that the participants consider that the proposed model is complete, suitable and clear, and that it would facilitate the understanding, adoption and evaluation of Scrum. Conclusions: In short, a model is proposed that suggests six (6) phases, twenty-nine (29) activities, five (5) roles and other process elements that would allow professionals and organizations to be guided to minimize subjectivity in understanding and adopting Scrum. As future work, it is expected to define an evaluation instrument based on the reference model presented here, which allows evaluating the degree of Scrum compliance.