The Agile Atlas is a web site supported by the Scrum Alliance which is an information resource for Scrum and Agile practitioners. The purpose of this site is to provide an “encyclopedia” of information about Agile and related methods.
Other Resources for Scrummasters, Product Owners and Agile Developers: podcasts, approaches, groups
Collaboration Games from the Growing Agile Toolbox is a free e-book written by Karen Greaves and Samantha Laing that proposes ten games to build collaboration in Agile teams.
Running Agile software development projects using Scrum is not always an easy task. Sometimes you need to take a step back and look at the Agile best practices with a dose of humour.
The Essential Scrum Glossary is a list of definitions of terms used in Scrum in particular and in Agile in general. An entry in the glossary might be a single word, such as “epic”, a phrase, such as “all-at-once product development”, or an acronym like “TDD”. The definitions are numbered if a term has more than one definition.
Alistair Cockburn describes software development as a cooperative game. Scrum provides one set of rules for one such way of playing the game. The Scrum Guide is the official rule book. However, the Scrum Guide doesn’t tell you the rationale behind Scrum as a whole, or behind many of its successful practices. Those rationales come out of experience, community, and the insights of its founders and inventors. The ScrumPLoP mission is to build a body of pattern literature around those communities, describing those insights, so we can easily share them with the Scrum and Agile communities.
Continuous delivery allows teams to reduce dramatically the transaction cost of releasing high-quality software, so you can do it much more frequently, providing a much richer and faster feedback cycle from users back to product teams. But, in turn, you need to change the way you think about managing the flow of work through the software delivery process.
The Lean UX that eliminate the contractual obligations inherent with specification documents and other deliverables is presented by Jeff Gothelf in this podcast. He defines Lean UX as “a rethinking of the software design philosophies and methodologies, moving away from the contractual obligations of spec documents and focusing really more on validating your designs through building products and experiments.