0 calificaciones0% encontró este documento útil (0 votos)
4 vistas2 páginas
Las reuniones descritas tienen como propósito planificar y gestionar el proceso Scrum para un proyecto mediante la creación y priorización de historias de usuario en el tablero de producto, la asignación de tareas a Sprints, y la revisión continua del progreso para mejorar el producto y el proceso iterativamente.
Descripción original:
explicaicón de las principales reuniones que se llevan acabo dentro de SCRUM
Las reuniones descritas tienen como propósito planificar y gestionar el proceso Scrum para un proyecto mediante la creación y priorización de historias de usuario en el tablero de producto, la asignación de tareas a Sprints, y la revisión continua del progreso para mejorar el producto y el proceso iterativamente.
Las reuniones descritas tienen como propósito planificar y gestionar el proceso Scrum para un proyecto mediante la creación y priorización de historias de usuario en el tablero de producto, la asignación de tareas a Sprints, y la revisión continua del progreso para mejorar el producto y el proceso iterativamente.
User Story PO, SHs, SM Write many “one- High-level PB with User Stories Workshop liner” stories requirements classifieds as themes regular, epics and as functional defines themes requirements Prioritization, Buy PO, SHs, SM, Compare relative Define priority Functional PB (User the future priority in terms and order of User Stories) with priority of business value Stories order and determine order Add additional PO, SM, Team Add Complement Expanded PB with PBIs infrastructure functional altered order PBIs including requirements (dependencies) ordering or with additional interlacing with work User Stories Planning Poker PO, SM, Team Compare selected Determine PB with relative sizes PBIs to a relative size of a reference story selected number of PBIs (could be all PBIs) Architectural PO, SM, Team, or Analyze each Provide high-level User Stories with Scan selected story (epics or logical architectural patterns members of regulars), and architectural in notes Team determine guidance architectural or design patterns Release Planning PO, SM, Team Order and assign Agree to contents PB with tentative PBIs PB to different of MVP for next assigned for the Sprints using release Sprints business value, dependencies and capability User Acceptance PO, SM, SHs Add UATs to PB Elaborate User Stories with Grooming typically users, for 1-3 Sprints = functional UATs Team grooming 1 requirements through UATs Sprint Planning PO, SM, Team Agree to PBIs for Finalize the Sprint PB, tasks for it a Sprint, contents and goal Volunteer for of a Sprint. Build work, provide a product tasks for Sprint increment. Backlog == Isolate work for grooming 2 the team. Daily Scrum SM, Team Answer 3 Provide empirical Collaborations among questions: what process team members, up- did you do? management for to-date Sprint Backlog What will you do how to with new implement PBIs estimates? What issues or impediments? Sprint Review PO, Team, SM, Review or Provide assurance PBIs in the Sprint that SHs demonstrate to the PO that need more work contents of the progress has been Sprint made, provide positive reinforcement to the team Retrospective Team, SM Provide input on Allow the team to List of proposed what worked, and improve by self- improvements as PBIs what could be analysis to present to the PO improved PB Refactoring PO, SM Add or modify Retargeting the Modified PB PBIs in backlog project: Provide with new content, empirical process sizes and management for priorities WHAT to do next