1. What is the purpose of a Sprint in Scrum?

The purpose of a Sprint in Scrum is to complete a specific set of tasks, features, or deliverables within a fixed time period (typically 2-4 weeks). This time-boxed iteration allows for the team to plan, execute, and review their work as a cohesive unit. The main goals of a Sprint are to deliver potentially shippable increments of the product, inspect and adapt progress towards project goals, and foster collaboration and communication among team members. Sprints also provide a consistent cadence for regular feedback from stakeholders and allow for adjustments to be made based on that feedback. Ultimately, the purpose of a Sprint is to facilitate the continuous delivery of high-quality products through incremental and iterative development.

2. How long does a typical Sprint last?

+
+A sprint typically lasts 2-4 weeks, with a recommended duration of 2 weeks.

3. What do the team members do during the Sprint Planning event?

During the Sprint Planning event, team members typically do the following:

1. Analyze and discuss the product backlog: Team members review the items in the product backlog and discuss their priority and feasibility.

2. Collaboratively select items for the upcoming sprint: Based on their analysis of the backlog items, team members collectively decide which items they will work on during the upcoming sprint.

3. Estimate effort and prioritize tasks: Team members estimate how much effort each chosen item requires and prioritize tasks based on their complexity and impact on goals.

4. Define a sprint goal: The team works together to establish a clear and specific goal for the sprint that aligns with the product vision.

5. Plan tasks for each selected item: Once backlog items have been prioritized, team members plan out how they will complete each task necessary to fulfill them.

6. Identify potential obstacles or dependencies: The team discusses any potential obstacles or dependencies that may hinder their progress during the sprint, such as lack of resources or technical challenges.

7. Commit to completing the work: By the end of Sprint Planning, team members should have a clear understanding of what is expected of them and commit to completing all planned work within the designated time frame.

4. How is the goal for each Sprint decided upon?

+
+The goal for each sprint is decided upon during the Sprint Planning event. During this event, the Scrum Team decides which backlog items can be worked on in the upcoming sprint based on their priority and capacity. The team also discusses the overall objective or goal for the sprint and agrees on what they aim to achieve by the end of the sprint. This goal serves as a guide for the team throughout the sprint and helps them stay focused on delivering value.

5. Can a Sprint be cancelled once it has begun?

Yes, a Sprint can be cancelled before it is completed or towards the end of the Sprint if it is deemed necessary by the team or stakeholders. However, cancelling a Sprint should only be done in exceptional circumstances and should not become a regular occurrence. The team should thoroughly evaluate the reasons for canceling the Sprint and make necessary adjustments to prevent similar situations from arising in future Sprints.

6. What is expected from team members during the Daily Scrum event?

Team members have the following responsibilities during the Daily Scrum event:

1. Visibility: Team members are expected to be visible and present at the Daily Scrum so that they can actively participate and contribute to the discussion.

2. Share progress: Each team member should share their progress on tasks assigned to them in the previous day, including any roadblocks or impediments they faced.

3. Plan for the day: The team should review the tasks that still need to be completed and plan out new ones for the current day, based on priorities set by the Product Owner.

4. Communicate issues: If a team member is facing any issues or challenges, they should raise them during the Daily Scrum so that they can be addressed and resolved as soon as possible.

5. Discuss coordination: Team members should discuss any coordination needed between them, such as dependencies between tasks, to ensure smooth progress.

6. Time management: All team members should keep track of time and make sure that they use their scheduled time effectively during the Daily Scrum event.

7. Focus on sprint goals: The Daily Scrum is an opportunity for each team member to align their work with the sprint goal and discuss ways to contribute towards achieving it.

8. Actively listen: Team members are expected to actively listen to each other’s updates and provide constructive feedback or support when necessary.

9. Respect timebox: The Daily Scrum has a set time limit (usually 15 minutes), and all team members are expected to respect this timebox by keeping their updates concise and relevant, avoiding discussions outside of its scope.

10. Use visual aids: Visual aids such as task boards or progress charts can be used by team members during the Daily Scrum to provide a quick overview of their progress and help facilitate discussion.

7. How long should the Daily Scrum last?

The daily scrum should last no longer than 15 minutes.

8. Can stakeholders attend the Daily Scrum?

A: In general, the Daily Scrum is intended only for members of the Scrum team (Product Owner, Scrum Master, and Development Team). However, if stakeholders have a specific need or question that can be addressed during the Daily Scrum and will not disrupt or distract from the purpose of the meeting, they may be invited to attend. It is ultimately up to the discretion of the Scrum Master and the team to decide who attends the Daily Scrum meetings.

9. What happens during the Sprint Review event?

The Sprint Review event is a meeting that takes place at the end of each Sprint where the Scrum Team reviews the work that was completed during the Sprint. This includes reviewing and demonstrating the completed product increment to stakeholders, gathering feedback from stakeholders, and discussing any changes that may be needed for future Sprints.

During the Sprint Review, the Development Team presents their work to stakeholders and receives feedback on whether they have met the Sprint goal and achieved the product vision. This allows for transparency and collaboration between the Scrum Team and stakeholders.

The Product Owner then updates the Product Backlog based on any new information or feedback received during the review. This helps prioritize and plan for future Sprints.

The outcome of the Sprint Review is a clear understanding of what was accomplished during the Sprint, what still needs to be done, and how it aligns with business goals. The team also reflects on their process and discusses ways to improve for future Sprints.

10. Who participates in the Sprint Review and how long does it typically last?

The Sprint Review involves the Scrum Team (Product Owner, Scrum Master, and Development Team) as well as stakeholders such as customers, users, and management. It typically lasts no more than four hours for a one-month Sprint. For shorter Sprints, the event is usually shorter.

11. How are changes and adjustments made based on feedback during the Sprint Review?

The Scrum Team, including the Product Owner and the Development Team, evaluates the feedback from stakeholders during the Sprint Review and identifies any changes or adjustments that need to be made. These changes are then discussed and prioritized in the Product Backlog.

The Development Team will then create a plan for implementing these changes in future Sprints. The Product Owner may also update the priorities of the Product Backlog based on stakeholder feedback.

During the next Sprint Planning, these updates and changes will be taken into account when selecting new items from the Product Backlog. The Development Team will also adjust their work plan for the upcoming Sprint accordingly.

The Scrum Master plays a key role in facilitating this process by ensuring effective communication and collaboration between all members of the Scrum Team. They also help to identify any potential roadblocks or issues that may arise from implementing these changes.

Ultimately, the goal is to continuously improve and adapt based on feedback and ensure that valuable features are being delivered to meet the needs of stakeholders.

12. What is the main focus of a Sprint Retrospective?

A Sprint Retrospective is focused on reflecting and improving the team’s process, interactions, and practices during the previous sprint. The main focus is to identify what worked well and things that can be improved upon in future sprints. It also provides an opportunity for the team to make commitments for changes or improvements that they will implement in the next sprint.

13. Who leads the discussion during a Sprint Retrospective?

-Scrum Master
(Su Sprints Retrospective Scrums vem acompanhar e fiscalizar, eles não devem ser sujeitos da revisão, já que seu objetivo é garantir que a metodologia seja seguida corretamente.)

14. Is it necessary to have a separate facilitator for the retrospective?

It is not necessary to have a separate facilitator for the retrospective, but it can be helpful. Having a neutral, unbiased person lead the discussion can create a safe and productive environment for all team members to share their thoughts and ideas. The facilitator can also help steer the conversation, keep it on track, and ensure that everyone has an equal opportunity to participate. However, if there is someone on the team who is skilled in facilitating discussions and creating a safe space for communication, they could also take on this role.

15. How are action items identified and implemented after a retrospective?

After a retrospective, members of the team or scrum master will often create action items for improvement based on the observations and discussions during the retrospective meeting. These action items may be specific tasks to address issues or areas for improvement.

1. Identify Action Items: The first step is to identify the specific action items that need to be implemented. These can be identified by discussing with the team, reviewing the retrospective notes, and considering any suggestions or feedback that were raised during the meeting.

2. Assign Responsibilities: Once the action items have been identified, it is important to assign responsibilities for each task to a team member or group of members who will be responsible for implementing it.

3. Set Priorities: It can be helpful to prioritize the action items based on their importance and urgency. This will help in planning and allocating resources effectively.

4. Create a Plan: A plan should be created outlining what needs to be done, by whom, and by when. This helps in keeping track of progress and ensuring that all necessary steps are taken.

5. Implement Action Items: Once the plan has been created, it is time to implement the action items according to their assigned responsibilities and deadlines.

6. Monitor Progress: Regularly monitoring progress is important to make sure that action items are being implemented as planned and any issues or roadblocks are addressed promptly.

7. Review Results: After a reasonable amount of time has passed, it is important to review the results of implementing the action items. This can be done through follow-up discussions or another retrospective meeting to assess whether they have effectively addressed the identified areas for improvement.

8. Take Further Action if Needed: If further improvements or changes are needed, they can be identified through follow-up discussions or future retrospectives in order to continuously improve processes within the team.

Implementing action items after a retrospective requires clear communication, effective planning, and consistent follow-up in order to ensure continuous improvement within the team.

16. Can new items be added to the Product Backlog during a sprint?

Yes, new items can be added to the Product Backlog during a sprint. In fact, it is encouraged in Scrum to continuously refine and update the Product Backlog as new information and ideas emerge. However, it is important for the entire Scrum Team to understand the impact and priority of adding new items during an ongoing sprint, as it may necessitate changes to the current workload or goals. Any changes should also be communicated transparently to the stakeholders to ensure alignment and manage expectations.

17. What happens if not all planned work is completed by the end of a sprint?

If not all planned work is completed by the end of a sprint, the team should have a retrospective meeting to discuss why certain tasks were not completed and how they can improve their process for future sprints. The incomplete tasks should be re-assessed and either added to the backlog to be prioritized for the next sprint or reprioritized within the current sprint if there is still enough time. It is important for the team to continuously learn and improve from their sprints in order to increase their efficiency and productivity.

18 . How often does sprint planning occur in an average project?

Sprint planning typically occurs at the beginning of each sprint in an agile project, which can range from 1-4 weeks depending on the team’s preference. Therefore, it can occur as frequently as every 1-4 weeks in an average project.

19 . Can external factors affect sprint length or execution?

Yes, external factors such as changes in business priorities or resources, unexpected events or disruptions, and stakeholder feedback can all impact sprint length and execution. Changes to the project environment may require adjustments to the sprint plan and timeline, which can affect the team’s ability to complete tasks within the originally planned timeframe. This could lead to shortened or extended sprint lengths, as well as revisions to the backlog items included in each sprint. Additionally, changes in team dynamics or external dependencies may also impact the team’s ability to execute sprints effectively.

20 . Is documentation required for each scrum event, and if so, what should be included in them?

Yes, documentation is required for each scrum event to ensure that all team members are on the same page and to track progress throughout the project. The following information should be included in the documentation for each scrum event:

1. Sprint planning:

– Goals and objectives of the sprint
– Selected user stories for the sprint
– Estimated effort and time for each user story
– Team’s capacity and velocity calculations

2. Daily scrum:

– Date and time of the daily scrum
– Attendees and absentees list
– Updates on completed tasks from the previous day
– Plan for completing tasks on current day

3. Sprint review:

– Date and time of the review meeting
– Attendees and absentees list
– Demonstrated product features or functionality
– Feedback from stakeholders
– Identified areas for improvement

4. Sprint retrospective:

– Date and time of retrospective meeting
– Facilitator’s name
– Attendees list
Format: What went well, what didn’t go well, what could be improved
In-depth discussion on identified issues
Plan for implementing improvements

5. Sprint backlog:

-A comprehensive list of user stories planned for a particular sprint along with their priorities, estimated effort, assigned team member(s), status (to-do/ in progress/ done), comments or notes.

6. Product backlog updates:

-The updated version of product backlog after any changes made in top priority items by a Product Owner before starting a new sprint are included in this document.

7. Burndown charts:

-Charts that display remaining work against days left in a sprint at any point during a development process.