by Kevin Aguanno, CSPM (IPMA-B), Cert.APM, PMP, PMI-ACP, CSM, CSP, FPMAC, FAPM
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.
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.
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.
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.
Are you a stickler for "agile rules" when using agile project management? Don't be! That's just one of the lessons this practitioner has learned over the years through hands-on experience succeeding—and failing—while working on agile efforts.