The board game Othello has the slogan: “A minute to learn, a lifetime to master.” This applies really well to a team that’s learning Scrum. The basic practices and mechanics of Scrum are straightforward, and not difficult to adopt.
Implementing Scrum is difficult and it is always difficult to answer the question of where to start this Agile Travel. In this article, Ilan Goldstein shares 10 tried-and-tested steps to help new practitioners get their Scrum show on the road.
Knowing the basics of Scrum is essential for any team member, but out in the trenches, a good ScrumMaster must be ready to identify and deal with Agile Antipatterns quickly to help his team and organization move forward.
Implementing Scrum is difficult and there might be nothing better than taking time and making mistakes to adopt Agile successfully. This being said ” Scrum Shortcuts without Cutting Corners” is a book that can help you to choose better trails when you explore some of the Scrum practices.
The rhythm of Agile software development is to always be working on the next known, small batch of work. Is there a place for software architecture in this style of development? Some people think that software architecture should simply emerge and doesn’t require ongoing attention. But it isn’t always prudent to let the software architecture emerge at the speed of the next iteration.
This article by Tim Dahmen introduces a notation is based on a metaphor for software development, which is fantasy role-playing games. It explains a graphical and symbolic notation that allows to communicate about several Scrum phenomena.