Agile PM Process Grid-3.9 Knowledge Sharing


In John Stenbeck’s book “PMI-ACP and Certified Scrum Professional Exam Prep and Desk Reference”, he creates an “agile project management process grid” which describes 87 processes used in agile project management.   These processes are divided into five process groups (Initiate, Plan, Iterate, Control, and Close), which are analogous to the five process groups in traditional project management, and seven knowledge areas which can be mapped, more or less, onto the ten knowledge areas in traditional project management.

I am now covering processes that are performed during the Control process group of an agile project.   Remember, after the Planning process group, an agile project does not go in a linear fashion from Iterate to Control to Close; rather, it cycles from Iteration to Iteration with periodic checkpoints (many times at the end of an iteration cycle) where you Control or make changes to a project to make sure it gets back on track.   Or sometimes, you even change the track itself if there is a change in the requirements.

In the past set of posts, I have covered those processes done in the Control process group that relate to the fifth knowledge area of Risk Management.   Today I start covering the process related to Communication:  3.9 Knowledge Sharing

1. Skill-related Knowledge Sharing

One of the best long-term investments in a company is not a senior person with highly developed skills, but a senior person with high developed skills who is willing to transmit these skills to junior members.    This allows the junior members to fill additional roles when the team is stretching to reach an iteration goal.

2. Project-related Knowledge Sharing

When a technical challenge is presented that requires the team to explore a possible solution (sometimes referred to as an exploratory spike), it is good to have someone who is experienced about things that work as well as things that don’t work.   This can help the team in an open space meeting when possible solutions are being evaluated.

3. Process-related Knowledge Sharing

This means sharing knowledge related to agile practices and agile frameworks.   This not only is useful within teams, but within teams as well.   Such an exchange of knowledge is beneficial for delivering on process improvement activities.

The next process covers the last knowledge area of Continuous Improvement, namely, 7.6 Process Analysis.

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: