Taking an Agile approach to software development for the first time is no small task: there are a number of different practices to onboard and process change is disruptive, frustrating and potentially demoralizing. How do you onboard Agile practices and still meet delivery requirements? To what extent can these be introduced, especially the first time around, so that they stick?
There are two things to balance when introducing new practices: adopt at a pace that doesn't push too far too fast and simultaneously establish a "critical mass" of core practices to reap symbiotic benefits. While there are no hard-and-fast rules on how or where to begin, the right sequence can increase probability of success and set the stage for greater process adoption.
So You've Decided To "Go Agile" - A Pragmatic Approach To Onboarding Agile Project Management
Potentially the main document I need to think about, and digest, this week I think.
Comments