A New Tool for Retrospectives
The Dialogue Sheet is a new technique for team retrospectives in Scrum Projects. This technique involves a large sheet of paper that help to create good discussion and teamwork in Agile and Scrum projects.
The Dialogue Sheet is a new technique for team retrospectives in Scrum Projects. This technique involves a large sheet of paper that help to create good discussion and teamwork in Agile and Scrum projects.
This article presents the changes needed to create collaborative agile teams. It explains that you need to modify in your traditional project management team both the process, the way people get work done, and how people work together.
This article explains that it is important to end doomed projects before they become “too big to fail”. This article isn’t about the personal benefits of failure, but is rather about Agile software development. It’s about how failure, recognizing it and doing something about it, is a critical element of any Agile initiative.
In this article, Stefan Roock shares five tips for impediment resolution with Scrum: 1. Make the impediments visible 2. Search for impediments 3. Limit the number of impediments 4. Differentiate between local and global impediments 5. Help the team to resolve impediments
This article examines something called “The Daily Scrum Meeting” used by Scrum Teams on Agile Software Development Projects around the world. Using some real-life stories and cartoons, you should walk away from this with a better understanding of what not to do, what to do, and then how you can make changes if the first team looks more like what your Scrum Team is doing today.
Continuous feedback is part of basic principles of Agile project management, using techniques such as Test Driven Development (TDD), Continuous integration or daily stand-ups meetings that allow the Scrum team to share concerns about potential challenges as well as coordinate efforts to resolve difficult and/or time-consuming issues.
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.
Scrum Expert Copyright © 2009-2024 Martinig & Associates