Bibliographic citations
This is an automatically generated citacion. Modify it if you see fit
Diaz, M., Miranda, N. (2018). Gestión de proyectos scrum y producción de trajes de luces caso: “K’anchari Trajes Típicos” . [Tesis, Universidad Andina del Cusco]. https://hdl.handle.net/20.500.12557/2267
Diaz, M., Miranda, N. Gestión de proyectos scrum y producción de trajes de luces caso: “K’anchari Trajes Típicos” . [Tesis]. : Universidad Andina del Cusco; 2018. https://hdl.handle.net/20.500.12557/2267
@misc{renati/24040,
title = "Gestión de proyectos scrum y producción de trajes de luces caso: “K’anchari Trajes Típicos” .",
author = "Miranda Mondragón, Nataly Claudia",
publisher = "Universidad Andina del Cusco",
year = "2018"
}
Title: Gestión de proyectos scrum y producción de trajes de luces caso: “K’anchari Trajes Típicos” .
Authors(s): Diaz Zevillanos, Marisé; Miranda Mondragón, Nataly Claudia
Advisor(s): Molero Delgado, Iván
Issue Date: 8-Nov-2018
Institution: Universidad Andina del Cusco
Abstract: La investigación realizada se basa en organizar la empresa elegida de acuerdo a la
metodología de gestión de proyectos scrum que permitirá proponer una nueva organización
en los procesos para la obtención de indumentarias folclóricas llamadas por los
propietarios trajes de luces el cual requiere un arduo trabajo por la misma complejidad de
su elaboración. Las características serán obtenidas de los requerimientos del cliente, esto
último muy importante ya que en scrum las características son tomadas de la perspectiva
del usuario final, estas características conformarán lo que se conoce como historias de
usuario y la colección de todas estas historias son conocidas como backlog del producto.
Una vez obtenido el backlog del producto se dará inicio a la planeación de qué historias de
usuario específicamente se colocará en la liberación del producto. Se realizó una primera
reunión con todos los miembros de la empresa iniciando de este modo el ciclo, reunión
durante el cual se creó la visión del proyecto .El product owner es el encargado de que las
características correctas entren en el backlog del producto, el scrum master, es el
administrador del proyecto, cuyo trabajo consistirá en que todo el proceso sea ligero y que
todos los miembros del equipo cuenten con las herramientas necesarias para realizar sus
tareas, es quien ha de organizar las reuniones.
El resto del equipo tendrá roles para la elaboración del producto en sí. Para planear
la liberación del producto, el equipo deberá contar con el backlog del producto, donde se
identifican las historias de usuario que se quieren dejar en dicha liberación, esas historias
de usuario pasarán a formar parte del release backlog, el equipo priorizará las historias de
usuario y estimará tiempos para cada una de ellas, las historias muy grandes deberán tener
una subdivisión en pequeñas porciones de tiempo para ser más manejables, la colección de
todas estas estimaciones promediarán el tiempo de desarrollo de la selección de historias
con mayor prioridad para llevar a cabo el trabajo, lo más importante es que deberán
finalizar un producto listo para ofertar con todas las características cien por ciento
terminadas.
The research done is based on the choice of a method for the management of projects that allows a new organization in the processes for obtaining folk costumes called by the owners of suits of lights that requires a job for the same complexity of its elaboration. The characteristics of the end user are the characteristics of the end user; these characteristics are compatible with the stories of the user and the collection of all these stories are known as the backlog of the product. Once the product backlog was announced, the start of the planning of what was announced was announced. Specific user stories will be presented in the product release. A meeting was held with all the members of the company, thus initiating the cycle, the meeting during which the vision of the project was created. The owner of the product is in charge of the correct characteristics in the backlog of the product, the master scrum, is the project manager, whose job will be that the whole process is light and that all the members of the team have the necessary tools to perform their tasks, that is, organize the meetings. The rest of the team will have roles for the preparation of the product itself. To plan the release of the product, the team must have the product registration, which identifies the user stories that are to be left in that release, the user stories pass To be part of the release backlog, the team prioritize the user stories and time estimator for each of them, the very large stories have a subdivision into small portions of time to be more manageable, the collection of all these estimates will average the development time of the selection of stories with higher priority to carry out the work, the most important thing is that the promise ends a product ready to bid with all the features one hundred percent completed.
The research done is based on the choice of a method for the management of projects that allows a new organization in the processes for obtaining folk costumes called by the owners of suits of lights that requires a job for the same complexity of its elaboration. The characteristics of the end user are the characteristics of the end user; these characteristics are compatible with the stories of the user and the collection of all these stories are known as the backlog of the product. Once the product backlog was announced, the start of the planning of what was announced was announced. Specific user stories will be presented in the product release. A meeting was held with all the members of the company, thus initiating the cycle, the meeting during which the vision of the project was created. The owner of the product is in charge of the correct characteristics in the backlog of the product, the master scrum, is the project manager, whose job will be that the whole process is light and that all the members of the team have the necessary tools to perform their tasks, that is, organize the meetings. The rest of the team will have roles for the preparation of the product itself. To plan the release of the product, the team must have the product registration, which identifies the user stories that are to be left in that release, the user stories pass To be part of the release backlog, the team prioritize the user stories and time estimator for each of them, the very large stories have a subdivision into small portions of time to be more manageable, the collection of all these estimates will average the development time of the selection of stories with higher priority to carry out the work, the most important thing is that the promise ends a product ready to bid with all the features one hundred percent completed.
Link to repository: https://hdl.handle.net/20.500.12557/2267
Discipline: Ingeniería de Sistemas
Grade or title grantor: Universidad Andina del Cusco. Facultad de Ingeniería y Arquitectura
Grade or title: Ingeniero de Sistemas
Register date: 28-Feb-2019
This item is licensed under a Creative Commons License