1 / 13

Common Cause/PA Website Project

Common Cause/PA Website Project. Common Cause of Pennsylvania. Who are they? Volunteer based nonpartisan nonprofit advocacy organization What do they do? Inform constituents of PA of the issues that affect Pennsylvanians Work to strengthen public participation in the political process Goals

ping
Download Presentation

Common Cause/PA Website Project

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Common Cause/PA Website Project

  2. Common Cause of Pennsylvania • Who are they? • Volunteer based nonpartisan nonprofit advocacy organization • What do they do? • Inform constituents of PA of the issues that affect Pennsylvanians • Work to strengthen public participation in the political process • Goals • Continuing growth and spreading their message across the state

  3. The Problem • CC/PA would like to have control of their own website • Currently run by national chapter of CC • Would like maintain a new website in house which can be controlled by volunteers • New website will support their goals by increasing their visibility

  4. Stakeholder Analysis • Team 8 • Project Managers • SME - Suzanne Cummings • James Eisenstein • Project Sponsor • Barry Kauffman • CC Executive Director • Ruth Frits • Web Developer • Entry Level & Interns • Resources

  5. Initial Financial Analysis

  6. Final Financial Analysis Cost variance = Earned Value – Actual Cost = $62,181.28 - $55,519.00 = $6662.28 Schedule Variance = Earned Value – Planned Value = $62,181.28 - $66,622.80 = -$4441.52 Cost performance Index = Earned Value / Actual Cost = $62,181.28 / $55,519.00 = 1.12 Schedule Performance Index = Earned Value / Planned Value = $62,181.28 / $66,622.80 = 0.933 Estimate at Completion = Budget at Completion / Cost Performance Index = $111,038.00 / 1.12 = 99141.07 • Under Budget • Behind Schedule

  7. Milestones

  8. Milestones Continued

  9. Project Risk Management • Technology Risk Medium Probability / High Impact / Risk Factor of 4 No confirmation to see approval of hardware No relationship between sponsor and Kintera • Financial Risk High Probability / High Impact / Risk Factor of 7.2 Non profit organization / Not certain of volunteer’s experience No budget could make the project unfeasible • People Risk Medium Probability / High Impact / Risk Factor of 3.2 Working on project without getting to know clients Manager and team realize misunderstanding of customer’s expectations

  10. Project Risk Management (cont’d.) • Market Risk Medium Probability / High Impact / Risk Factor of 3.2 Displeased over the control of their presence on the Internet Website draws more users and members to organization • Structure/Process Risk High Probability / Low Impact / Risk Factor of 2.4 National level of organization take over CC/PA website Customized website distinguish unique identity

  11. Project Quality Management Standards: • Website works on all browsers • Accessible to all users: website can be used by the disabled Requirements: • Completed project meets all specifications and satisfies all needs: the website must accomplish the desired goal and meet all expectations • System available 24/7: the website is available at all times, except during updates or reconstruction • System available to all users: anybody can use and view the website • System is easy to find/navigate: website is linked to the main Common Cause website; website is easy to find through web searches and easy to navigate

  12. Lessons Learned • Contact stakeholders early in the project and stay in contact • Define scope more clearly • Have resource availability defined in writing

More Related