¿Cómo se aplican los valores de Scrum en eventos y ceremonias?

Sprint Planning: Commitment - Team members' acceptance to accomplishing the Sprint Goal based on available capacity is the proof of their commitment Focus - It helps in the creation of necessary or relevant tasks and assists the team to ensure the work breakdown of user stories. Courage - Before committing to sprint goals, it requires courage to bring up any dependencies, risks, or differences on deliverables by team members Respect - Every team member perspective are treated with respect, creating a welcoming culture that encourages collaboration Openness - Transparency is promoted by openness, which encourages everyone to discuss their views and concerns related to sprint goals that has potential to impact the schedule / delivery

Sprint Planning >Plan in detail and collaboratively Daily Scrum > Update the team daily and help others or take help when needed. Sprint Review > Showcase your work to stakeholders best way possible. Take feedback, and suggestions from the stakeholders respectfully and take proper notes. Sprint Retrospective > Make collaborative and open-minded retrospectives. Suggest improvement and praise good things. Understand and respect each other emotions. And find out individual and team scope of improvement. Backlog Refinement > Make good communication channels with stakeholders, the team and refine backlog collaboratively, and share respectfully if is there any concern.

During Sprint Planning: 1. Commitment is evident as team members dedicate themselves to achieving the Sprint Goal. 2. Courage is demonstrated as they openly discuss challenges and risks, promoting an environment of honest dialogue. 3. Focus directs discussions toward the most valuable tasks, ensuring alignment with the goal. 4. Openness encourages everyone to share insights and concerns, promoting transparency. 5. Respect is demonstrated as all ideas are valued, creating an inclusive atmosphere that nurtures collaboration.

Sprint planning is an event in scrum that kicks off the sprint. The purpose of sprint planning is to define what can be delivered in the sprint and how that work will be achieved. Sprint planning is done in collaboration with the whole scrum team.

During the Sprint Planning event, the team selects work for the upcoming sprint, embodying commitment by agreeing on a realistic and achievable Sprint Goal. Focus is maintained as the team plans how to achieve the goal, breaking down tasks and assigning them. Openness is key, as team members discuss potential obstacles and dependencies. Respect is shown as each member's opinion and expertise are valued and considered in the planning process. Courage is evident when team members speak up about concerns or when they advocate for realistic expectations, ensuring the sprint’s success.

Daily Standup / Daily Scrum Commitment - It shows daily participation, and updating individual progress enables us to gauge our progress toward sprint goals Focus - Focus enables us to assess whether we are making progress toward our sprint goals Courage - As team member's honestly discuss their struggles, courage emerges, encouraging a culture of tracking and solving problems effectively Respect -Each team member's assignment status is available to all, and their contribution to the sprint goal is valued. Openness -It enables team members' sharing of their accomplishments and challenges to the right stakeholders, increasing transparency

If risks are uncovered in the project, it needs to be discussed and planned in the daily scrum. This standup should not focuses on solving the risks but to plan for mitigation or assessing the risk. The more details and planning for risks can be further discussed in the sprint planning or in the retrospective meetings.

This is a daily opportunity for the Scrum team, the developers in particular, to exercise commitment by consistently participating and sharing updates. Focus is maintained as each member briefly states what they did, what they will do, and any impediments they face. Openness is essential for discussing challenges and seeking help. Respect is demonstrated by listening to others and valuing their contributions. Courage comes into play when admitting difficulties or delays, fostering a supportive environment for problem-solving.

During Daily Scrum: 1. Commitment manifests as team members pledge to achieve the Sprint Goal, ensuring collective progress. 2. Courage shines as they openly share obstacles, promoting a culture of honest problem-solving. 3. Focus guides discussions toward the day's plan, aligning efforts with the goal. 4. Openness supports team members to communicate their progress and needs, promoting transparency. 5. Respect blooms as everyone listens attentively and values each contribution, creating an environment of inclusivity.

Daily Scrum- A time boxed event for the Scrum Team to inspect, participate and discuss on the progress towards the Sprint Goal. We can incorporate Scrum Values in Daily Scrum in the following ways. 1. Commitment- The team needs to commit to produce an actionable plan for the next day so the team can be closes to Sprint Goal. 2. Focus- Team need to focus on the progress towards the goal. 3. Respect- The team needs to respect others opinions, suggestions and insights and also time. 4. Openness- the Team needs to be open about any impediments they are facing and voice out any concerns. 5. Courage- The team needs to have courage to ask for help or suggestions, make decisions that will align with the Sprint Goal.

In the Sprint Review, the Scrum team demonstrates what they've accomplished during the sprint. This is an opportunity to embody commitment by showing the completed work, focus by staying on track with the Sprint Goal, openness by sharing successes and challenges, respect for each other's contributions, and courage to discuss what didn’t go as planned. It is also an opportunity for the team to collaborate with stakeholders, receiving feedback that guides the next steps. This mutual respect and open communication ensure that the sprint review is a constructive and forward-looking session.

During Sprint Review: 1. The value of Commitment shines as the team presents the increment, showcasing their dedication to delivering value. 2. Courage comes to the forefront as the team openly discusses challenges and areas for improvement, demonstrating their willingness to tackle difficult topics. 3. Focus remains central as the team aligns their work with the product goal and responds to stakeholder feedback. 4. Openness is palpable as the team transparently shares their accomplishments and setbacks, building trust among stakeholders. 5. Respect thrives as team members genuinely listen to stakeholders, valuing their perspectives and insights.

The sprint review's purpose is to inspect the increment that was developed in that sprint and collect feedback from key stakeholders. The sprint retrospective is to inspect and improve the agile practices that were followed during the sprint. Both are distinct and essential for a Scrum team to function well

Make everyone in the team owner of the sprint goal. but, when it comes to taking the blame you are the owner. The review went well, then it was a team effort. Bonus: When shielding the team they should what are they being shielded from. This give them perspective of what's going on.

Das Review ist Showtime! Hier zeigst du, was du geschafft hast. Sei stolz darauf, aber auch ehrlich, wenn noch was fehlt. Nimm das Feedback der Leute ernst – die bringen oft gute Ideen, wie's noch besser geht.

Sprint Retrospective Ceremony Commitment - The team's commitment to consistently improving their processes through the action items Focus - It helps team members to focus on Rose, Bud & thorns that helps to bring tangible process improvements in upcoming sprints Courage - Open discussions about what worked well and what needs improvement are sparked by courage and promote growth Respect - Respect drives every interaction during the retrospective, fostering a culture where varied perspectives are respected and from which the team can extract tangible improvements Openness - In order to have productive conversations, it fosters an appropriate atmosphere for the exchange of ideas Retrospective documentation on the Miro Board is encouraged

The Sprint Retrospective is a time to reflect on the past sprint. Commitment to continuous improvement is the cornerstone of this ceremony. The team discusses what went well and what didn’t, maintaining a focus on process improvement. Openness is critical as team members share their honest opinions and feelings about the past sprint. Respect is shown by valuing everyone's input and experience and creating a safe space for feedback. Courage is needed to address difficult issues and propose changes, even if they are challenging or uncomfortable.

A sprint retrospective is a type of meeting within the Agile framework that happens at the end of a sprint. During a sprint retrospective, teams reflect on what went well and what could be improved for their next sprint.

During Sprint Retrospective: 1. Commitment is evident as the team pledges to continuously improve their processes. 2. Courage drives open discussions about what worked well and what needs enhancement, fostering growth. 3. Focus directs the team's attention to the most impactful improvements, ensuring their efforts align with their goals. 4. Openness promotes a safe space for sharing ideas and feedback, enabling constructive conversations. 5. Respect underscores every interaction, creating an environment where diverse perspectives are valued. Instilling the Scrum values during the Sprint Retrospective empowers the team to refine their practices and elevate their collective performance.

Retrospective: Inspect, adapt, and move on. It's always a process to be blamed and change the game plan. People can do wonders until they have the courage to adapt to the changes.

The team reviews and revises the product backlog, with a focus on ensuring that the backlog items are clear, prioritized, and ready for future sprints. It is the team's collective commitment to the product's vision and goals that guides this process. Openness in discussing the complexities of backlog items ensures a well-understood and actionable backlog. Respect for the Product Owner’s vision and the team’s capacity is crucial. Courage is demonstrated in questioning and refining backlog items, ensuring they align with the product strategy.

During Backlog Refinement: 1. Commitment is evident as the team prioritize and prepare user stories for upcoming Sprints. 2. Courage encourages open discussions about technical challenges and uncertainties, ensuring thorough understanding. 3. Focus directs their attention to refining the highest-priority items, aligning with Sprint goals. 4. Openness fosters transparent communication, allowing the team to share insights and ask questions freely. 5. Respect underscores interactions, valuing each member's input and creating a harmonious atmosphere. Through the Scrum values, the team ensures their Backlog is well-prepared for successful Sprints.

backlog grooming, is the period of time where product owners, managers, and team members review and prioritize product backlog items. This project management process is commonly used in development teams who use the Agile methodologies

Das Backlog Refinement ist wie das Sortieren deines Werkzeugkastens. Du schaust, was ansteht, ordnest und schätzt. Frag nach, wenn dir was unklar ist, und diskutier mit dem Team, was als Nächstes dran ist. Der Product Owner hat zwar das letzte Wort, aber deine Meinung zählt auch.

In every Scrum event, the five Scrum values - commitment, courage, focus, openness, and respect - guide interactions, decision-making, and collaboration within the team. Team members dedicate themselves to achieving Sprint Goals by emphasizing commitment. Courage is evident when addressing challenges openly and seeking innovative solutions. Maintaining focus on the objectives of each event ensures productive outcomes. Openness encourages sharing of information and insights, while respect supports a positive and inclusive environment. Keeping these values at the forefront improves the effectiveness of every Scrum event and ceremony.

Openness is a value needed in every event. Without it, the event may not have the necessary impact. For example, when having the retrospective, if the team is not open, problems may remain unsolved.