When teams switch to Agile/SCRUM Product development there is a change in how things are done and many times it appears as if there is a conflict between the PMBOK practices and Agile methodology.
In reality this need not be the case, agile practices can easily fit into PMBOK constructs and help develop products in a faster,leaner way. Similarly PMBOK prctices which looks like they are more suited for Waterfall development can be adapted to Agile methodology easily if we undersatnd the mapping between the two. The mapping of PMBOK and Agile methodology can help getting Agile accepted by the enterprise without much difficulty.
PMBOK guide says Projects are accompolished through process and espouses major processes that needs to applied in every project some form of the other to successfully complete the project. These processes are aggregated into five groups defined as the Project Management Process Groups:
- Initating Process Group
- Planning Process Group
- Executing Process Group
- Monitoring and Controlling Process Group
- Closing Process Group.
With this concept behind the PMBOK Process groups it becomes very easy to map the Agile Process Flow to the PMBOK process group flow. Let us see how this plays out.
The PMBOK process groups are not alien to the Agile/Scrum process flow. This kind of mapping can be used as a starting point of the conversation between the Scrum product owner and Project Manager to identify how the Agile mode of working can co exist with the enterprise level PMBOK processes in the organization.
No comments:
Post a Comment