| Problem |
Difficulties in sharing the (intermediate) work results in the project team.
|
| Initial Context |
A new project has been started and the deliverables required from the project are known (see Shared Understanding, KSP05).
|
| Roles |
Project team members of a project. Project Manager, Release Manager or some other role. For simplicity here the role Project Manager is used.
|
| Forces |
Project team members can not work fully separated. They must cooperate to achieve the results required in the project. Results from a project might be software code, documents, designs, etc. To work effectively the team must have ways to share this knowledge with each other and to know what the others need and what they produce.
Because parts of software need to be implemented by different persons, integration and the working of software modules together is critical.
|
Solution
|
To have the basic infrastructure existing for sharing work result knowledge in the project team the project manager (or another named person in the team) should do the following.
- Define Intermediate Results. Based on project deliverables (see Shared Understanding, KSP05), define the required intermediate results.
- Check Reuse Possibilities. Check if the work results from earlier projects could be utilized in this project (see Quickly Made, KSP13).
- Define Integration. Define the principles of integration and required tools in this project. Initiate establishing required environment.
- Define configuration items of this project and their requirements for configuration management.
- Define Data Management. Define how (intermediate) work results are stored and shared in the project. Define and initiate also the use of a selected configuration management system. Define how to handle software code, documents, designs etc. And how to combine those to builds and releases. Initiate establishing required environment.
- Define Guidance. Define required guidance for intermediate results, integration, configuration and data management.
- Introduce Guidance to other project team members and possible other relevant stakeholders.
- Study Guidance and Implement Project according to it.
|
| Resulting Context |
Required intermediate results and how to find those are known in project team. Agreed integration and data management known and in use making possible cooperation and separate sub teams working with separate tasks.
|
| Instances |
To be used when a new project is initiated. The utilization of the guidance continues till project is closed.
|
| Process Connection |
Software engineering.
|