Agile practitioners generally agree that regular retrospectives throughout the project are a good practice; however, many are not seeing the full benefits from the practice. This article shares a number of tips on how to perform retrospectives effectively—getting the maximum value from this important agile process.
235 items found
A new research report from Software Advice sheds light on which functionalities of agile project management software have the greatest impact on efficiency, and the extent to which agile methods are used in teams beyond software development.
Who is using Scrum? How? And why? Help us get the real answers to these important questions by completing this survey and you’ll be entered to win a $500 Amazon gift card.
Are your project retrospectives getting a bit stale, diluting their effectiveness? Keeping retrospectives fresh for your team requires diligence on your part, but the rewards from continuous improvement are worth it. Here are three fun, simple retrospective techniques that can help get your teams re-engaged.
While there are many governance data points that can be gathered and analyzed to help make go/no-go decisions, there are three in this writer's experience that stand out as being the most important.
When you’re operating in an Agile environment — or any other software development scenario, for that matter — three factors almost always make the difference between success and failure: domain knowledge, dialogue and deadline pressure. Here, Cutter Consortium consultant and researcher Michael Mah presents his anatomy of a failed project.
Like many fields, nonprofit and government organizations want to find ways to respond to projects faster and more efficiently. This article provides five ideas for them to use agile methods and approaches.
As more organizations become agile, clear, real-time communication becomes increasingly important. Here are a few tips to keep in mind to ensure your communication remains effective a new fast-paced environment.
In the final installment of our series on structuring Agile teams, here is an iterative process, in the form of questions, to help project leaders design the most appropriate team structure for the project at hand.
One of the secrets of a practitioner's success is that I he has varied from the traditional burndown chart and sprint estimation suggestions that are taught when a person learns about Scrum. If you have had issues with making accurate burndown charts that reliably tell you when your sprint will finish, then perhaps his suggestions can help.