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 Under Budget Behind Schedule 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

8. Milestones MilestoneDate Initiating Completed scope draft10/27/05 Assemble project teams, define roles completed 10/20/05 Completed initiating stage10/20/05 Planning Completed schedule11/10/05 Completed planning stage11/11/05 Executing Completed CMS development11/25/05 Completed Templates11/14/06 Completed site design11/23/05 Completed website construction11/30/05 Completed security development1/19/06 Completed executing stage1/19/06 Deployment Completed deployment stage2/2/06

9. Milestones Continued Rollout Date Modify items as necessary2/13/06 Completed Pilot2/13/06 Completed stakeholder review2/14/06 Deploy production system complete2/20/06 Completed rollout2/21/06 Completed deployment stage2/21/06 Controlling Status reports16 th of every month Stakeholder status reportEvery Wednesday Status reports to clientEvery other Wednesday Completed external testing3/13/06 Completed unit testing3/13/06 Completed external testing3/17/06 Completed integration testing3/17/06 Completed external testing3/20/06 Completed testing stage3/21/06 Training materials complete3/28/06 Completed documentation3/28/06 Completed controlling stage3/28/06 Closing Project concluded4/4/06

10. 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

11. 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

12. 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

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