Scrum.org
MARCH 11, 2020
TL; DR: Development Team Anti-Patterns. After covering the Scrum Master and the Product Owner, this article addresses Development Team anti-patterns, covering all Scrum Events as well as the Product Backlog artifact. The Role of the Development Team in Scrum. Source : Scrum Guide 2017. .
Scrum.org
APRIL 3, 2023
I want you to create a schedule, name the exercises, and point to sources where I can learn more about the suggested activities. Can you be more specific regarding the exercises for lessons 4 to 7? Please suggest what kind of exercises best advance the respective lesson topic for the students.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
ProjectManager.com
MAY 19, 2022
Communicating information to all key stakeholders, sponsors and team members. Interactive Gantt charts, assign tasks and track progress, can be shared with stakeholders and keep the project team connected in real time. Manage Team. Assigning tasks to the team is only the beginning. Conduct Team-Building Exercises.
Scrum.org
MARCH 19, 2023
This allows me to have a more up-to-date understanding of the world, including newer events and developments. models: The first experiment compares the Scrum Guide 2017 to the Scrum Guide 2020 The second experiment is designing a Retrospective exercise The third experiment is to help a new Scrum team to design a Definition of Done.
Scrum.org
AUGUST 25, 2022
How sustainable is your pace as a developer? This has always been a huge struggle for us and most of the teams we’ve been part of. Unfortunately, many developers and development teams still burn more hours than are probably good for them. The initial practice was for developers to work no more than 40 hours a week.
Scrum.org
NOVEMBER 25, 2019
The Scrum Master encourages the Scrum Team to improve, within the Scrum process framework, its development process and practices to make it more effective and enjoyable for the next Sprint. By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint.
Scrum.org
APRIL 14, 2020
TL; DR: A Remote Retrospective with a Distributed Team. This fifth article now dives into organizing a remote Retrospective with a distributed team: practices, tools, and lessons learned. By the end of the Sprint Retrospective, the Scrum Team should have identified improvements that it will implement in the next Sprint.
Expert insights. Personalized for you.
220 
Let's personalize your content