Migrated from github.com/shafiqalibhai/awesome-agile-essentials
https://saadaakash.github.io/awesome-agile-essentials/
- Dockerfile 100%
| resources | ||
| Acceptance-Testing.md | ||
| Definition-of-Done.md | ||
| Dockerfile | ||
| Kanban.md | ||
| LICENSE | ||
| README.md | ||
| Scrum.md | ||
| User-Stories.md | ||
| WaterfallVSIterative.md | ||
awesome-agile-essentials
Overview
An awesome list of concepts & resources of Agile Software Development, curated from handpicked contents, courses & the Internet.
This repository was migrated from upstream source github.com/shafiqalibhai/awesome-agile-essentials and is preserved here for archival, reference, or continued local development.
At a glance
- Default branch:
master - Visibility: public
- Size: 317 KB
- Created: 2026-04-27
- Last updated: 2026-04-27
- Stars / Forks / Open issues: 0 / 0 / 0
Repository structure
resources/Acceptance-Testing.md(1,146 B)Definition-of-Done.md(1,006 B)Kanban.md(2,307 B)LICENSE(7,048 B)README.md(9,252 B)Scrum.md(6,594 B)User-Stories.md(2,693 B)WaterfallVSIterative.md(4,091 B)
Getting started
Clone the repository:
git clone https://forgejo.deployview.com/ssa/awesome-agile-essentials.git
cd awesome-agile-essentials
Installation
git clone https://forgejo.deployview.com/ssa/awesome-agile-essentials.git
cd awesome-agile-essentials
Usage
Refer to the source files in this repository for entry points and intended usage. Update this section with concrete examples once they are established.
Original README
The content below is preserved from the previous README. Headings have been demoted so they don't compete with the new top-level sections.
Awesome Agile Essentials 
An awesome list of concepts & resources of Agile Software Development, curated from handpicked contents, courses & the Internet.
Table of Contents
- The Fundamentals
- Types of Agile Methodology
- User Stories
- Acceptance Testing
- Free Scrum Courses
- Study Materials: Professional Scrum Master level I (PSM I)
- Study Materials: The Professional Scrum Product Owner level 1 (PSPO 1)
- Study Materials: The PMI Agile Certified Practitioner (PMI-ACP)
- Topic Specific Resources
The Fundamentals
- Agile Manifesto
- Writing the Agile Manifesto by Martin Fowler
- 12 Principles Behind the Agile Manifesto
- Agile Glossary
Types of Agile Methodology
User Stories
Acceptance Testing
Free Scrum Courses
- Scrum Training Series
- Scrum 101
- Volkerdon Training Series
- Scrum Foundations Training by Mike Cohn, Mountain Goat Software
Study Materials: Professional Scrum Master level I (PSM I)
- Suggested Reading for Professional Scrum Master™ I
- PSM I™ Preparation Quiz – Real Mode
- PSM I Assessment (Free)
- PSM Exam Study Tips
- How to prepare for and pass the PSM I exam
- Scrum.org PSM I Study Tips
- Pocket Scrum Certification Self-Study List
- How to pass PSM 1 exam
Study Materials: The Professional Scrum Product Owner level 1 (PSPO 1)
Study Materials: The PMI Agile Certified Practitioner (PMI-ACP)
Topic Specific Resources
Scrum
| Website | Description |
|---|---|
| Scrum in 5 Minutes | The goal of this blog entry is to explain the basic concepts of Scrum in less than five minutes. You learn how Scrum can help a team of developers to successfully complete a complex software project |
| The Scrum Guide | The Definitive Guide to Scrum: The Rules of the Game |
| The Nexus™ Guide | This Guide Describes Nexus, the Framework for Scaling Scrum |
| Scrum Open Assessments | As these are free study tools, please note that the questions on the Open Assessments do not have the same level of difficulty as the certification assessments. |
| PROFESSIONAL SCRUM DEVELOPER™ CERTIFICATION | The Professional Scrum DeveloperTM (PSD) assessment is available to anyone who wishes to validate their knowledge of how to build complex software products using Scrum. |
| Reasons Why Scrum Can Fail | Scrum fails when those in the named roles fail to live up to the role. This can also include cases where a role isn’t named or when someone or more than one person steps-up into that role. But in either case, if those mindsets are not present on the team it is a recipe for failure |
| Product Backlog Grooming Best Practices: What it is and Why it’s Critical | The new product development process can be messy and unwieldy if it's not managed carefully. |
Kanban
| Website | Description |
|---|---|
| Personal Kanban | Personal Kanban is used in every country, every line of work, by families, teams, companies, and governments. |
| Essential Kanban Condensed | by David J Anderson and Andy Carmichael |
User Stories
| Website | Description |
|---|---|
| Creating Effective Sprint Goals | Working with a sprint goal is a powerful agile practice. This post helps you understand what sprint goals are, why they matter, how to write and how to track them |
| Getting good user stories from business analysts | 7 things to keep in mind when writing good requirements |
| 10 Tips for Writing Good User Stories | User stories are probably the most popular agile technique to capture product functionality: Working with user stories is easy. But telling effective stories can be hard. |
| Identifying and Improving Bad User Stories | Charles Suscheck and Andrew Fuqua explain some common failure patterns that will help you focus on the right role, value, and business functionality when writing stories |
Definition of Done (DoD)
| Website | Description |
|---|---|
| DONE Understanding Of The Definition Of "Done” | The Professional Scrum Master (PSM) workshop has a module that talks about the Definition of "Done" (DoD) and Technical Debt. |
| Definition of Done | Software developers have a reputation for being somewhat careless when answering the question "Are you done with this feature"? |
| Agile Best Practices: The Definition of Done | 3Pillar Global's SVP of Engineering, Jeff Nielsen, talks about how a mutual understanding of the definition of done |
Accepting Testing
| Website | Description |
|---|---|
| Specifying with examples | An interesting thing about examples is that they pop up several times later in the process as well. |
| Behind-the-Scenes: How We’re Automating Acceptance Testing | Acceptance testing can be quite a complex thing, so while I’ll show some code it is far from complete and primarily here to give you a taste of how we set things up. |
Contributing
Contributions are welcome. The typical workflow is:
- Open an issue describing the change you'd like to make.
- Fork the repository (or create a feature branch if you have write access).
- Commit your changes with clear, descriptive messages.
- Open a pull request against the
masterbranch.
Please follow the existing code style and include tests or reproduction steps where relevant.
License
See the LICENSE file in this repository for licensing information.
Repository
- Browse: https://forgejo.deployview.com/ssa/awesome-agile-essentials
- Clone (HTTPS):
https://forgejo.deployview.com/ssa/awesome-agile-essentials.git - Clone (SSH):
ssh://git@forgejo.deployview.com:30143/ssa/awesome-agile-essentials.git - Upstream / origin: github.com/shafiqalibhai/awesome-agile-essentials
This README was generated automatically based on repository metadata, contents, and any prior README content. Edit any section above to add project-specific detail.