Articles and videos on creating and managing cross-functional Scrum teams: scrum master, product owner and development team.
If one of the first aim of Scrum was to break the silos between business analysis, development and testing, you can consider that improving the cooperation with the operation side of IT as the next frontier in this journey. What is the point to produce potentially shippable software increment in two weeks if your database administrator doesn’t want more than three new releases windows for the production database?
There might exist some lonely standalone software developers that create software without any other person involved, but my guess is that there are not many of them. Communication is an essential skill in software development, testing and project management… and life. As feedback is a key communication tool, I was therefore very interested when I stumble on this book about feedback written by an Agile coach.
If Scrum and Agile approaches are supposed to increase the chances of success for software development projects, not all the projects that want to use Scrum are successful. In some organizations, Scrum is a failure. This article discusses why Agile projects might fail because of the confusion between the Scrum roles (Scrum Master, Product Owner, Developer) of a Scrum Team and the required Agile mindsets.
How do we actually know if our Agile teams are doing well? Is gut instinct enough? Furthermore, in a rapidly growing organization such as Spotify, how can we ensure some sort of consistency in our baseline level of Agile knowledge across the technology, product, and design organization?
This is not a talk about Scrum teams. This is a talk about you and your role in developing a great team. No matter whether you are a Scrum Master, Project Manager or CTO, at least part of your job is to help your team or teams grow. In order to make this happen you need to work on two levels: The Zen Level and The Operational Level.
At the beginning of his book, Allan Kelly describes Xanpan as both a method and a philosophy, his philosophy on how software is, or should be, created, and how Agile works, or should work. If Xanpan is basically a mix of XP (eXtreme programming) and Kanban, it contains ideas and techniques of other Agile and Lean approaches, focusing on how teams should work together to deliver better software and value.
This presentation uncovers a number of key principles and useful tools to help you better skills as a geek who leads Agile and Scrum teams. The most challenging aspects to software development are always the people issues. Picking the right data structures, finding the right testing approaches are simple compared to building an effective software team.
Scrum Expert Copyright © 2009-2025 Martinig & Associates