Project Management



Project Management

Introduction

The purpose of this paper is to analyze the possibility and requirements of opening a new building. The paper emphasizes on all the aspects of the requirements and skills to be used by the project manager as well as the overall process of project management that has to be implemented to execute the opening of the new building. The paper also discusses about the activities required to successfully manage the new initiative.

Discussion

The Spiral Model of Project Management

The spiral model is based upon the principle that we go through the different phases again and again, until we reach a certain degree of maturity of the product to be created which e.g., a customer can accept. It is even possible that one part of our project is still in definition phase while another one is already in implementation phase. Typical examples of this iterative approach would be IT projects, i.e. the design and development of products and services in the IT industry with its short innovation cycles and high probabilities of changing requirements during implementation phase.

Main Requirements of the Project

To advertise and recruit required professionals.

To analyze and document the specifications for the required functionality.

To acquire the needed hardware and software as part of IT infrastructure facilities (Dobson, 2003,, 102).

To design, implement, test and operate the entire system.

Next step is defining human resources in terms of category, seniority and hourly cost: (Dobson, 2003,, 102).

Functional expert(s) - Knows the business process

Technical support - Technical product knowledge

Workflow Business Analyst - Workflow tools expert

System Administrator- Maintain workflow environment

Business Analyst - assist in doing a business process analysis

Creating/Maintaining User Accounts

Super classes will be developed for use in to make the new building. Creating the user accounts and resetting passwords will be the responsibility of the Technical Services group and will follow our existing practices, with the exception of passwords. Passwords will be maintained following the procedure described in the workflow system administration guide who allows for the user's Banner and workflow passwords to remain synchronized.

Role Maintenance

Standard Workflow Role - System Administrator

The standard workflow role called “System Administrator” will be assigned to programming staff and Functional staff. This role allows for managing the enterprise, roles, passwords, business events, categories, product types, component types, technology types, user accounts and modelling workflows.

Standard Workflow Role - Business Analyst

The standard workflow role called “Business Analyst” will not be assigned to anyone. A new role will be created which includes some of the Business Analyst functionality and will be assigned to workflow developers (Kerzner, 2003,, 68).

New Account Administration Role - Account Administrator

A new role called “Account Administrator” will be established. This new role will allow for establishing and maintaining user accounts, passwords and user-role assignments. This role will be assigned to Technical Services account administration staff (Kerzner, 2003,, 68).

New Developer Role - Workflow Developer

A new role called “Workflow Developer” will be established. This new role will allow for creating/maintaining roles, user-role assignments, fixing and modeling workflows, business processes and attaching workflows to business ...