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• Continuing growth and
spreading their message across the state
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
Stakeholder Analysis
• Team 8Project Managers SME - Suzanne Cummings
• James Eisenstein Project Sponsor
• Barry Kauffman CC Executive Director
• Ruth Frits Web Developer
• Entry Level & InternsResources
Initial Financial Analysis
Final Financial Analysis
Earned Value Chart
AC
BACEAC
EVPV
0
50000
100000
150000
0 3 6 6.45
Month
$
• 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
MilestonesMilestone Date
Initiating
Completed scope draft 10/27/05
Assemble project teams, define roles completed
10/20/05
Completed initiating stage 10/20/05
Planning
Completed schedule 11/10/05
Completed planning stage 11/11/05
Executing
Completed CMS development 11/25/05
Completed Templates 11/14/06
Completed site design 11/23/05
Completed website construction 11/30/05
Completed security development 1/19/06
Completed executing stage 1/19/06
Deployment
Completed deployment stage 2/2/06
Milestones ContinuedRollout Date
Modify items as necessary 2/13/06
Completed Pilot 2/13/06
Completed stakeholder review 2/14/06
Deploy production system complete 2/20/06
Completed rollout 2/21/06
Completed deployment stage 2/21/06
Controlling
Status reports 16th of every month
Stakeholder status report Every Wednesday
Status reports to client Every other Wednesday
Completed external testing 3/13/06
Completed unit testing 3/13/06
Completed external testing 3/17/06
Completed integration testing 3/17/06
Completed external testing 3/20/06
Completed testing stage 3/21/06
Training materials complete 3/28/06
Completed documentation 3/28/06
Completed controlling stage 3/28/06
Closing
Project concluded 4/4/06
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 RiskHigh 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 RiskMedium 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
Project Risk Management (cont’d.)
• Market RiskMedium 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 RiskHigh Probability / Low Impact / Risk Factor of 2.4
National level of organization take over CC/PA website
Customized website distinguish unique identity
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
Lessons Learned
• Contact stakeholders early in the project and stay in contact
• Define scope more clearly• Have resource availability
defined in writing