Continuous improvement is one of the main values of Agile and retrospectives should play an essential role in supporting this process. In his short and free book “Agile Retrospective Kickstarter”, Alexey Krivitisky provides some exercises that should help Scrum teams to get the most out of their retrospective meetings.
As Agile matures and learns from experience, it is clear that the Agile business analyst has a significant role to play. This interactive and musical session will explore the relationship between Product Owner and Business Analyst, their responsibilities and the skills needed. I’m an Alien … I’m a Business Analyst in an Agile world!”
Technical debt is a well-known concept in Agile software development. Technical Debt is defined as the eventual consequences of poor or evolving software architecture and software development within a codebase. In this blog post, Steve Blank discusses the concept of organizational debt.
Making decisions in groups like Scrum teams is our daily bread. Together we ponder over the right architecture, we select tools and set rules that we should follow as a software development team. In case of errors we discuss and decide how to get rid of them once and for all. We discuss, exchange point of views, bring arguments… or even yell at each other.
If delivering business value should be the main goal of a software development project, not all the developers’ activities are contributing to this objective. In his book ” Scrum Shortcuts without Cutting Corners”, Ilan Goldstein discusses how you should deal with bugs and the technical aspects of your software project.
Agile is a now mainstream method used in IT project management. Yes, Agile and Scrum are now considered as a method and no longer as a philosophy. Everyone wants to “do” Agile and thus want to “be” Agile as well, but what are the common mistakes in applying Agile?
There’s a debate raging in the Agile world around the #NoEstimate concept: should we estimate, or not? Lost in the noise are more important questions: When should we estimate, and why? When should we not estimate, and why not?
Scrum Expert Copyright © 2009-2024 Martinig & Associates