Metrics to Drive High Performance Scrum Teams
This presentation by Grindr VP of Engineering, Lukas Sliwka, focuses on implementing Scrum metrics to drive high performance teams while building strong and innovative software engineering organization.
This presentation by Grindr VP of Engineering, Lukas Sliwka, focuses on implementing Scrum metrics to drive high performance teams while building strong and innovative software engineering organization.
Let’s challenge some of the commonly accepted patterns for software development teams. High degree of autonomy doesn’t turn into anarchy but rather help to keep intrinsic motivation high. Participatory leadership means that every team member is a leader yet it doesn’t mean competition. Decisions making process has nothing to do with power structures. Culture is paramount and it goes ahead of technical skills. Collaboration is ultimately the factor the whole team optimizes their work for.
Story mapping is a technique invented by Jeff Patton that order user stories along two independent dimensions. The “map” arranges user activities along the horizontal axis in rough order of priority. On the vertical axis, it represents increasing sophistication of the implementation. In his blog post, Sunit Parekh explains how you can apply story maps to build your product backlog in a visual way.
In 2001 a group of programmers proposed the word “agile” to describe a set of values they shared. Several of these programmers had already developed methods based on these values. The values are universal, that’s how they were chosen. The methodologies, however, were designed for the technology landscape of the 1990s. Think of all the changes in technology and business practise in the last 25 years. If that seems too daunting just think about the last five years. In taking “Agile” mainstream, we adopt these ancient practises on faith while losing sight of the values that inspired them.
Continuous improvement is one of the main values of Agile and retrospectives should play an essential role in supporting this process. In his short and free book “Agile Retrospective Kickstarter”, Alexey Krivitisky provides some exercises that should help Scrum teams to get the most out of their retrospective meetings.
As Agile matures and learns from experience, it is clear that the Agile business analyst has a significant role to play. This interactive and musical session will explore the relationship between Product Owner and Business Analyst, their responsibilities and the skills needed. I’m an Alien … I’m a Business Analyst in an Agile world!”
Technical debt is a well-known concept in Agile software development. Technical Debt is defined as the eventual consequences of poor or evolving software architecture and software development within a codebase. In this blog post, Steve Blank discusses the concept of organizational debt.
Scrum Expert Copyright © 2009-2026 Martinig & Associates