The Scrum checklist is a simple tool that provides guidelines to assess your current implementation of Scrum or help you adopting it. Created by Henrik Kniberg, the author of “Scrum from the Trenches”, they incorporate his experience gained during years helping companies getting started with Scrum and many meetings with other practitioners, trainers and Scrum coaches.
The “rightsizing” of user stories occurring during the planning of the next sprint in Scrum is not always an easy task to perform. Inexperienced teams have difficulties to split user stories into smaller chunks that still deliver business value and would rather use technical criteria. In this blog post, “Specifications by Example” author Gojko Adzic provides a new approach to achieve this goal using the hamburger as a reference. You identify the tasks making up a user story. Then you use this breakdown to identify different levels of quality for each step and create vertical slices to identify smaller deliverables, thus creating your next sprint’s hamburger.
During Scrum adoption, people tend to get away from tasks and activities that they don’t like in traditional projects like documentation or writing proper code comments. In this article, a ScrumMaster shares his experience with a “no documentation” approach. He learned the hard way that minimal documentation is better than no documentation in Scrum projects. The team can decide on a case-by-case basis what level of documentation for which components and code logics is needed.
Should you track individual performances in Scrum and how do you do it? Nanda Vivek says that there is only one answer and this is “No”. Measuring individual productivity is against the spirit of Scrum and the article discusses the importance of being helpful and collaborative in teams. The author however does not give guideline on how to deal in this case with the individual review that is a common practice in many large organizations.
Pair programming is an extreme programming technique that should help Scrum teams to build better software: two heads are better than one, they say, and thus two heads will usually produce a higher-quality system. This article presents the benefits of this technique for the team, the developers and the managers that will appreciate the value of a true team that works well together, collaborates and continuously improves the code base.
This article presents the IBM perspective on top five lessons learned about scaling Agile in a leading insurance provider. These lessons were that a team-by-team, incremental approach is best. Measurement and management tools can help you get and sustain executive buy-in and improve the development process. Mentoring and coaching should be provided for the process first and for the tools second. Integrated tools help demonstrate value. Retrospectives are essential for continuous improvement.
Companies that transition to Agile often adopt the analogy that sprints are just mini waterfall. This article provides five reasons why Scrum sprints are not mini-Waterfall. Each argument is illustrated by a diagram that provides a clear visual evidence of the difference between the Agile approach and a traditional process.
Scrum Expert Copyright © 2009-2024 Martinig & Associates