Project Management presentation- case presentaition . make powerpoints

User Generated

anaplJ

Business Finance

Description

ATTACHED ARE :

1-THE CASE

2-PRESENTATION OUTLINE

3-PRESENTATION CLARIFICATION

THE POWER POINT NO MORE THAN 60 SLIDES. integrate at least two (2) outside references (besides the case study contents and the text), At the last 10 slides I need questions & answers part) please.

Unformatted Attachment Preview

A High Level Outline Option for Presentations Below is a potential high-level outline approach for presentations. This is only one; it is not the only one, it may not be fully complete. It is just something to give each group some additional “food for thought”. 1. Welcome and Introduction: a. Business Background and History. b. Case Background and History. c. Key Stakeholders (an opportunity to leverage a tool example – Stakeholder Assessment). d. Related Relevant Information to the Business or Case – i. Assessment of the Business Market/Environment. • Identify any unique factors to the market/environment that are relevant to the business or case. ii. Assessment of the Business Competition. • An opportunity to leverage a tool example – Assess position of your business against others in the market/environment via a SWOT Analysis. iii. Financial Analysis. iv. Other Relevant Items. e. Within this section is an opportunity to integrate a multi-media component into your presentation about the business or case. 2. Assessment of the following related to your business or case: a. What happened? b. What role did Key Stakeholders have in what happened? c. What other factors influenced the situation? d. What resulted? e. What Went Well? f. What Went Wrong? 3. Application of Project Management Knowledge Areas to the Business or Case (to Yield Improvement): a. For each relevant Project Management Knowledge Area (do completely for each Project Management Knowledge Area, one Project Management Knowledge Area at a time) – i. Name what the Project Management Knowledge Area is. ii. Explain why the Project Management Knowledge Area is relevant to your business or case. iii. Explain how you would apply the Project Management Knowledge Area to your business or case to yield improvement (another opportunity to leverage tool examples relevant to each/every Project Management Knowledge Area you are covering – multiple opportunities to leverage multiple tools). iv. Explain what impact you believe application of the Project Management Knowledge Area will have on the case. v. Explain how you would measure and validate for the desired impact or impacts on your business or case. 4. 5. 6. 7. 8. b. This could be another opportunity to integrate a multi-media component into your presentation relevant to a Project Management Knowledge Area being covered. Current State: a. Add any relevant current information on the business or case. b. This could be another opportunity to integrate a multi-media component into your presentation. Conclusion. End. Works Cited/References. Appendix: a. Include additional complete or full tool examples relevant to the case that you may have referenced in your main presentation only but did not include the full example in the body of it. b. Include other relevant information that you may have referenced in your main presentation only but did not include in the body of it. Tool Examples to Consider Within and/or Supplemental to Presentations 1. Stakeholder Analysis. 2. SWOT Analysis. 3. Developing examples of Strategy, Vision, Mission, and Goal statements. 4. Scope Statement (what a proper one would be; write your own). 5. Flow Chart of both the Business and IT processes in a visual format. 6. Risk Assessment (also known as a RAID Log). 7. Risk Mitigation Plan to address risks. 8. Probability-Impact Matrix. 9. High-level Work Breakdown Structure (WBS). 10. Milestone-level plan and/or a Gantt Chart. 11. RACI Chart. 12. Project Budget and/or tools to report on budget performance (plan versus actual performance, may be integrated within a Status Report). 13. Communications Plan (to improve upon communications and transparency issues). 14. High-level Test Plan and/or Testing Approach. 15. Procurement Plan (to better manage contracting-related issues). 16. Status Report (to track progress, financials, risks, issues, etc.). 17. Training Plan – How you would leverage training to aid in adoption. 18. Change Management Log – With actual changes made included. Questions to Ask As You Consider Presentation Topics 1. Does your topic fit the assignment well? 2. Is your topic adaptable to the needs of the assignment from a Project Management perspective? 3. Will your topic allow you to – a. Develop a high-quality overall presentation? b. Effectively analyze the topic in terms of the Project Management Knowledge Areas? c. Apply the Project Management Knowledge Areas and offer improvement opportunities? d. Apply the Project Management related questions I note in class and in my Canvas announcements (also see Item 3 in the High Level Outline Option for Presentations section above)? i. What Project Management Knowledge Areas, Tools, Techniques, and/or Processes would you employ? ii. Why? iii. How? iv. How would you expect what you employ to improve the situation (e.g., what are the expected benefits from employing the Project Management Knowledge Areas, Tools, Techniques, and/or Processes used)? v. How would you measure the impact to validate for the desired effect (e.g., how will you prove the intended benefit was realized)? e. Create strong tool examples with real case data included to support the above items? 4. When you do additional internet research on the topic is there more/additional information available online, through other resources, or on websites/company/corporate sites that you can leverage for your presentation? 5. Make sure it is a topic that will allow you to develop the best presentation possible. PRESENTATION-RELATED CLARIFICATIONS If you have additional questions, please reach out to me. Please consider the following: ▪ I do not expect to see any incorrect spelling on slides. ▪ Slides should use proper punctuation and consistent tense format. Word use/choice on slides should be crisp and flow well from point to point. ▪ Bullet points and sub-points should be properly (and in a consistent format) indented and vary bullet types among your main and sub-points. ▪ Spell checkers can only tell you if a word is misspelled. They will not tell you if the correct word, tense form, or punctuation has been used. \ Additional Expectations Application of the material: ▪ Consider: o What went wrong or could have been done better? o What went well (it not always just about what went wrong)? o What led to or caused a particular (good or bad) outcome? o Which Project Management Knowledge Area(s) are most important to your case or topic? ➢ What Project Management Knowledge Area practices might you apply to your case or topic to yield an improved outcome? ➢ How would you apply them? ➢ What impacts would you expect to result? o What PM Tools are most important to your case or topic? ➢ What specific PM Tools might you apply to your case or topic to yield an improved outcome? ➢ How would you apply them? ➢ What impacts would you expect to result? Page 1 of 1 3/15/13 Scanned by CamScanner Scanned by CamScanner Scanned by CamScanner Scanned by CamScanner Scanned by CamScanner Scanned by CamScanner Scanned by CamScanner Scanned by CamScanner Scanned by CamScanner Scanned by CamScanner Scanned by CamScanner Scanned by CamScanner Scanned by CamScanner Scanned by CamScanner Scanned by CamScanner Scanned by CamScanner Scanned by CamScanner Scanned by CamScanner Scanned by CamScanner Scanned by CamScanner
Purchase answer to see full attachment
User generated content is uploaded by users for the purposes of learning and should be used following Studypool's honor code & terms of service.

Explanation & Answer

hi, I want to re-submit the Powerpoint file with some edition & correction, so this is my final answer

Providian Trust
Case Study

Welcome and Introduction
a) Business Background and History:
Providian Trust was a noteworthy trust organization that gave
money related and guardian administrations. Its primary
wellspring of income originated from which incorporate
private and business home loans, and customer and corporate
credits. Michael LeBlanc, the Senior Vice President of Trust,
Investment, and Treasury, drove the venture gone for rebuilding Providian Trust's business forms by actualizing a
noteworthy programming framework called Access Plus an
advantage administration framework created by Select One.
LeBlanc emphatically trusted that the execution of access in
addition to would give the administration the ability to control
customer's records and enhance the operations in both the
back and front workplaces.

Welcome and Introduction (cont.)
a) Business Background and History: (cont.)
The venture was to keep going for 20 months and cost $18 million. A
few boards of trustees were set up to execute and design the venture.
LeBlanc had a sharp information of the put stock in showcase yet did
not have any IT anticipate administration encounter, so he asked Todd
Benari - the Vice President of Trust operations to head the venture
group. Despite the fact that Providian Trust had two IT offices with a
group of 270 IT workforce, just the 10 of the 30 faculties in the Trust
Operations office were incorporated into the venture group. While the
venture was full of good aims and arranging like the correction of the
business procedures to utilize innovation as an empowering
component, centralization, and union of the organization of confiding
in data, different regions did not go so well.

Welcome and Introduction (cont.)
b) Case Background and History:
Based on the facts exhibited for the situation, it
might be accepted that while LeBlanc needed to
change the trust division's data framework into a
progressively a productive one a definitive
aftereffect of this project would have been a reengineering of the division's business forms. While
the old framework empowered administrators to be
really required in customer accounts the proposed
new framework operations people would be
expecting the obligations of the trusts officers.

Welcome and Introduction (cont.)
b) Case Background and History: (cont.)
As indicated by a few examinations, by and large roughly
70% of re-engineering ventures fall flat. This high failure
rate is regularly because of lack of common sense and the
absence of arrangement for negative representative
responses. It is along these lines likely that Providian Trust
will likewise fall inside that 70% section in view of the lack
of foresight and usage of the project, the absence of
legitimate initiative and the negative reactions shown by
the workers.

Welcome and Introduction (cont.)
c) Key Stakeholders:
Key stakeholders in Providian trust case include
those having effect or being influenced by the
association's activities, targets and strategies. A
few cases of key partners are leasers, chiefs,
representatives, government (and its
organizations), proprietors (investors), providers,
unions, and the group from which the business
draws its assets.

Welcome and Introduction (cont.)
d) Related Relevant Information to the Business or
Case:
• i. Unique factors: Since its beginnings, as a matter
of fact, Providian Trust constantly settled itself as
a client situated organization. In light of
estimations of trust, respectability, and
genuineness, Providian Trust kept up an
overwhelming spotlight on its clients and trusted
that to be fruitful, it was basic that Providian
conveys high consumer loyalty reliably and
consistently.

Welcome and Introduction (cont.)
ii. Opportunity to leverage: Opportunity to leverage includes
the fact that the firm chooses to create Access Plus, another
trust and authority administration programming, however is
confronting firm resistance from a few individuals, most
particularly from Internal Auditor, Peter Story which were for
the most part disregarded by the CEO and the Board. Between
time CEO Stephen Walsh is defied with an obsolete data
system for Providian's trust division making undue preferred
standpoint all the more mechanically propelled contenders.
Veteran Trust Officers invest a great deal of energy revising
articulations, costing the organization around $2 million to $5
million on rebates and postponed charges in view of
inconsistencies in money related proclamations.

Welcome and Introduction (cont.)
• iii. Financial Analysis: Providian Trust headquartered in
New York conveyed economical and guardian benefits
through a system of 216 branches. In 1994, this
organization managed $49. 4 billion input stock in the
resource with a staff of 840 full-time workers. 60% of
organization's charge wage and 9% of gross income
produced by its guardian business that year. In spite of
the fact that they had an immense group taking a shot
at the front and back office dealing with and record
keeping and settling exercises, there was dependably a
possibility for error and it was simple for everybody
point finger at others when it happens.

Welcome and Introduction (cont.)
iv. Other Relevant Items: Project Justification
Analysis LeBlanc justified that by having this
transformation extend effectively actualized
with a financial plan of $18 million, they can win
more trust from the clients and have the
product information dealing with and because
of this re-engineering procedure, they can get
$9.2 million benefits, while lessening the work
drive from 840 to 660.

Welcome and Introduction (cont.)
e) An opportunity to integrate a multi-media component into Providian
Trust takes place after Stephen Walsh had stepped into the position of
Providia...


Anonymous
This is great! Exactly what I wanted.

Studypool
4.7
Indeed
4.5
Sitejabber
4.4

Similar Content

Related Tags