Examen Sm - Simulador

The Product Owner is responsible for representing the voice of the customer and ensuring maximum business value in the project. They prioritize and manage the product backlog, work closely with stakeholders, and make decisions on what features and functionality should be included in the final product. In this scenario, the Product Owner would be responsible for ensuring that the project delivers the desired results for the client and maximizes the value of the $50 million investment.

The Scrum Master is responsible for ensuring that any environmental obstacles that could impact the quality of deliverables or processes are eliminated. This role involves facilitating the team's progress by removing any barriers or impediments that may hinder their work. The Scrum Master acts as a facilitator, helping to create a productive and efficient working environment for the team. They support collaboration, communication, and problem-solving within the Scrum framework.

The principle of Scrum regarding empirical process control is based on three main ideas: adaptation, inspection, and transparency. These ideas emphasize the importance of continuously evaluating and adjusting the process based on empirical evidence. However, "velocity" is not a concept related to empirical process control in Scrum. Velocity refers to the measure of work completed by a team in a given time frame and is used for planning and forecasting, but it is not directly related to the empirical control of the process.

Como Scrum Master de programa, su responsabilidad principal es facilitar y enseñar las prácticas de Scrum a todos los involucrados del programa. Esto implica asegurarse de que todos comprendan y sigan los principios y valores de Scrum, así como ayudar a resolver cualquier problema o obstáculo que puedan encontrar en la implementación de Scrum. El Scrum Master también actúa como coach y facilitador, ayudando al equipo a mejorar continuamente su rendimiento y adoptar las mejores prácticas ágiles.

The question asks for the objective that is not part of a retrospective meeting. The objective "Identificar a los miembros del equipo que fueron vitales" (Identify the team members who were vital) does not align with the typical objectives of a retrospective meeting, which are to identify things to continue doing, things to stop doing, and things to start doing in order to improve the team's performance.

The given correct answer is "Scrum Guide Body". In the process of refining the prioritized product backlog, the Product Owner can refer to the Scrum Guide Body for guidance. The Scrum Guide is a comprehensive document that provides a framework for implementing Scrum, including guidelines and best practices. The Scrum Guide Body serves as a reference for understanding the roles, events, artifacts, and rules of Scrum. By following the Scrum Guide, the Product Owner can ensure that the backlog refinement process aligns with the principles and values of Scrum.

La reunión de retrospectiva del proyecto es una reunión en la metodología Scrum donde el equipo reflexiona sobre el proyecto y busca formas de mejorar la colaboración y efectividad en el futuro. En esta reunión se revisan los procesos, las herramientas y las interacciones del equipo para identificar qué funcionó bien y qué se puede mejorar.

If the deliverables of a sprint do not meet the defined acceptance criteria, they are not considered accepted and usually carried over to a subsequent sprint to rectify any issues.

La reunión de planificación financiera no ayuda al equipo Scrum a identificar o resolver riesgos porque su objetivo principal es discutir y planificar los aspectos financieros del proyecto, como el presupuesto y los costos. Si bien es importante para la gestión del proyecto, esta reunión no está directamente relacionada con la identificación y resolución de riesgos específicos del equipo Scrum.

"Entregables aceptados" se refiere a las historias de usuario que han cumplido con los criterios de aceptación establecidos y han sido aceptadas por el Product Owner. Esto significa que estas historias han sido revisadas y aprobadas como satisfactorias para su entrega y cumplen con los requisitos y expectativas del cliente. El Product Owner tiene la responsabilidad de determinar si una historia de usuario cumple con los criterios de aceptación y si está lista para ser entregada al cliente.

Un Scrum Master eficiente debe tener habilidades para mantener un ambiente laboral conductivo, habilidades para operar como líder servicial y habilidades para resolver problemas. Sin embargo, no se espera que tenga habilidades para trabajar en códigos complejos, ya que su rol se centra más en la gestión del equipo y en facilitar el proceso de desarrollo, en lugar de estar directamente involucrado en la codificación.

The retrospective meeting is incorrectly assigned a time-box of 8 hours according to Scrum. In Scrum, the retrospective meeting is typically time-boxed to 3 hours for a one-month sprint. The purpose of the retrospective meeting is to reflect on the sprint and identify areas for improvement, and a longer duration may lead to inefficiency and lack of focus. Therefore, assigning a time-box of 8 hours to the retrospective meeting goes against Scrum principles.

If a deliverable does not meet the defined acceptance criteria, it is not considered accepted and usually carried over to the next sprint. This statement aligns with the explanation provided in the given text, which states that if an deliverable does not meet the acceptance criteria, it cannot advance to the next sprint for rectification. Therefore, the correct answer is "Si un entregable no cumple con los criterios de aceptaciön definidos, no se considera aceptado y, por lo general, se lleva a un siguiente sprint."

The correct answer states that the items of higher value, even though they may be potentially risky, receive higher priority in the Prioritized Product Backlog. This means that the Product Owner should prioritize the items that provide the most value to the customer or stakeholders, even if they come with some level of risk. By doing so, the team can focus on delivering the most valuable features first and manage the associated risks accordingly.

The question asks which Scrum project would be very useful for the company Atlas Tech, which has many products in its portfolio. The options provided are a security vault software, an image editing software, and a financial manager software for a commercial bank with changing security requirements. Since the company has a diverse portfolio and would benefit from all of these projects, the correct answer is "Todas las anteriores" (All of the above).

In Scrum, the estimation of user stories is typically done by the Scrum team. The Scrum team consists of the Product Owner, Scrum Master, and the Development Team. The team collectively estimates the effort required to complete each user story during the Sprint Planning meeting. This estimation helps in prioritizing and planning the work for the upcoming sprint. The Product Owner provides guidance and clarifications on the user stories, but the actual estimation is done by the Scrum team.

El rol del Product Owner generalmente se le denomina "la voz del cliente" porque su principal responsabilidad es representar los intereses y necesidades del cliente en el desarrollo del producto. Además, el rol del PO es asegurar el máximo valor de negocio para el proyecto, comunicando los requerimientos del cliente al equipo de desarrollo. Sin embargo, el rol del PO no actúa como moderador en las reuniones del equipo. Esta función suele ser desempeñada por el Scrum Master, quien facilita y guía las reuniones del equipo.

Andy, as a Scrum Master, helps his team in creating a Sprint Backlog. This process falls under the phase of "Planificación y estimación" (Planning and estimation) in Scrum. In this phase, the team collaboratively decides on the work that needs to be done in the upcoming sprint and estimates the effort required for each task. This helps in setting clear goals and priorities for the sprint, ensuring that the team is aligned and has a shared understanding of the work to be accomplished.

The correct answer is "El equipo de desarrollo ha estado funcionando efectivamente sin mucha intervención o supervisión." This situation aligns with the Scrum framework because in Scrum, the development team is self-organizing and empowered to make decisions without constant supervision. They are responsible for planning and executing the work, and they collaborate closely with the Scrum Master and Product Owner. This scenario indicates that the development team is functioning effectively and autonomously, which is a characteristic of Scrum.

El Scrum Master facilita las reuniones del taller de historias de usuario en un proyecto de software. El Scrum Master es responsable de asegurar que el equipo de Scrum siga las prácticas y principios de Scrum, y ayuda a facilitar la comunicación y colaboración entre el equipo y el Product Owner. En el contexto de este proyecto, el Scrum Master se encarga de asegurar que el taller de historias de usuario sea efectivo y ayude al Product Owner a priorizar los requerimientos de manera adecuada.

Juan should inform the Scrum Master about the situation, who can then discuss the situation with Carlos and the Product Owner. This is the appropriate action because the Scrum Master is responsible for ensuring the smooth functioning of the Scrum team and resolving any issues that may arise. By informing the Scrum Master, Juan can ensure that the situation is addressed and the necessary actions are taken to mitigate any impact on the current sprint.

During an ongoing sprint, it is important that the acceptance criteria of a user story are not modified or changed. The Scrum Master is responsible for ensuring that such changes do not occur during a sprint. They facilitate the Scrum process and ensure that the team adheres to the agreed-upon rules and guidelines. They also act as a mediator between the team and the product owner, making sure that the product backlog is properly managed and that any changes to the acceptance criteria are properly communicated and discussed.

A team that is self-organized focuses on collective responsibility and shared ownership rather than individual performance tracking. The emphasis is on collaboration and teamwork, where the team members work together towards achieving the project goals. Therefore, the statement "Mejor seguimiento del desempeño individual de miembros del equipo" is not a result of a self-organized team.

During the Scrum of Scrums meeting, the Chief Product Owner convenes to address obstacles that affect more than one Scrum team. The question "¿Qué Falta por hacer en nuestro equipo y quién tiene que hacerlo?" (What is left to do in our team and who has to do it?) is not one of the questions asked during this meeting. The Scrum of Scrums meeting focuses on discussing what each team has been working on since the last meeting, what they plan to do until the next meeting, and what they plan to do that could affect other teams.

El hecho de que los equipos estén ubicados físicamente en el mismo lugar no es una característica esencial de un Equipo de Scrum. Aunque la co-ubicación puede facilitar la comunicación y la colaboración, Scrum permite que los equipos trabajen de manera distribuida, utilizando herramientas y tecnología para mantenerse conectados. En cambio, las características esenciales de un Equipo de Scrum incluyen ser interfuncionales, auto-organizados y motivados para lograr los objetivos del proyecto.

The Chief Scrum Master is responsible for ensuring that there is a forum for the timely and appropriate exchange of information between teams in large projects. They oversee the coordination and communication between multiple Scrum teams, ensuring that the necessary information is shared effectively. This role is specifically focused on managing the overall program or portfolio of projects, making them the most suitable person to ensure the smooth flow of information between teams.

In Scrum, the participation of the client is high throughout the project, meaning that the client is actively involved in the decision-making process and providing feedback. On the other hand, in traditional project management, the level of client participation varies depending on the project's lifecycle. This means that in traditional project management, the client's involvement may be limited to certain stages or milestones of the project.

El Scrum Master sugeriría el uso de listas de verificación de riesgos (Risk Checklists) para una identificación integral de riesgos en un proyecto de una aplicación bancaria. Las listas de verificación de riesgos son herramientas que permiten al equipo identificar de manera sistemática y exhaustiva los posibles riesgos que podrían afectar el proyecto. Estas listas contienen una serie de preguntas o ítems relacionados con diferentes aspectos del proyecto, lo que ayuda a asegurar que no se pasen por alto posibles riesgos importantes. Al utilizar estas listas, el equipo puede identificar y evaluar los riesgos de manera más efectiva, lo que les permite tomar medidas preventivas o mitigadoras oportunamente.

The Scrum Master can help the Scrum Team achieve the goal of developing an Effort Estimated Task List by acting as a moderator and removing any obstacles during the estimation meetings. By facilitating the discussion and ensuring that everyone has a chance to share their perspectives on user stories and requirements, the Scrum Master can help the team come to a consensus on the effort required for each task. Additionally, by addressing any impediments that may arise during the estimation process, the Scrum Master can ensure that the team can accurately estimate tasks and create a realistic task list.

Las épicas se fragmentan en historias de usuario más pequeñas durante un sprint porque son demasiado grandes para completarse en un sprint. Al dividir las épicas en historias de usuario más pequeñas, se pueden abordar de manera más manejable y se pueden completar en un período de tiempo más corto. Esto permite una mayor visibilidad y control sobre el progreso del proyecto, así como una entrega más rápida y frecuente de valor al cliente.

The correct answer is "Auto-organización, Priorización basada en valor, Colaboración." These three principles of Scrum are essential for the Scrum Master to ensure the successful implementation of the Scrum framework in projects. Auto-organización refers to the self-organization of the Scrum team, allowing them to decide how to best accomplish their work. Priorización basada en valor means prioritizing work based on its value to the customer, ensuring that the most valuable tasks are completed first. Colaboración emphasizes the importance of teamwork and collaboration within the Scrum team and with stakeholders to achieve project goals.

The given correct answer is "Comparación por pares" because in this method, each user story is compared with other user stories one by one, and a decision is made about which one is more important. By repeating this process, a prioritized list of user stories can be generated. This method involves pairwise comparison of user stories to determine their relative importance.

The Burndown Chart is a visual representation of the work remaining in a sprint. It shows the progress of the team towards completing the planned work and helps to track any deviations from the plan. By using the Burndown Chart, the team and stakeholders can have a transparent view of the project's progress, which promotes transparency in Scrum. The chart allows everyone to see how much work is left, how well the team is performing, and any potential obstacles or issues that may arise. This promotes open communication and collaboration within the team and with stakeholders, ensuring transparency in the project.

not-available-via-ai

The correct answer is "Como (rol), yo debería (requerimiento), a fin de (beneficio)." This format follows the standard structure for writing user stories in Agile development. It starts with the role or persona of the user, followed by the requirement or action they need to perform, and ends with the benefit or goal they want to achieve. This format helps to clearly define the user's perspective and the purpose of the story.

The correct sequence of stages in the Tuckman Model of group dynamics is formation, storming, norming, and performing. In the formation stage, team members come together and begin to understand their roles and responsibilities. This is followed by the storming stage, where conflicts and disagreements may arise as team members establish their individual identities. The norming stage is where the team starts to establish norms and rules for working together effectively. Finally, in the performing stage, the team is able to work together cohesively and achieve their goals.

La opción "Identificar mejoras a las características" no es uno de los objetivos de una reunión de retrospectiva del sprint porque esta reunión se enfoca principalmente en evaluar y mejorar el proceso de trabajo del equipo, no en mejorar las características o funcionalidades específicas del producto o proyecto. Los otros objetivos mencionados, como identificar mejoras al proceso, identificar las mejores prácticas y identificar problemas con el proceso y embotellamientos, están más alineados con el propósito de una reunión de retrospectiva del sprint.

La planificación detallada por adelantado no es un beneficio de la implementación de Scrum porque en Scrum se enfatiza en la adaptabilidad y la capacidad de respuesta a los cambios. En lugar de realizar una planificación detallada por adelantado, Scrum fomenta la planificación iterativa y flexible, donde los cambios pueden ser incorporados fácilmente durante el desarrollo del proyecto. Esto permite que el equipo se adapte rápidamente a los cambios en los requisitos o prioridades del proyecto, lo que aumenta la eficiencia y la satisfacción del cliente.

The correct answer is that the Scrum team is a self-organized unit, so Santiago and Gerardo should resolve the issue with the help of the other team members. In Scrum, the team is responsible for solving conflicts and making decisions collectively. The Scrum Master's role is to facilitate the resolution process, but the ultimate responsibility lies with the team. Therefore, it is important for Santiago and Gerardo to work together, seek input from other team members, and find a resolution that is agreeable to everyone.

The given scenario describes a situation where the Scrum Team has developed a code for tracking bus movements as part of a $50 million public transportation project. However, during testing, it was found that the code was complex, time-consuming, and redundant. The team has decided to redesign the code while ensuring that all functionality is preserved and making it more sustainable. This process of restructuring and improving the code without changing its functionality is known as refactoring.

En la fase de inicio de Scrum, uno de los procesos es identificar al Scrum Master y stakeholders. Esto implica seleccionar a la persona adecuada para el rol de Scrum Master, quien será responsable de liderar y facilitar el proceso Scrum. También implica identificar a los stakeholders, que son las partes interesadas en el proyecto y que tendrán un papel importante en la toma de decisiones y en la definición de los requisitos del producto. Esta identificación temprana de los roles clave ayuda a establecer una base sólida para el proyecto y a garantizar una comunicación efectiva desde el principio.

A Scrum Master can use a Burndown Chart to represent the actual process compared to the planned process of a team. A Burndown Chart visually displays the amount of work remaining over time, allowing the team to track their progress and identify any deviations from the planned process. It helps the Scrum Master and the team to understand if they are on track to meet their goals and make any necessary adjustments to ensure successful project completion.

El Scrum Master tiene varias responsabilidades, como coordinar la creación del Cronograma de planificación del lanzamiento, facilitar las reuniones de revisión del Backlog Priorizado del Producto y representar al equipo central de Scrum para proporcionar lecciones del proyecto. Sin embargo, refinar el Backlog Priorizado del Producto no es una de las responsabilidades del Scrum Master. Esta tarea generalmente es realizada por el Product Owner y el equipo de desarrollo.

This scenario exemplifies tolerance to risk because the Product Owner is willing to accept a certain level of defects in the product, as long as it is still acceptable to the customer. However, there is a limit to the number of defects that can be tolerated, as exceeding that limit would result in the rejection of the deliverables. Tolerance to risk refers to the level of risk that an organization or individual is willing to accept before taking action. In this case, the Product Owner is willing to tolerate some level of defects but has set a limit to the number of defects that can be accepted.

Demostrar prototipos y simular funcionalidades a los clientes es una técnica utilizada para confirmar el valor de los entregables del proyecto. Al mostrar prototipos y simular funcionalidades, el Scrum Master puede obtener retroalimentación directa de los clientes y verificar si los resultados esperados del proyecto cumplen con sus expectativas. Esto ayuda a garantizar que los beneficios y el valor definidos al inicio del proyecto se estén logrando correctamente.

The Scrum Master plays a crucial role in ensuring that a sustainable pace is maintained within the team. This means that the Scrum Master is responsible for monitoring and managing the team's workload, making sure that they are not overburdened or underutilized. By maintaining a steady rhythm, the Scrum Master helps to optimize productivity and prevent burnout. This responsibility is essential in maintaining the overall quality of the team's work and ensuring that they can consistently deliver value.

The correct answer is "La velocidad del equipo es el número total de puntos de historias completados en un sprint." This is because the velocity of a team is typically measured by the number of story points they have completed in a sprint. Story points are a way to estimate the effort required to complete a user story, and tracking the number of story points completed can help determine the team's productivity and predictability.

The Scrum Guidance Body is responsible for providing guidance and support to the Scrum Team. This includes ensuring that any issues or conflicts among team members are resolved before the start of a sprint, as lack of coordination can lead to technical debt. Additionally, the Scrum Guidance Body can also include documentation and process definitions that help in reducing technical debt. This means that they can provide resources and guidelines to the team to address any technical debt that may arise during the development process.

The question "En su equipo que falta por terminar?" is not a question that is typically answered during a Scrum of Scrums meeting. The Scrum of Scrums meeting is a meeting where representatives from different Scrum teams come together to discuss their progress, dependencies, and any issues or obstacles that may affect multiple teams. The focus is on coordination and alignment between teams, rather than discussing individual team tasks or work that is yet to be completed.

The question asks for the factor that is NOT considered during business justification. The other three options - Costo de oportunidad (opportunity cost), Costo del proyecto (project cost), and Costos de desarrollo (development costs) are all factors that are typically considered during business justification. Therefore, the correct answer is Costos evitables (avoidable costs), as it is not mentioned as a factor to consider during business justification.