5 Roles and Responsibilities of Project Management.

There five major roles, Such as,

1. Customer,
2. Manager,
3. Architect,
4. Developer,
5. Tester,

and each role has a number of specializations. Depending on the size and complexity of the project, the team may have many participants who specialize or combine specialties. In general, a single individual should not perform cross-role specializations.

The customer is the provider of requirements for the project. In this context, a customer includes the project sponsor and the end users. The customer can assume the following specializations or combine them:

• The Business Process Designer is responsible for modeling the business. The business process designer is a subject matter expert in the performance of the business process under consideration. The business process designer is highly available to the project team.
• The Business Process Reviewer is responsible for reviewing the business model for completeness and accuracy. This specialization is important when the business process is informal, new or is undergoing substantial change.
• The business model is eventually translated into requirements. The Requirements Reviewer is responsible for reviewing the requirements for completeness and accuracy.

The Project Manager is responsible for ensuring that the project reaches a successful conclusion. There are two specializations:

1. The Tracker is responsible for tracking the issues list. This specialization is useful when the number of outstanding issues the project generates warrants a dedicated focus.
2. The Coach is responsible for advising the project team. This specialization is useful when the project is of a sensitive nature, explores new areas of automation, or to enhance the experience level of the project team. Typically, the coach is a senior a senior management resource.

The Architect is responsible for ensuring that the solution will operate cohesively within the customer’s information technology infrastructure. There are five specializations:

1. The Business Process Analyst works with the Business Process Designer to create detailed models of the automation of the business process. This specialization is useful in particular for re-engineering efforts.
2. The Use Case Specifier defines the user stories or use cases that describe the scenarios the end users will apply within the solution. This specialization is always present in projects.
3. The Database Designer defines the logical and physical data model of the solution. The database designer integrates the solution’s data model into the customer’s enterprise data model. This specialization is always present in software projects.
4. The Architecture Reviewer is responsible for reviewing the architectural artifacts of the project and advising the project team on their consistency with best practices and customer specific practices.
5. The Design Reviewer is responsible for reviewing the design of the solution and ensuring that the design is an appropriate translation of the architecture. This specialization is always present in projects.

The Developer is responsible for the engineering and implementation of the solution. There are six specializations that are always present in projects:

1. The System Analyst is responsible for decomposing requirements into system components.
2. The User Interface Designer is responsible for defining the user interface of the solution.
3. The Designer is responsible for defining the design of the solution.
4. The Implementer is responsible for building and testing system components, hardware or software.
5. The Test Designer is responsible for translating the use-cases into test cases that will demonstrate the functioning of the solution.
6. The System Integrator is responsible for insuring that the solution will properly operate within the customer’s computing environment.

The tester is responsible for auditing the project artifacts to verify that they are consistent with the expected results of the solution, and that they comply with the organizations best practices and customer specific practices. There are three specializations that are always present in projects:

1. The Component Reviewer is responsible for auditing a particular component of the solution and verifies its compliance with SCI best practices and customer specific practices.
2. The Integration Tester is responsible for testing that the solution will operate within the production computing environment.
3. The Performance Tester is responsible for testing that the solution will perform within the expected time frames.