When I got involved in the Process Knowledge Initiative to help create an open-source body of knowledge, I knew that the first part, with all the forming of committees and methodology and such, would be a bit excruciating for me. I was not wrong. However, it has been thankfully short due the contributions of many people with more competence and patience in that area than I, and I’m pleased to announce that we’ve put together an initial structure and will soon be starting on the fun stuff (in my opinion): working with the global BPM community to create the actual BoK content.
From our announcement earlier this week:
The month of November was a busy one for the Process Knowledge Initiative. In execution of our startup activities, we defined the PKBoK governance process and technical team structure, recruited our first round of technical experts, and secured preliminary funding via our Catalyst Program.
On the PKBoK development side, the team is actively researching and defining the candidate knowledge (or focus) areas in preparation for a January community review release.
With the knowledge area release, the development of the PKBoK becomes a full community activity, from content contributions, working group collaboration, and public commentary to content improvement and annotation.
It’s impossible to do something like this without some sort of infrastructure to get things kicked off, although we expect most of the actual content to be created by the community, not a committee. To that end, we’ve put forward an initial team structure as follows:
- Technical Integration Team is responsible for establishing the PKBoK blueprint (scope, knowledge areas, ontology, content templates), recruiting working group leaders, and coordinating content development, publication and review.
- Methodology Advisory Board provides guidance and support on PKBoK development and review processes. The Methodology Advisory Board does not participate in content creation or review; rather it provides rigor to ensure the final content represents the community perspective.
- Technical Advisory Board provides expert input to, and review of, deliverables from the Technical Integration Team and Working Groups. Technical Advisors may lead, or contribute content to working groups within their area of specialization.
- Working Groups develop PKBoK content for a particular knowledge area, task or set of tasks. Working groups will form via public calls for participation. The first call is planned for April 2011.
- BPM Community reviews, contributes to, and consumes the PKBoK. All BPM community members are welcome to participate in the development of the PKBoK or utilize the delivered content in their individual BPM practices.
You can see the people who are participating in the first three of these in the announcement – including academia, industry analysts, standards associations, vendors and end-user organizations – and we’re looking for more people to join these groups as we move along.
Most of the content creation will be done by the working groups and the global BPM community; the other groups are there to provide support and guidance as required. We’ll soon be putting forward the proposed knowledge areas for discussion, which will kick off the process of forming the working groups and creating content.
I’m also starting to look at wiki platforms that we can use for this, since this really needs to be an inclusive community effort that embraces multiple points of view, not a moderated walled garden. This open model for content creation, as well as a liberal Creative Commons license for distribution, is intended to gain maximum participation both from contributors and consumers of the BoK.