• If you are citizen of an European Union member nation, you may not use this service unless you are at least 16 years old.

  • Want to get organized in 2022? Let Dokkio put your cloud files (Drive, Dropbox, and Slack and Gmail attachments) and documents (Google Docs, Sheets, and Notion) in order. Try Dokkio (from the makers of PBworks) for free. Available on the web, Mac, and Windows.


Contribution Guidelines

Page history last edited by PBworks 13 years, 7 months ago

This Scrum Smells Catalog is intended to be a read/write space for sharing Scrum experiences and knowledge from the perspective of smells and example remedies. To make it easier for both readers and for future contributors, it is strongly recommended that you structure your material consistent with other Smells in this catalog. There are two recommended structures for this as outlined in the following. It may be a good idea to start with the Simple structure and transition it to the Expanded structure when the additional detail becomes clearer.



Structure A - Simple


1. Smells


The surface indicators of a problem with the Scrum implementation.


2. Discussion


Discuss the underlying problems and how they can be addressed.




Structure B - Expanded


1. Smells


The surface indicators of a problem with the Scrum implementation.



2. Causes


What problems/impediments underlie these smells? Identify the root cause if possible.



3. Consequences


What is likely to happen if this problem persists?



4. Prevention


How can we avoid this problem occurring in the first place?



5. Example Remedies


How was the problem resolved? Labelled "Remedy A", B, C etc. There may be many possible remedies and readers should take care to select an approach appropriate to their unique context.



6. Case studies


Tell a story about how what happened including the organisational context. Labelled "Case Study A", B, C etc.



Comments (0)

You don't have permission to comment on this page.