Articles, Blog Posts, Books and Quotes on Agile Project Management
This article explains that it is important to end doomed projects before they become “too big to fail”. This article isn’t about the personal benefits of failure, but is rather about Agile software development. It’s about how failure, recognizing it and doing something about it, is a critical element of any Agile initiative.
In this article, Stefan Roock shares five tips for impediment resolution with Scrum: 1. Make the impediments visible 2. Search for impediments 3. Limit the number of impediments 4. Differentiate between local and global impediments 5. Help the team to resolve impediments
This article examines something called “The Daily Scrum Meeting” used by Scrum Teams on Agile Software Development Projects around the world. Using some real-life stories and cartoons, you should walk away from this with a better understanding of what not to do, what to do, and then how you can make changes if the first team looks more like what your Scrum Team is doing today.
Scrum is often mentioned as an approach that minimize project documentation to only what is really useful. However, other persons can need written content to work with the developed software. This blog post discusses the role of technical writers in Scrum projects and how agile principles should apply to their activity.
Your team has adopted the relative story point estimation and you are now ready to jump into your first planning poker session. Where do you start? What is a 1-point story? What is a 3-point story? What is a 13-point story? Your team is looking to you and this process is almost as new to you as it is to them.
Marc Löffler shares in this blog post 11 hints to improve all the Scrum meetings. He discusses daily stand-up meeting where he suggests to show colleagues what your currently working on instead of just talking about it. He also make proposals to improve the sprint planning, sprint reviews and retrospectives.
In this blog post, Michael Sahota explains the basic principles of NonViolent Communication (NVC) and how they can help your to improve communication in your Scrum team. Nonviolent communication (also called compassionate communication) is a communication process that often functions as a conflict resolution process. It focuses on two aspects of communication: honest self-expression and empathy. This communication is very close to the concepts developed in the Core Protocols.
Scrum Expert Copyright © 2009-2024 Martinig & Associates