PROJECT MANAGEMENT

Project Management

Table of Contents

OUTLINE3

PART I3

Purpose3

Analysis of Motivations towards the Project3

The Spiral Model Of Project Management3

Main Requirements of the Project4

Creating/Maintaining User Accounts5

Role Maintenance5

Project Management Organization7

Major Tasks to be Carried Out10

Costs & WBS13

Risk Analysis16

Major Risks That Could Affect the Delivery of the Project17

Gantt Chart19

Critical Path Analysis19

Stakeholder analysis22

Direct and Indirect Costs and Project Crashing23

Stakeholder Map24

Project Team Structure25

Memo27

Summary28

PART II28

References34

Managing Time and Quality

OUTLINE

The purpose of this assignment is to produce a project management system which will result in increasing the sales volume with the help of e-commerce. Originally, the toy maker used SolidWorks software for every object but found that creating human-like figures-dolls, for example-was too constraining with an engineering tool.

PART I

Purpose

To increase sales by extending e-commerce services online.

Analysis of Motivations towards the Project

The outcome of this project is in itself a motivation towards completing this project. This project will result in increasing the sales volume of the company by implementation of an e-commerce system.

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.

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

Next step is defining human resources in terms of category, seniority and hourly cost:

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

Superclasses will be developed for use in zuausr to establish workflow users. 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 which 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 modeling 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.

New Account Administration Role - Account Administrator

A new role called “Account Administrator” ...