Customer logo here Project Name: Project Charter Company logo here Project Name: Project Charter The blue-colored text passages within this document are tips and guidance for filling out this...

1 answer below »
Complete the project charter using the guidlines provided
Customerlogo hereProject Name: Project CharterCompanylogo hereProject Name:Project CharterThe blue-colored text passages within this document are tips and guidance for filling outthis template. If you are ready with your first draft, you should delete these passages before sending the document to your sponsor.Project:Project NameTitle:Project CharterDocument number:Version0.1Document status:DraftAuthor:Doe, JohnResponsible:Date created:dd.mm.yyProtection class:"For internal use only"The Project and Author fields are filled automatically with the data from the document properties (File Properties). Once the appropriate entries have been made here, these fields can be updated with the "Update Field" function (can be found in the context menu for the individual fields). Possible states for the document status include "Draft," "Released," and "Final." The status of the current document should be specified respectively in the field above.Document historyVersionDateAuthorComment/Change0.1dd.mm.yyDraftThe document history should provide an overview of the development of the document. Different versions with their date, author, and possible comments should be entered here.Tips for Using This Template:The Statement of Work (SOW) forms the basis for the project order. The project order represents a further level of detail. Information that is often only outlined roughly in the SOW has to be provided in greater detail in the project order. Furthermore, internal points can also often be listed in the project order, which are essential for project success.The blue text contained in the template should provide assistance for usage. It briefly describes how the individual elements and styles are to be understood. Please delete all of the blue text before you disseminate or print the document; it is intended exclusively for internal use.Page1Background/Project purpose or justification2Goals2.1Goals2.2Scheduling goals/milestones3Project product description4Delivery units4.1Delivery units/services5Project success criteria6High-level risks7Key stakeholders8Assumptions, restrictions and external dependencies9Responsibility of the customer9.1Tasks9.2Resources and staffing10Project category11Project budget (overview)12Project startup13Project end13.1Signatures for releaseAnnexA.Glossary and abbreviationsB.References, accompanying documents1 1. Background/Project Purpose or JustificationThis section describes why the project was initiated and how significant it is for the company.2 GoalsThis section describes which goals are to be realized with the project. These goals serve as a point of reference for the project closing. Measurable goals should be defined. 2.1 GoalsGoalDescription2.2 Scheduling Goals/MilestonesScheduleDescription3 Project Product DescriptionThis section describes the project end product to be supplied. Product Scope DescriptionThe product scope description documents the characteristics of the product, service, or results that the project will be undertaken to create. The description should also document the relationship between the products, services, or results being created and the business need that the project will address.4 Delivery UnitsA list of all project products/deliverables whose complete and satisfactory delivery indicate the completion of the project.4.1 Delivery Units/ServicesDelivery UnitDescription/CommentA deliverable is any unique and verifiable product, result, or capability to perform a service that is required to be produced to complete a process, phase, or project. Deliverables are typically tangible components completed to meet the project objectives and can include elements of the project management plan. Deliverables also include ancillary results, such as project management reports and documentation. These deliverables may be described at a summary level or in great detail.5 Project Success CriteriaThis section outlines the quantifiable criteria that have to be fulfilled so that the project can be performed successfully.Project Success Criteria6 High-Level RisksThis section describes some of the key project risks and their potential impact on the success of the project. This list of risks should be regarded as provisional rather than complete because risks are usually identified and dealt with continuously during the course of the project. RiskPossible Impacts on the Project7 Key Stakeholders This section should at least contain the key stakeholders with their names and roles in the project context. This is your starting point for further stakeholder management and analysis.NameRole8 Assumptions, Restrictions and External DependenciesAssumptions are expectations that form the basis for decisions. This section lists the main assumptions on the basis of which appraisals, plans, and methods are defined for the project.AREItemA = AssumptionR = RestrictionE = External dependency9 Responsibility of the CustomerThis section lists what the customer is to contribute in the course of the project. These responsibilities can be split into two categories.9.1 TasksTaskCommentContact9.2 Resources and StaffingResources/StaffingCommentContact10 Project CategoryAccording to the relevant requirements and experiences in the company, the project is classified based on the following predefined features.Project CategoryProject Categories:C Projects:B Projects:A Projects:ComplexityLowAverageHighRisk & Impact on CompanyLowAverageHighStrategic ImportanceLowAverageHighNumber of Persons on ProjectGenerally 5–10Generally 10–20Generally > 20Project DurationUp to six months6–12 months6–24 monthsOnce the categories have been defined, please enter them above. In addition, we recommend that you mark the individual criteria in the table. The category parameters should be modified accordingly to your company/industry parameters.11 Project Budget (Overview)The financial framework within which the project has to operate is described here. Depending on the size of the framework, it may make sense to provide further details for individual parts.AreaAmountProjectSubproject12 Project StartupThe project is deemed started with the following signatures:Representativeof Steering CommitteeCustomerProject ManagerSignatureNameDate13 Project End Planned Project End: 13.1 Signatures for ReleaseThe project manager is released with the signatures provided here following the project closing phase:Representativeof Steering CommitteeCustomerProject ManagerSignatureNameDateAnnexI. Glossary and AbbreviationsIf abbreviations have been used in this document (as well as terms that need to be defined in greater detail) and common understanding for every user is a prerequisite for the success of the project, this is an opportunity to explain them.TermExplanationII. References, Accompanying DocumentsIf references have been made in this document to other external documents, these documents should be listed here.Reference No.TitleDoc. No.File name: Project Charter.docxPage 19 of 19Print date 05.05.16
Answered Same DayFeb 28, 2020

Answer To: Customer logo here Project Name: Project Charter Company logo here Project Name: Project Charter The...

Amar answered on Mar 03 2020
81 Votes
3
    Project Name: New Drug Development - Lifecycle Pharmaceutical
Project Charte
    
    
    
    Project:
    New Drug Development - Lifecycle Pharmaceutical
    
    
    Title:
    Project Charte
    
    
    Document number:
    01
    
    
    Version
    0.1
    
    
    Document status:
    Draft
    
    
    Author:
    XX, XXXX
    
    
    Responsible:
    XX, XXXX
    
    
    Da
te created:
    01.03.18
    
    
    Protection class:
    "For internal use only"
    
    
Document history
    Version
    Date
    Autho
    Comment/Change
    0.1
    01.03.18
    XX, XXXX
    Project Charter Draft
    
    
    
    
    
    
    
    
    Page
1    Background/Project purpose or justification    4
2.1    Statement of Work    4    
2    Goals    5
2.1    Goals    5
2.2    Scheduling goals/milestones    5
3    Project product description    5
4    Delivery units    7
4.1    Delivery units/services    7
5    Project success criteria    8
6    High-level risks    9
7    Key stakeholders    10
8    Assumptions, restrictions and external dependencies    11
9    Responsibility of the customer    12
9.1    Tasks    12
9.2    Resources and staffing    12
10    Project category    13
11    Project budget (overview)    14
12    Project startup    15
13    Project end    16
13.1    Signatures for release    16
Annex    17
A.    Glossary and a
eviations    17
B.    References, accompanying documents    17
1
1. Background/Project Purpose or Justification
Lifecycle Pharmaceutical company is facing significant competition in the market and has been losing market share steadily over the years. In a bid to defend its position and regain market leadership eventually the company is pursuing strategies of various natures. One of them is to refu
ish its long lost product leadership. In this context, the company has embarked on a project to design, develop, test, obtain regulatory approval and produce a marketable drug.
This project has been established and approved to deliver the same and aid the company to regain its market leadership position.
1.1 Statement of Work
The company has embarked on a project to design, develop, test, obtain regulatory approval and produce a marketable drug. The statement of the work for this project can be summarized as follows,
· Design the drug candidates LC-1, LC-2, LC-3 & LC-4
· Develop, Test and Finalize of drug candidates LC-1, LC-2, LC-3 & LC-4
· Obtain regulatory approvals for the drug candidates that has cleared the testing
· Document the drugs developed and regulatory approved ones
· Design and develop suitable production process for the final drug candidates
2 Goals
2.1 Goals
    Goal
    Description
    Design Drug
    Design the drug candidates LC-1, LC-2, LC-3 & LC-4
    Develop Drug
    Development, Testing and Finalization of drug candidates LC-1, LC-2, LC-3 & LC-4
    Obtain Regulatory Approval
    Obtain regulatory approvals for the drug candidates that has cleared the testing
    Product Documentation
    Documentation of drugs developed and regulatory approved ones
    Process Development for Production
    Design and develop suitable production process for the final drug candidates
2.2 Scheduling Goals/Milestones
    Schedule
    Description
    Project Planning
    Completion of project planning and finalization of approved project management plan document
    Design Drug
    Design the drug candidates LC-1, LC-2, LC-3 & LC-4
    Develop Drug
    Development, Testing and Finalization of drug candidates LC-1, LC-2, LC-3 & LC-4
    Obtain Regulatory Approval
    Obtain regulatory approvals for the drug candidates that has cleared the...
SOLUTION.PDF

Answer To This Question Is Available To Download

Related Questions & Answers

More Questions »

Submit New Assignment

Copy and Paste Your Assignment Here