In Agile Product Management , when product owners gets introduced to Scrum frame work, most of the time they have difficulty in transitioning from the detailed requirements world of traditional PMI world to the nebulous world of User Stories that are not really complete. But once they get coached on the fundamentals of what a User Story is and how to write them, their natural skill as a product manager accelerates their expertise on writing effective user stories.
Last week I had such an opportunity to conduct coaching sessions for the product owners in our team on writing effective user stories.
A Blog on Product Management, Technology, Digital Marketing, Online Advertising and Agile/Lean/Scrum Practices by Anantha Narayanan (aka) productzen
Showing posts with label Product Management. Show all posts
Showing posts with label Product Management. Show all posts
Saturday, March 3, 2012
Wednesday, July 27, 2011
Agile Mapping for PMBOK Process Groups
Most of the organizations that develop software products employ standard project management practices and expect their employees to follow those process in their daily work at the organizations. In many of the prodcut development efforts that I worked I have had a Project Manager trained in PMBOK practices help manage the project at the enterprise level.
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:
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.
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.
Labels:
Agile,
PMBOK,
Product Management,
Project Management,
Scrum
Subscribe to:
Posts (Atom)

