The way traditional businesses approach the management and organization of creative, intellectual workers is wrong. By throwing away everything that blocks productivity (meetings, deadlines, managers, titles, strict vacation policies, etc) and treating your employees as the responsible adults that they are, huge amounts of potential can be unlocked and employee happiness and retention can be at unprecedented highs.
This article explores some of the principles of agile interactions of Scrum teams. More specifically, it focuses on those interactions necessary to discovering and elaborating requirements within the context of the Scrum framework.
This article uses a tree metaphor to explains that Scrum is a very tiny yet powerful machine that will not achieve its goal if you customize it.
The article “Distributed Teams and Agile” by Craig Knighton shares experiences and a model to organize and operate distributed Agile teams. It conveys a simple main message: Agile is the best way to manage distributed software development teams.
This article proposes four “smells” that might indicate that you’re not optimally practicing whole-team approach in your Scrum software development project
In this funny blog post, Maurits Rijk lists the reasons that people will give to explain why Scrum will never work. A “dilbertian” exercise well done and that you shouldn’t take literally. Or maybe yes! ;o)
This article aims to bring to the table a consolidated Scrum Project Dashboard layout that could be easily maintained and updated by the Product Owner with day-to-day and well-known information provided by the team. He will be able to get stakeholder and management attention and support while providing an updated clear picture on the Project’s status.