Resource Links:
- A lesson in agile: How one team ended dependency delays
- Agile Organizations Must Address Both Structural and Instantiated Dependencies
- Dealing with Dependencies
- Dependencies Are Evil
- Dependencies Break Agile
- Dependencies, Scrum of Scrums, and SAFe
- Dependency and Skill Capacity Planning (portfolio planning)
- Dependency Management in a Large Agile Environment (slideshare)
- Eliminate Dependencies, Don’t Manage Them
- Impact of Multiple Team Dependencies in Software Development
- Managing Technical Dependencies (lays out many options including the weak choice – Scrum of Scrums)
- On hardware dependencies and scrum
- Shared Dependencies – The Critical Issue When Adopting Agile at Scale
- Solving the Hairy Problem of Team Dependencies
Mark Levison has been helping Scrum teams and organizations with Agile, Scrum and Kanban style approaches since 2001. From certified scrum master training to custom Agile courses, he has helped well over 8,000 individuals, earning him respect and top rated reviews as one of the pioneers within the industry, as well as a raft of certifications from the ScrumAlliance. Mark has been a speaker at various Agile Conferences for more than 20 years, and is a published Scrum author with eBooks as well as articles on InfoQ.com, ScrumAlliance.org an AgileAlliance.org.
*Thank you for visiting the World's Largest Opinionated Agile Reference Library. This 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.« Back to Glossary Index
