Most of the Scrum teams use a task board to visualize their activity and progress with task cards. In these two blog posts, Keith Clinton, the author of Agile Game Development with Scrum, discusses the concept of feature boards and feature cards.
Rich Hickey has stated “The simpler solution is going to kick your butt”, Russ Miles would go further, “The simpler solution is already kicking your butt; no one is more agile than the teams developing with simplicity in mind”.
The Product Owner is a very important role in Scrum. He has the key responsibility to create, manage and prioritize the product development backlog. Can this responsibility always be to a unique person or is there situations where you could have a team of product owners? Kenneth Rubin discusses this topic in his “Essential Scrum” book.
The definition of “Done” (DoD), which means that a feature is ready for delivery, is a concept often discussed in Scrum. In this blog post, George Dinwiddie discusses the concept of “Ready” that apply to user stories that are ready to be developed.
Agile is founded on people and interactions. This presentation will explain a model to align teams for high performance and give you practical techniques, adapted from clinical hypnosis, that have proven successful with project visioning, goal setting, improved team communication and business collaboration.
The daily stand-up meeting is an important moment in Scrum project. Team members meet to know about potential challenges as well as to coordinate efforts to resolve issues. They usullay discuss the three following questions: What did I accomplish yesterday? What will I do today? What obstacles are impeding my progress? In this blog post, Derek Huether describes 10 types of persons that create trouble in the Scrum daily stand-up meeting.
One of the principles of the Agile Manifesto says, “continuous attention to technical excellence and good design enhances agility.” In his book “Implementing Domain-Driven Design“, Vaughn Vernon complains however that adopting Scrum has often led to spend less or no time on good software design practices and he is not the only one in this case.
Scrum Expert Copyright © 2009-2026 Martinig & Associates