Document and automate development processes using rational method composer and jazz (iv)

Create a new process asset

Scenario: Creating a new process asset

In parts 2nd and 3rd of this series, we learned how the Business Recovery matters (BRM) team of the Jke organization quickly configures its project environment and starts in a number of hours rather than days. The team uses validated success patterns to create plans and work items. Each work item provides links to relevant guides and contextual guides that enable team members to quickly master the team's processes. This article describes how the Jke team creates new process assets.

Jke is rapidly expanding into new business areas, recruiting people to fill vacancies. The company needs more powerful HR software to manage its resources. They decided that using a commercially available (COTS) software, and adapting it to their own needs, would be less time-consuming and more cost-effective than in-house development of new HR software. However, the company had no previous experience in selecting, adjusting, and deploying commercial software, so they needed a process to guide them through the work.

The team responsible for developing HR software borrowed Peter from the BRM team because of his expertise in IBM Rational method Composer. They studied the process library contained in Rational method Composer and found a set of practices to guide them through the task of selecting, adjusting, and deploying COTS software. They decided to follow these practices and help them to complete the new project. They also decided to automate the process at IBM Rational Team concert, allowing teams to strictly follow process guidance.

The following team members are related to the scenario:

Peter, Process Engineer

Kelly, project Manager

The following sections describe the actions of team members.

Customizing the process in the Rational method Composer

Peter has a Rational method Composer license, and he confirms that the entire HR development team has a content reader license.

Create a team process

Peter found a guide in IBM Technote, known as the "How to create" team process.

In the Rational method Composer Practice Library, he opens the team process perspective, which supports minor changes to the process.

Peter chose the COTS method configuration and created a new team to name it Jke HR Dev. Changes are automatically placed in the Jke HR custom plug-in instead of changing the original plug-ins provided in the library.

Peter will perform the following tasks:

In the Team Process Navigator tab, under Getting Started, he adds a new supporting Material, which is named HR Systems topology, so access to the document can be simple.

He renames the stakeholder role to HR stakeholder, so the role name is consistent with the terminology used in Jke.

Figure 1 shows the changes that have been made.

Figure 1. Make simple changes in the team Process perspective