This is the final installment of four articles tying the concepts, values, and principles of Agile and Scrum to the Customer Experience discipline. I introduced the series here, and parts one, two, and three are here, here, and here. In this article, I’ll dive into the concept of embracing change. Specifically, the Manifesto highlights this aspect of Agile project management as preferring to respond to change rather than following a plan.
Now, the idea here isn’t to not have a plan or that planning is somehow bad or discouraged. But keep in mind that the genesis of Agile as an approach to project management was a rejection of the rigid nature with which some PMs follow a plan, ignoring or wishing-away changes to the environment around them. As I mentioned in an earlier article in this series, when Customer needs change (as they always do), it won’t do to simply follow the plan as originally written and expect good results. (more…)