As the Agile Manifesto stated that it prefers “working software over comprehensive documentation”, some early Agile adopters jumped to the conclusion that documentation was useless. Thus Scrum software developers should only concentrate in creating working software with code that was the most easier to understand.
Agile and Scrum team formation is a natural human response to certain conditions. Once they exist, the formation process begins. This session looks at those conditions, and then looks at what other conditions need to be reached to progress through the different stages defined by Bruce Tuckman: Forming, Storming, Norming, and Performing.
There’s some weird stuff going on in the name of “agile” nowadays.Too many pretty promises, eager exaggerations, and misguided misapplications of misunderstood premises make for troubling times. So what is the future of agile? We want to share with you how agile fails and how agile succeeds. The key to the future of agile is being thoughtful, realistic, and above all skeptical.
The Scrum Guide says that “The Scrum Master is a servant-leader for the Scrum Team.”, but what is servant leadership? We will talk about where servant leadership came from and what servant leadership is. We will talk about examples of servant leaders in our world and where to find more information about servant leadership. Finally, we will talk about how you can become a servant leader.
Nexus is a framework for scaled Scrum developed by Scrum co-creator Ken Schwaber and Scrum.org community. It addresses the most painful problems of scaled development – dealing with dependencies and building ‘Done’ integrated software every iteration.
As Agile has become a mainstream approach in software development, there are many books and discussions about its concepts and how to implement them. The book “Environment for Agile Teams” by Andy Brandt provides a different, and very interesting, perspective as it discusses the practical details of the everyday life of a Scrum team.
In small Scrum teams, it’s common for people to share roles such as Scrum Master / Tester / Dev but in a lot of cases there are conflicting interests. How can a Tester adequately test when as a Scrum Master the highest priority is assisting the team to deliver?
Scrum Expert Copyright © 2009-2025 Martinig & Associates