Comments for The Blending of Traditional and Agile Project Management at http://www.projecttimes.com , comment 1 to 3 out of 3 comments http://www.projecttimes.com Sat, 31 Jul 2010 03:03:00 +0100 FeedCreator 1.7.3 http://www.projecttimes.com/agile/the-blending-of-traditional-and-agile-project-management.html#comment-172 There is never project that could be managed purely as 'waterfall' or as an 'agile'. In waterfall project process you will find certain components that are developed iteratively and in agile there are some steps that will have to be delivered sequentially due to constraints or dependencies. It is us, the project managers - who created this distinction to address risks related to poor communication during the project (detailed requirements) or various skills of the project manager (detailed process). In reality, in any type of project we should communicate well, be flexible to adopt the change requests and manage the scope adequately. So this blending is nothing new, it is just going back to origins of project management, before it became deformed by splitting into various methodologies. This distinction of the approach should however be made based on uncertainty of the projects. Some projects are more risky then others, and they require more attentiveness then those that are routine ones. In uncertain situations agile approach will benefit the team more then the 'waterfall'. The bottom line is - there is no - one size fit all. - andre_kaminski Thu, 12 Mar 2009 09:49:10 +0100 http://www.projecttimes.com/agile/the-blending-of-traditional-and-agile-project-management.html#comment-171 Interesting article and it makes some sense, however would it not be more difficult to manage scope? - joysmith1 Thu, 12 Mar 2009 08:13:33 +0100 http://www.projecttimes.com/agile/the-blending-of-traditional-and-agile-project-management.html#comment-170 I am pleased to see more recognition that many projects today do not fit the waterfall model of the 50's. Many PMO's are still stuck in that world and slow to adapt. I have found that agile is a much more productive approach and allows you to focus on results. Change is slow however, as I have seen PMO's create "phases" so they can get agile iterations to fit into a waterfall mentality. This forces PM's to have to create full-blown waterfall deliverables for each agile iteration, including a Charter. - zebhead Wed, 11 Mar 2009 15:48:14 +0100