PMBOK Supplementing Agile Processes

SHARE
Request to reuse this
Add to my favorites
Topics: Agile

On various platforms, we have been discussing the popularity of agile practices. There is no smoke without fire--the credit doesn't come without the real value each of these agile frameworks provides. While agile processes focus on time-to-market product delivery, continuous stakeholder engagement, embracing the changes even at a late stage and most importantly developing a highly efficient team, these processes are, in fact, abstract in nature.

There are several aspects left open to the agile teams. So why can't we take advantage of PMBOK (Project Management Body Of Knowledge) to fill in these aspects?

Let's look into some of these aspects:

• Scrum (one of the popular agile frameworks) gives stress on building a self-organizing and cross-functional team. But it doesn't mention how? The idea of a self-organizing team is cool, but sometimes it can paralyze the team. We cannot deny the fact that the team is built on a set of individuals with differing expectations and hence conflicts at earlier stage of team development is inevitable. This is the time to look into PMBOK- Project Human Resource Knowledge Area.

• Identifying stakeholders is a crucial activity in both traditional and agile processes. Frequent product delivery, built within the agile framework, ensures a direct communication and cooperation from stakeholders and …

Please log in or sign up below to read the rest of the article.