Project knowledge, which was notionally introduced in the previous chapters, is fully contextualised and defined in this chapter. The chapter begins by explaining what currently happens in the traditional project delivery regarding project knowledge. The complete definition of PKM is provided. At the end, an example of PKM is given to explain how it might look.

Traditional Project Knowledge Management

Knowledge, which is the combination of experience and research, is necessary to help IT industry, just as it is for all the other industries. IT industry will have two aspects: domain and technology. Domain is the collective knowledge, driven primarily by processes. Technology has implements such as programming languages that help putting that knowledge into useful outcome, most of the time it is software. Technology primarily helps in automating processes.

The automation that typically results in creation of software, is delivered via a project or programme. Knowledge plays a crucial role in software development and consists of business and technical knowledge. Typically, a software development project consists of four knowledge-intensive phases. The phases along with the document representing that phase is listed below:

This combination of knowledge is called ‘Project Knowledge’. Let us now understand how the Waterfall and Agile methodologies manage this project knowledge.

Project Knowledge Management in Waterfall Methodologies: Document Driven

Project knowledge is managed in the Waterfall methodology using documents. The main documents representing project knowledge are:

Documents are authored by relevant stakeholders and are subject to review by the project team and SMEs, who may or may not be part of the project team. Post review, the documents are singed off and once a document is signed-off, changes to it are managed by version control. The next version of the document is also subject to the review cycle. Every time the next version of the document is signed-off, the information needs to be communicated to the entire project team.