{"id":170,"date":"2009-01-29T14:41:32","date_gmt":"2009-01-29T12:41:32","guid":{"rendered":"https:\/\/fucinaweb.com\/en\/?p=170"},"modified":"2009-01-29T14:41:32","modified_gmt":"2009-01-29T12:41:32","slug":"pmbok-and-agile-development","status":"publish","type":"post","link":"https:\/\/fucinaweb.com\/en\/pmbok-and-agile-development\/","title":{"rendered":"PMBOK and agile development"},"content":{"rendered":"

A Guide to the Project Management Body of Knowledge<\/a><\/em> (PMBOK) is considered the bible of project management. Bible in that it deals with every facet of project management by means of 5 process groups (initiating, planning, executing, monitoring and controlling, closing). Bible also for its size, more than 400 pages packed with concepts that often scare who is studying to become a Project Management Professional.<\/p>\n

Thanks to this reputation, concepts expressed in the PMBOK could seem far from the agile development methodology<\/a> and some weeks ago I expressed my opinions regarding this topic<\/a> in the Web Project Management FAQ.<\/p>\n

And now Forrester publishes on its site an interesting (but not free) report, The PMBOK and agile: friends or foes?<\/a>, that deepens these arguments.<\/p>\n

Starting from the differences between PMBOK and agile development, the authors soon highlight several points of contact between these 2 approaches. But it’s the last part of the report, where they state that it’s possible to combine the strengths of both to optimize outcomes, the more interesting.<\/p>\n

In particular, an agile developer can find in the PMBOK:<\/p>\n