The Project Coach

All too often I hear about organizations that declare “We are now Agile…” or someone in management looks at the development team and says: “go forth and be Agile…”, and then throws them to the wolves to figure out how without any training. Some in the leadership may embrace it enthusiastically and say “we need to be more agile…”, while others are complete skeptics and believe that without all the usual documentation, no work of any quality could possibly be getting done. Indeed one of the biggest challenges in trying something new like agile practices in an organization is managing expectations of the leadership. › Continue reading…

Undoubtedly, the masters would agree hands down that the recommended approach for any project team practicing agile methods would be co-location. The benefit of this arrangement is all the casual conversation that team members naturally tend to engage in, or are forced to overhear from their co-workers, which in turn promotes collaboration on the project – or so the theory goes. Unfortunately with the fabric of today’s multi regional, global, or outsourced organizations, co-located teams are not always an option. › Continue reading…

In my last article I discussed characteristics and roles of the agile scrum methodology as compared to waterfall.  In this continuation article, I committed to examine the artifacts, meetings and processes involved and also discuss what they compare to in a waterfall context.  By design agile and the scrum methodology deliberately minimize processes, artifacts and meetings › Continue reading…