Business objective
Americans take an estimated two driving trips daily, and each endpoint needs a place to park. In a local survey, four out of five participants reported recent parking difficulties: locating parking in unfamiliar areas, competing in crowded locations, or not knowing the status of a given parking location.
Damn Parking addresses these problems with a platform that uses cameras to convert live video streams into real-time metadata on parking availability. Users can also share their current parking location and departure time in exchange for access to available parking for a future time.
Scope boundaries
The end result is a working prototype of the Damn Parking application. The website will let users view available parking spaces, check availability in selected locations, and update information when they are leaving a space. The prototype will also demonstrate how camera data could determine whether spaces are available or occupied.
In scope: website design, main parking features, a basic parking map, and prototype testing.
Out of scope: installing cameras city-wide, creating a complete city-wide parking network, processing payments, or releasing the application commercially. Those features may appear in future versions.
Constraints
- Limited real-world infrastructure: no city-wide camera or sensor network; camera detection is demonstrated at limited scale.
- Budget: free or low-cost development, hosting, mapping, and data-processing tools.
- Limited real-time data: the prototype cannot guarantee complete real-time coverage for all locations.
- Privacy: camera functionality focuses on space occupancy, not unnecessary identifying information about drivers, pedestrians, or vehicles.
Assumptions
- Users have an internet-connected device that can reach the Damn Parking platform.
- Users want parking availability before or while traveling to a destination.
- Users may contribute parking information, such as when they are leaving a space.
- Camera footage or sample video can be made available to demonstrate occupancy detection.
- The prototype operates on a limited set of locations, not city-wide coverage.
- Mapping technologies can display parking locations geographically.
- The team has the software and hosting resources needed to build and demonstrate the prototype.
Stakeholder register
| Stakeholder | Role / Interest | Influence | Primary needs |
|---|---|---|---|
| Drivers / parking users | Primary users | High | Clear availability, locations, and navigation |
| Students / campus drivers | Initial researched segment | Medium | Less search time; find convenient spaces |
| Lot / garage operators | Manage represented facilities | High | Accurate facility representation; responsible data use |
| Camera / data providers | Occupancy data source | High | Secure access and processing methods |
| Project team | Design, build, test, manage | High | Clear requirements and semester completion |
| Course instructor / sponsor | Evaluates PM and deliverables | High | Complete, well-documented sprint artifacts |
| University / property owners | Infrastructure owners | Medium | Appropriate infrastructure and camera-data handling |
Success criteria (target)
- Core functionality: demonstrate parking availability, selected locations, user parking updates, and camera-based occupancy detection.
- Budget: spending at or under budget with basic cost tracking.
- Prototype quality: stable, understandable, and clear user experience.
- Schedule: all planned deliverables completed by their deadlines.
The Project Manager coordinates activities, assigns tasks, monitors progress, and escalates blockers. Significant scope, budget, or objective changes require team (and when applicable, sponsor) approval.
Document Project Charter