Skip to content

Sanitized case study of an enterprise SharePoint & Project Server implementation, focusing on PMO systems, project governance, resource management, and reporting.

License

Notifications You must be signed in to change notification settings

MelikaWorks/sharepoint-project-server-pmo

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

25 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

sharepoint-project-server-pmo

Sanitized case study of an enterprise SharePoint & Project Server (PWA) implementation, focused on PMO systems, project governance, resource and cost management, and reporting.

Enterprise SharePoint Project Server (PWA) – Case Study

This repository presents a sanitized, real-world enterprise case study of SharePoint Project Server (PWA), focused on portfolio management, project governance, reporting, and resource/cost awareness.

The purpose of this repository is to demonstrate system design, administration, and analytical thinking, rather than to provide deployment scripts or raw configuration files.


Scope of the Case Study

This case study covers the following areas:

  • Multi-project and portfolio-level visibility
  • Project Web App (PWA) configuration and usage
  • Project governance with controlled task management
  • Custom views across project, task, resource, and cost dimensions
  • KPI-based progress monitoring and reporting
  • Enterprise-level resource and cost awareness
  • Structured troubleshooting and documentation practices

All content has been anonymized and sanitized.


Tech Stack

  • Microsoft SharePoint Server (On-Premises)
  • SharePoint Project Server / Project Web App (PWA)
  • SQL Server (Project Server backend)
  • Enterprise Reporting & KPI Dashboards
  • Role-Based Access & Governance Design

My Role

In this project, I was responsible for the end-to-end setup, configuration, and operational support of the Project Server environment, with responsibilities including:

  • SharePoint / Project Server administration
  • PMO systems implementation and support
  • Reporting and governance design
  • Resource and cost structure coordination

This was a live production environment used by multiple projects.


Repository Structure

.
├── case-study/
│   ├── overview.md
│   ├── my-role.md
│   └── architecture.md
│
├── architecture-and-design/
│   └── troubleshooting-notes.md
│
├── reports-and-insights/
│   ├── reports-overview.md
│   ├── kpi-and-progress-analysis.md
│   └── lessons-learned.md
│
├── screenshots/
│   ├── 00-optional-portal-home.jpg
│   ├── 01-project-center.jpg
│   ├── 02-reports-library.jpg
│   ├── 03-project-site.jpg
│   ├── 04-custom-list-capacity.jpg
│   ├── 05-multi-project-environment.jpg
│   ├── 06-project-summary-kpi-dashboard.jpg
│   ├── 07-pwa-custom-view-project-progress-tracking.jpg
│   ├── 08-pwa-manage-project-task-resource-views.jpg
│   ├── 09-project-web-app-task-structure-and-governance.jpg
│   ├── 10-pwa-project-build-team-cost-management.jpg
│   └── 11-resource-center-cost-resources.jpg
│
├── lessons-learned.md
├── masking-rules.md
└── README.md

Screenshots

The screenshots folder contains selected and sanitized screenshots illustrating key aspects of the system, including:

  • Project Center and portfolio-level views
  • Project-level dashboards and timelines
  • Custom PWA views and governance controls
  • Resource and cost-related configurations

Screenshots are intentionally limited to highlight system structure and design, rather than expose operational or sensitive data.


Reporting and Analysis

Detailed explanations of the reporting structure and progress analysis are provided in the following documents:

  • reports-and-insights/reports-overview.md
  • reports-and-insights/kpi-and-progress-analysis.md

These documents focus on how insights were derived and applied to support decision-making, rather than on raw data or metrics.


Lessons Learned

Practical insights gained from operating the system in a real enterprise environment are documented in the following files:

  • reports-and-insights/lessons-learned.md
  • lessons-learned.md

These reflections focus on governance, user adoption, and analytical considerations, rather than tool-specific limitations.


Troubleshooting Approach

A high-level overview of the troubleshooting methodology and problem-solving mindset applied throughout the project is available in:

  • architecture-and-design/troubleshooting-notes.md

Detailed, step-by-step fixes and internal references are intentionally excluded from this public repository.


Data Sanitization Notice

All materials in this repository have been sanitized to remove:

  • Organization and company identifiers
  • User names and personal data
  • Server names, URLs, and infrastructure details
  • Real cost figures and sensitive timelines

For additional details, see:

  • masking-rules.md

Purpose of This Repository

This repository is intended as a professional portfolio artifact to demonstrate experience with enterprise project management systems, governance, and analytical thinking.

It is not intended for direct deployment or operational reuse.


Author

👩‍💻 Melika Mehranpour
Senior Software Engineer | Enterprise & Collaboration Platforms

Expertise:
SharePoint • Project Web App (PWA) • Workflow Automation • Reporting & Governance

🔗 LinkedIn | GitHub

License

See the LICENSE file for license information.

About

Sanitized case study of an enterprise SharePoint & Project Server implementation, focusing on PMO systems, project governance, resource management, and reporting.

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published