Reference no: EM131036643

In this task, I need you to create a documentation for the software called 2Plan

Learn about 2plan

https://2-plan.com/

https://en.wikipedia.org/wiki/2-plan_project_management_software

You can also do your own research.

Your document should include the following

1. Overview.. 3

2. Goals and Scope. 3

2.1 Project Goals. 3

2.2 Project Scope. 4

2.2.1 Included. 4

2.2.2 Excluded. 4

3. Organization. 4

3.1 Organizational Boundaries and Interfaces. 4

3.1.3 Resource Owners. 4

3.1.4 Receivers. 4

3.1.6 Suppliers. 5

3.2 Project Organization. 5

1. Overview

Help:   This section describes a management summary. Provide essential information like

• What the motivation for this project is (e.g. to fill a gap in the product portfolio)
• Who the customer is
• What the project will deliver. Is it a new product or an extension of an existing one?
• What it will cost
• How long it will take
• Which organizations are involved
• Which other projects depend on the project result
• Which other projects contribute with their results

Refer to the Project Proposal [1] or other documents (e.g. Feasibility Study Report) containing information on the project background like market, technology, profitability, and competitor evaluation.

2. Goals and Scope

2.1 Project Goals

Help: The project goals define the expected project results together with the required development constraints. Information may be extracted from the Project Proposal [1] (or the Feasibility Study Report) and the Project Requirements Specification and completed, if required.

Identify the various categories of project goals (list the major project goals only and refer to the Project Requirements Specification or other documents for details). Consider the following categories:

• Functional goals
• Strategic goals
• Business goals (e.g.: time-to-market, cost)
• Technological goals
• Quality goals
• Organizational goals (e.g. competence development, testing of new methods, techniques, or tools, application of new processes, etc.)
• Other goals, e.g.: usability, portability, etc. (these goals, and what is specifically expected, should be clearly specified in the Project Requirements Specification)
• Constraints (e.g.: environmental constraints, application specific standards, national standards, cultural relationships, etc.)

Prioritize the project goals:

Functional, business, and quality goals should be prioritized at least.

Project Goal	Priority	Comment/Description/Reference
Functional Goals:	2	For details see the Project Requirements Specification [2]
<functional goal #1>
<functional goal #2>
Business Goals:
<Time-to-market>
<efficiency, cost, quality>
Technological Goals:
<technical goal #1>
Quality Goals:	2
<quality goal #1>
Constraints:
<environmental>
<appl. specific standards>
<national standards>

2.2 Project Scope

Help: Clarify what the project will (and will not) deliver, in order to avoid future shifts in the level of ambition.

2.2.1 Included

The deliverables of this project and their receivers are listed in detail in the delivery plan in chapter 10.

2.2.2 Excluded

Help: State what is specifically excluded from the project but what the customer may expect to be included. This could, for example, be clarifying that training of end-users is excluded.

This project will exclude ...

3. Organization

Help: Describe the internal project organization and all organizational issues affected by the project result or the project is dependent on.

You may extract information from the Project Proposal [1] (or Feasibility Study Report).

3.1 Organizational Boundaries and Interfaces

Help: Describe the environment that the project is embedded in. Identify external stakeholders the project is dependent on and who are affected by the project result. Describe the administrative and managerial boundaries between the project and each of the following entities: the parent organization, the customer organization, subcontracted organizations, and any other organizational entities that interact with the project.

3.1.3 Resource Owners

Resource Owners are defined in the Resource Plan in section 5.1.

3.1.4 Receivers

Receivers are defined in the Delivery Plan in section 10.

3.1.5 Suppliers

Help: A Supplier is an external organization contributing to the project with an existing product (COTS = Commercial Off The Shelf) that is incorporated into a project deliverable (e.g. a database system) or used for project support (e.g. tool, equipment).

Identify all external suppliers and their deliverables. State any special arrangements or procedures that will be used in contacts with the suppliers. Name contacts, if applicable.

Company:  Contact	Deliverable	Comment

3.2 Project Organaization

Help: Describe how the project is organized. Describe what subprojects and other areas of responsibility are planned. Identify and staff all steering functions, project management functions, and execution functions.

Graphical illustrations such as hierarchical organization charts or matrix diagrams may be used to depict the lines of authority, responsibility, and communication within the project.

All work should be original please don't copy and paste other people's work

The length of paper should be about 3 pages.