---
title: Project Lifecycle & Responsibilities | Shopware Community Hub
description: >-
  Understand the key roles and project stages involved in Shopware deployments
  on PaaS platforms, from provisioning to ongoing operations.
canonical_url: 'https://hub.shopware.com/learn/unit/paas-responsibilities'
---

# Project Lifecycle & Responsibilities

<LearningObjectives>

- Identify the key stakeholders and their responsibilities in PaaS-based Shopware projects.
- Understand the stages of a Shopware PaaS project lifecycle.
- Recognize the handover points and collaborative areas in the project process.

</LearningObjectives>

# Project Lifecycle & Responsibilities

A successful Shopware deployment on a PaaS platform requires a clear understanding of roles and responsibilities throughout the project lifecycle.

In this learning unit, you'll learn the **human side of PaaS deployments:** who does what and when, as well as how stakeholders collaborate from concept to production. Clear responsibilities and collaboration help avoid common pitfalls and ensure smooth project execution.

## Key Stakeholders and Their Responsibilities

PaaS projects typically involve four stakeholder groups:

### 1. Agency Partners

Agencies are typically responsible for:

- **Implementation**: Building and customizing the Shopware application.
- **Code quality**: Ensuring best practices.
- **Integration**: Connecting external systems and services.
- **Testing**: Validating functionality across environments.
- **CI/CD setup**: Configuring automated pipelines.
- **Knowledge transfer**: Educating the merchant team.

<Callout title="Key Point" type="info">

Agency developers must understand PaaS patterns and constraints to build cloud-ready solutions.

</Callout>

### 2. Merchants

Merchants are responsible for:

- **Requirements:** Defining business needs and constraints.
- **Content**: Managing products, categories, and content.
- **Acceptance testing**: Verifying business needs.
- **Go-live approval**: Deciding launch readiness.
- **Operations**: Running daily business on the platform.

### 3. Shopware

The Shopware team's responsible for:

- **Core software**: Maintain the Shopware core.
- **Documentation**: Providing deployment guidelines.
- **Updates and patches**: Releasing new versions and security fixes.
- **Community support**: Offering resources.
- **PaaS compatibility**: Ensuring Shopware runs on supported platforms.

### 4. PaaS Provider

The platform provider (e.g., Shopware, Platform.sh, Symfony Cloud, etc.) is responsible for:

- **Infrastructure**: Maintaining hardware and network.
- **Platform services**: Providing databases, caching, and search services.
- **Scaling**: Allocating resources on demand.
- **Security**: Keeping the platform secure.
- **Monitoring**: Tracking health and performance.
- **Support**: Handling platform-specific issues.

## Stages of a PaaS Project Lifecycle

A typical Shopware PaaS project follows six stages:

### 1. Provisioning

The foundation phase where the project infrastructure is established:

- **Account Setup**: Create PaaS accounts and access credentials.
- **Repository Creation**: Initialize Git repositories.
- **Environment Provisioning**: Set up a development, staging, and production environment.
- **Access Configuration**: Define roles and permissions.
- **Infrastructure Foundation**: Allocate base platform services and resources.

<Callout title="Best Practice" type="info">

Document all provisioning details (credentials, services, access) in a secure shared location.

</Callout>

### 2. Setup

The setup phase, where the platform is prepared for development:

- **Shopware Installation**: Deploy the Shopware core.
- **Environment Configuration**: Configure environments for development, staging, and production.
- **CI/CD Pipeline**: Establish automated deployment workflows.
- **Security Implementation**: Apply access controls.
- **Environment Variables**: Set secrets and configure environment-specific settings.
- **Backup Procedures**: Define backup and recovery.

<Callout title="Official Setup Guide" type="info">

Follow the [official step-by-step guide](https://developer.shopware.com/docs/products/paas/shopware-paas/#getting-started-with-shopware-paas-how-to-deploy-your-first-project) for detailed instructions.

</Callout>

### 3. Development

The core implementation phase where the application takes shape:

- **Shopware Customization**: Tailor Shopware functionality.
- **Custom Development**: Build plugins and modules.
- **System Integration**: Connect external systems and third-party services.
- **Automated Testing**: Implement Unit-, Integration- and End-To-End tests.
- **Design Implementation**: Apply user interface and user experience designs.
- **Deployment Workflows**: Refine and optimize automated deployment processes.

### 4. Quality Assurance

The validation phase ensuring everything works as expected:

- **Functional Testing**: Validate all features and user workflows.
- **Security Assessment**: Identify and fix security vulnerabilities.
- **Performance Testing**: Evaluate application performance under various load conditions.
- **Integration Validation**: Verify all external system connections.
- **User Acceptance Testing**: Stakeholders validate that the solution meets business requirements.
- **Issue Resolution**: Fix bugs and issues founded during testing.

### 5. Go-Live

The launch phase where the application goes live to users:

- **Data Migration**: Transfer data from legacy systems (if applicable).
- **DNS Configuration**: Point domain names to the production environment.
- **SSL Certificate Setup**: Configure HTTPS.
- **Security Hardening**: Implement production-specific security measures.
- **Performance Optimization**: Optimize production environment.
- **Monitoring Setup**: Enable alerts and tracking.
- **Launch Verification**: Final checklist.

### 6. Operations

The ongoing maintenance phase ensuring long-term success:

- **Performance Monitoring**: Track performance and uptime.
- **Update Management**: Apply Shopware and platform updates.
- **Backup Management**: Manage recovery processes.
- **Scaling Operations**: Adjust resources as needed.
- **Security Maintenance**: Apply patches regularly.
- **Performance Optimization**: Tune performance.
- **Routine Maintenance**: Perform routine tasks.

<Callout title="Enhanced Performance" type="info">

Optional services like [Elasticsearch](https://fixed.docs.upsun.com/add-services/elasticsearch.html), [RabbitMQ](https://fixed.docs.upsun.com/add-services/rabbitmq.html), and [Fastly CDN](https://fixed.docs.upsun.com/domains/cdn/fastly.html) can boost performance.

</Callout>

## Handover and Documentation

Ensure smooth transitions with:

1. **Platform Configuration Document**
   - Environment details
   - Service configuration
   - Access credentials (stored securely)
   - Deployment procedures

2. **Operational Runbook**
   - Monitoring setup
   - Backup and restore procedures
   - Scaling guidelines
   - Incident response process
   - Regular maintenance tasks

3. **Knowledge Transfer Sessions**
   - Scheduled training for the merchant team
   - Documentation of custom features
   - Video recordings of key processes
   - Contact information for support

<Callout title="Monitoring and Performance" type="info">

Every Shopware PaaS project include [Blackfire integration](https://fixed.docs.upsun.com/increase-observability/integrate-observability/blackfire.html) for performance monitoring. Train merchant teams on its use.

</Callout>

<Callout title="Best Practice" type="info">

Schedule handover meetings at each milestone. Document decisions and responsibilities.

</Callout>

## Common Challenges and How to Address Them

### Role Ambiguity

**Problem**: Unclear responsibilities.
**Solution**: Use the RACI matrix and align at project kickoff.

### Knowledge Gaps

**Problem**: Missing PaaS or Shopware expertise.
**Solution**: Provide training (e.g., through this learning path), pair novices with experienced team members, budget time to learn.

### Communication Silos

**Problem**: Lack of information flow between merchant, agency, and platform teams.
**Solution**: Regular syncs and shared communication channels.

### Unrealistic Expectations

**Problem**: Overestimating PaaS automation.
**Solution**: Educate early on what PaaS does and doesn't handle.

## Key Takeaways

- **Shared Responsibility**: PaaS projects are a shared responsibility across stakeholders.
- **Clear Handovers**: Clear handover documentation prevents gaps.
- **Lifecycle Understanding**: Understanding the lifecycle helps teams plan efficiently.
- **Proactive Communication**: Ongoing communication avoids pitfalls.

## Next Steps

In the next learning unit, we'll explore the **core technical concepts** of PaaS-Git-based workflows, environment orchestration, and infrastructure as code.