World’s Largest Opinionated Agile Reference Library. The content is created and the links are curated through the lens of Agile Pain Relief Consulting’s view of what is effective in the practice of Scrum and Agile. We don’t accept submissions, and emails to that effect are marked as spam. Book listings may use affiliate links that could result in a small commission received by us if you purchase, but they do not affect the price at all. From experience, this won’t amount to anything more than a cup of coffee in a year.
We’re always looking for all things Agile. As a result, we’ve amassed a large collection of information covering lots of practical topics, techniques, tips, and case studies which we believe may help you toward your Scrum/Agile goals. They have been curated and organized into one spot, to share with you to help you on your Agile journey. We routinely scan for broken links, but if you spot one before we do, please let us know.
- TDD vs BDDTest Driven Development [TDD] and Behaviour Driven Development [BDD] are often confused because the similarity of their names. TDD is the original(...)
- Team Formation ModelsTeam Formation Models are helpful in understanding what state a team is at, and then using that information to make an educated guess as to what will help(...)
- Team LaunchThe purpose of the team launch or liftoff is to help the team move from a group of unconnected people to have the start of a real team. (Additional(...)
- Team LearningSlack, in the context of Agile/Scrum, is when the time isn't solely focused on delivering. (It's important not to confuse this with Slack, a popular(...)
- Team SizeThe Scrum Guide offers very limited guidance, suggesting 3-9 people per team (exclusive of ScrumMaster and Product Owner), without giving reasons or(...)
- Technical DebtTechnical Debt is a deeply misunderstood term. It was originally coined at the beginning of Agile time by Ward Cunningham - from 1992: Shipping(...)
- Test Driven Development [TDD]Test Driven Development (TDD) is the engineering practice where the developer writes their Unit Test case before they write their code. Like Unit Testing,(...)
- Theory of ConstraintsThe Theory of Constraints is a system improvement tool. It illustrates how in a system where we find a bottleneck, the bottleneck is the constraint that(...)
- Trunk Based DevelopmentGit, Mercurial and other source control tools provide robust and easy to use branching capabilities. For work with OpenSource software —where anyone could(...)