Integrating UX into an Agile process is not always an easy challenge. In this article, Mike Bulajewski reminds the why the differences between the two vision exist in the first place and proposes some solutions on how they could be solved. This article provides a very interesting point of view of the Agile-UX relationship from the UX side.
We’ve all been there. You release a new feature, product or service, only to find it isn’t quite what your customers want or need. But by the time you release, it’s too late to make significant changes. Traditionally user experience design has involved a significant amount of upfront user research and design, to ensure we build products that meet customer needs. But this approach doesn’t always work so well within an Agile development environment.
Technical debt is one of this great new metaphor that is applied to software development and more specially to agile project management approaches like Scrum. As its financial counterpart, technical debt is not necessary a bad thing as long as you are able to manage it wisely. In this article, Don Reinertsen will help you to put some numbers on the costs and benefits of your technical debt.
In his book Agile Reflections, Robert Galen has aggregated multiple articles that he wrote about transitioning to Agile for the online publication PM Times. The book is based on his experience as in Agile coach helping companies in different phases of their transition to Agile software development.
Scaling and implementing an Agile approach in large projects is one of the hot topic in the Agile community, a natural consequences of the adoption of Agile by larger corporation. In this blog post, Ritika Nanwani shares some of her observations as a member of a large Scrum project.
Many organisations have been swept up in agile process adoption, with good reasons! The Agile Party is coming to a close and many organisations are now beginning to look at where they are and have come to the disheartening realisation that, rather than in a new world of embracing change and competitiveness, they have a lot of new processes, not much to show for it, and people are disillusioned enough to begin to revert to older, familiar ways… This is the unfortunate age of the ‘agile hangover’.
Sprint retrospectives are the most discussed form of retrospectives in Scrum. You can however the same self-analysis and continuous improvement technique to other items of Agile project management. In this article, Madhavi Ledalla discusses release retrospectives.
Scrum Expert Copyright © 2009-2025 Martinig & Associates