There are several typical challenges and notions that commonly arise during a transition to Scrum. . . .
Multi-vendor and cultural nuances pose a challenge to assimilating and digesting Scrum values and principles. . . . The fundamental Agile values of openness and transparency take a hit.
In my view, you are Agile only if . . .
Hand-offs between multiple stakeholders is becoming a challenge for managed services in Agile. The application of Agile practices and principles have become subjective, and teams interpret and implement as per convenience, tending to move toward Waterfall. . . .
As the day goes by in a typical CSM class, I get a lot of "what if?" questions from students. . . .
When the customer does not know what they want, the trouble begins. . . .
Agile IT development came along . . . and showed us how IT development can be done faster and better. But it did not exactly make it easy for the onsite-offshore model.
When we use the term "Lean Coffee," we are not talking about a soy latte. We are talking about a technique that can prove very effective when working with relatively small numbers of people . . .
Being the Scrum enthusiast that I am, and having taught teams and organizations to use burn-down charts many, many times, I thought of using one to track my progress for something that I do daily: going to work. . . .
Why did the federal and state governments, on something as high profile as health care reform, decide to use Waterfall, a risky 40-year-old process, to manage the delivery of health insurance exchanges?
In today's changing world, with social stimulation going on at every moment, it is impossible to use traditional methods to deliver needs as quickly as markets turn. . . .
There can be a number of reasons for failure when implementing Agile. In my experience, the following are the major ones. . . .
The history of humankind offers lots of remarkable ideas and innovations in strategy and tactics. There has been no area where people showed more inventiveness than in defending themselves or attacking and conquering others. This article brings forward similarities between war strategies and software development methods. . . .
As a ScrumMaster/Agile coach, at times I find making decisions in groups (or making groups make decisions) rather difficult, particularly in meetings where the decisions are made at the end by impatient, tired people. . . .
[Some] software projects, especially maintenance projects, normally do not have full-time product owners . . . sometimes there is more than one product owner. This article aims to showcase a mitigation plan that can be handy and effective in overcoming Scrum violations in the product owner's case.
This article talks about joint retrospectives -- why they are needed, who participates, when and where they are held, how they are handled, and their benefits and challenges.