Share
Explore BrainMass

Project Life Cycle

Please review the attached information regarding the Adaptation of XML Technologies in Adobe Systems for any additional information necessary to assist with the following questions:

1. Provide a communications plan, addressing how progress will be reported to the various project sponsors and executives.
2. A forecast of the time required to complete the project.
3. The project closure process that will be employed.
4. A brief explanation of the project audit process and how it will be applied to this project.
5. Budget estimates for the project.
6. Forecasted project outcomes, using quantifiable measures of success for the project and verifying project alignment with the organization's goals.

Thank you very much for your assistance with this.

---
(See attached file for full problem description)

Attachments

Solution Preview

1. Provide a communications plan, addressing how progress will be reported to the various project sponsors and executives.
There will be an a priori agreement on when the Adobe XML Project executives will submit these reports.
§ Project Initiation Checklist for Small Adobe XML Projects related to the main Adobe XML Adobe XML Project. Scooping and sign-off document. It covers the many topics governing a Adobe XML Project's charter. Assures your homework is done before asking for money. A Adobe XML Project risk assessment spreadsheet.
§ Project managers of the Adobe XML Adobe XML Project should use a default Microsoft Adobe XML Project template with many useful settings.
§ Issue Log. Probably the most revised document on most Adobe XML Projects by Adobe XML Adobe XML Project.
§ Project Initiation Kick Off Report. Announcing how you're going to kick off the Adobe XML Project. In memo form.
§ Project Initiation Report. This summarizes the results of the Adobe XML Project Initiation stage of the Adobe XML Project and recommends proceeding to the next stage. It defines what work is to be done, what is to be delivered, how long it will take, by whom, how much it will cost and why it is worth doing.
§ Stage End Approval Report. Adobe XML Project Phases are sometimes called "stages" .Costing spreadsheet by Adobe XML Project stage/phase.
Project Control Reports
· Change Request Form. Word template.
· Change Request Log. A register for Change Request Forms. Word template to be filled by the Adobe XML Project executive requesting the change.
· A flash status report: Communicate weekly with this 1 pager. Word template.
· Project Status Report. Another version of the Flash Status Report. Word template.
· Issue Log template.
· Project Board Agendas: "Prototype Adobe XML Project Board Progress Review Meeting," "Project Board Progress Review Meeting". This supports one of the governance ideas in the Adobe XML Project management process.
· Quality Review Agenda. Meeting to confirm that the product is complete.
· Quality Review Exception Item List. What needs to be fixed?
· Exception Situation Report. This document summarizes how and why the Adobe XML Project is in an Exception Situation, the impact of doing nothing, recommended recovery actions, changes to the plan and the impact of this new plan upon the Adobe XML Project. The proposed Exception Plan replaces the current Stage Plan.
· These reports are typically sent on the completion of the project and will be sent to the executives supervising the project.

Project Summary
x Adobe XML Project description, Scope, schedule, budget, and
quality objectives
à?
Project Performance
x Compare proposal to post implementation audit
x Comment on deviations
à?
Administrative Performance
à?
Organisational Structure
x How did structure impede and/or speed

2. A forecast of the time required completing the project.

The forecast of the time and the budget required for the Adobe XML Project should be done using the PERT/CPM technique. Using this technique will give the Adobe XML Project the most accurate forecast and the most economical budget.
Program evaluation and review technique (PERT) charts depict task, duration, and dependency information. Each chart starts with an initiation node from which the first task, or tasks, originates. If multiple tasks begin at the same time, they are all started from the node or branch, or fork out from the starting point. Each task is represented by a line which states its name or other identifier, its duration, the number of people assigned to it, and in some cases ...

$2.19