There are several examples of job aids on xp123.com; I've consolidate examples and related books on job aids at its sister site, jobaids.info
"Intensifying stories" is an attempt to identify what can make a story (feature, capability) more potent.
I've identified key features in a number of systems (perhaps 50), identified a rule or concept beneath those features, then generalized that to apply to a number of other systems.
This is no master list (nor do I expect any to exist), but I hope this list is helpful for people working to create highly-valuable capabilities in systems.
The Checklist Manifesto, by Atul Gawande. Metropolitan, 2009.
This book is an expansion of Gawande’s interesting New Yorker article. It’s an exploration of how the relatively simple idea of a checklist can be used to ensure that complicated things get done well. What works for pilots also works well for surgery. I thought the article was enough to get the idea, but the book was an interesting read for more depth.
|One of the most important things a ScrumMaster does is recognize and remove impediments.|
This summary sheet includes 100 impediments (PDF) you may run into (though hopefully not all at once:).
I was inspired to start this list years ago from an article by Barry Boehm (which I've since lost and can't even find a reference for it).
I've found these articles that address impediments, and you may find their perspective useful as well:
- James, Michael. "A ScrumMaster's Checklist"
(Not a list of impediments, but anything you can't check may represent one.)
- Perry, Tom. "Classifying Impediments"
- Perry, Tom. "Defining Impediments"
- Shalloway, Alan. "Lean Anti-Patterns"
- Wake, Bill. "100 Impediments"
Mike Cohn and I had proposed a "User Story Workout" for the Agile 2009 conference. Our session wasn't accepted, but I'm making this handout available.
(See the original article if you want a little more background.)
[July 2009.Updated Aug. 14, 2009 to squeeze in "Wm." Pietri and link to main article.]
Joshua Kerievsky has made available Industrial Logic’s "Smell to Refactoring Cheat Sheet." (http://industriallogic.com/papers/smellstorefactorings.pdf)
|Scrum is an agile software process, centered around a self-organizing team and a 30-day development cycle. This page contains a one-page summary of its development process.|
Related Articles: Extreme Programming on a Page.
This work is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 2.5 License.
[Revised July, 2005. Previous version developed January, 2004. PDF format courtesy of Eric Chamberlain.]
|This is a one-page summary of basic terms and processes for configuration management, suitable for an agile team.|
Also available in a Microsoft Word verion (.doc).
|This mini-poster serves as a reminder about most aspects of XP.|
Thanks to Laurent Bossavit, Alex Chaffee, George Dinwiddie, Alan Francis, Ed Hughes, Ron Jeffries, Paul Moore, Ilja Preuss, and Bob Worth. I appreciated their suggestions even if I didn’t always follow their advice. I’m certain I forgot others who wrote – thank you too!
Special thanks to Becky Kuhlman, who did the graphic design.
Thanks to Nicolas Mereaux for the French translation.
[Written February, 2002; revised March 26, 2002; link to French translation February, 2015.]