One of the primary questions for agile teams adopting a new approach such as Scrum is whether to start with principles or practices. Sometimes the best way to learn principles is indirectly, through practice. Experiences are a great way to learn, and sometimes they even teach you skills without your realizing it.
People typically think of training classes as passive activities, where the instructor talks and the others listen. But experiential learning, where you learn through hands-on activities and then reflect on the experience, often gets the lesson to stick in people's brains better. Consider using interactive lessons.
Gerald Weinberg's work inspired many to be better engineers and better leaders. Although he’s no longer with us, his message about the role of people in building quality software lives on in his writings and in those who have learned from him. Here, Steve Berczuk recalls some of Jerry Weinberg's most influential books.
When hiring, adopting a framework to help you screen candidates can save a lot of time. However, much like adopting Scrum to improve your software development, following a framework won’t magically guarantee perfect results. But a framework will give you the tools to start off better, and to improve over time.
When an agile team talks about velocity, it's usually how much functionality they'll deliver in a sprint, often based on historical data about the number of story points the team tends to finish. But you shouldn't use velocity as a measure of success for your agile process. Make sure everyone knows what's important.
We are trained to identify and evaluate risks. This prevents teams from making decisions that are unlikely to work, saving time and money and helping the team move forward. However, a risk-avoidance mindset can also stop progress. Successful agile teams see risks as ways of starting a conversation, not stopping it.
Scrum events are meant to be productive opportunities for collaboration that replace more tedious, wasteful meetings. If you find your planning meetings becoming passive events where no one is asking questions or actively seeking to understand the backlog, the problem might be in the execution or the preparation.