An Example of Distributed Scrum
In this blog post, Joseph Little proposes a set of suggestions and questions that should help you to think on how you should make decisions about distributed scrum.
Blogs on Scrum and Agile Project Management
In this blog post, Joseph Little proposes a set of suggestions and questions that should help you to think on how you should make decisions about distributed scrum.
In this blog post, Gary Reynolds shares ten issues that prevent Scrum stand-up meetings to reach their goal. He also offers advice on what ScrumMasters can do to ensure they either don’t occur at all or are eradicated over as short a time as possible.
Scrum is often mentioned as an approach that minimize project documentation to only what is really useful. However, other persons can need written content to work with the developed software. This blog post discusses the role of technical writers in Scrum projects and how agile principles should apply to their activity.
Marc Löffler shares in this blog post 11 hints to improve all the Scrum meetings. He discusses daily stand-up meeting where he suggests to show colleagues what your currently working on instead of just talking about it. He also make proposals to improve the sprint planning, sprint reviews and retrospectives.
In this blog post, Michael Sahota explains the basic principles of NonViolent Communication (NVC) and how they can help your to improve communication in your Scrum team. Nonviolent communication (also called compassionate communication) is a communication process that often functions as a conflict resolution process. It focuses on two aspects of communication: honest self-expression and empathy. This communication is very close to the concepts developed in the Core Protocols.
Henrik Larsson presents in this post the user stories lifecycle from their origin in a Minimum usable feature (MUF/MMF) to their validation by the product owner at the end of a Scrum sprint.
In this blog post, Marc Löffler shares a checklist of items and best practices that should facilitate the a successful retrospective for a distributed team. Even if virtual retrospectives are fine, he suggests that distributed team should meet personally on a regular basis, if possible every two retrospectives.
Scrum Expert Copyright © 2009-2024 Martinig & Associates