Create New Project

Creating a new project area has never been easy with RTC version 4.0. Here are the steps in creating a new project in JazzHub 4.0 RC2.

  1. Visit https://hub.jazz.net/. Log in using your JazzHub username and password.
  2. Click on the Create a project link.

  1. Select an appropriate process template. Click Next.

  1. Fill in the required fields concerning project area details. Click Next.

  1. Check the checkbox to agree to the JazzHub Terms of Use. Click Create Project.


Add Users to Project Area

Add Users

Inviting users to your project area is relatively simple. This assumes that the user has access to your repository, that is, RTC server with a username and password.

  1. Visit https://hub.jazz.net/. Log in using your JazzHub username and password.
  2. Click Invite people to join link in the home page. Invitation screen pops up.

  1. Enter a new user's email address. NOTE: The user must have access to the RTC server.
  1. Click Invite.

Change User roles

A user can have one login to an RTC server, but can access many projects in the said server with different roles. These roles affect what the user can do within the project area. Assigning roles to a user is easy as long as the user has accepted the invitation to the project area.

  1. Visit https://hub.jazz.net/. Log in using your JazzHub username and password.
  2. Scroll down the home page and click the Members link on the bottom right side of the page. This load the project area properties.

  1. Scroll to the Members area and hover over the Actions column of the user you want to modify. Click on Process Roles. The Edit Process Roles window appear.

  1. Select a role you want the user to have and click Add. Note that each role has a specific set of activities, and their view of the project area will change accordingly. Also a user can have multiple roles.

Here are some of the descriptions of the roles.

Analyst - The person in this role represents customer and end-user concerns by gathering input from stakeholders to understand the problem to be solved and by capturing and setting priorities for requirements.

Architect - This role is responsible for defining the software architecture, which includes making the key technical decisions that constrain the overall design and implementation of the project.

Developer - This role is responsible for developing a part of the system, including designing it to fit into the architecture, possibly prototyping the user-interface, and then implementing, unit-testing, and integrating the components that are part of the solution.

Project Manager - This role leads the planning of the project, coordinates interactions with the stakeholders, and keeps the project team focused on meeting the project objectives.

Release Engineer - This role is responsible for software builds and releases. Responsible for the design and development of builds, scripts, installation procedures, and systems including source code control and issue tracking.

Stakeholder - This role represents interest groups whose needs must be satisfied by the project. It is a role that may be played by anyone who is (or potentially will be) materially affected by the outcome of the project.

Team Lead - This role technically leads a component and is responsible for planning and architectural integrity of the component.

Tester - This role is responsible for the core activities of the test effort. Those activities include identifying, defining, implementing, and conducting the necessary tests, as well as logging the outcomes of the testing and analyzing the results.

  1. Click OK. Then click Save to persist project changes.