mermaid
flowchart TB
    subgraph "Product Manager"
        PM1(Define Requirements) --> PM2(Prioritize Features)
    end

    subgraph "Designer"
        D1[Design UI/UX] --> D2[Create Mockups]
    end
    
    subgraph "Developer"
        Dev1[Implement Features] --> Dev2[Test Code]
    end

    subgraph "Quality Assurance"
        QA1[Write Test Cases] --> QA2[Execute Test Cases] --> QA3[Report Bugs]
    end
    
    subgraph "DevOps"
        DO1[Configure Environment] --> DO2[Deploy Application] --> DO3[Monitor & Maintain]
    end

    PM2 --> D1
    D2 --> Dev1
    Dev2 --> QA1
    QA3 -->|If bugs found| Dev1
    QA3 -->|If no bugs| DO1

    style Product\ Manager fill:#f9f,stroke:#333,stroke-width:2px
    style Designer fill:#bbf,stroke:#333,stroke-width:2px
    style Developer fill:#f96,stroke:#333,stroke-width:2px
    style Quality\ Assurance fill:#bfb,stroke:#333,stroke-width:2px
    style DevOps fill:#fd7,stroke:#333,stroke-width:2px

This flowchart represents a simplified process of developing a piece of software, with each role operating in its own swimlane. The flow starts with the Product Manager defining requirements and prioritizing features, which then informs the Designer’s work on UI/UX and mockups. The Developer implements the features and tests the code, with the Quality Assurance team writing and executing test cases, and reporting any bugs they find. If bugs are found, the process loops back to the Developer to fix them. Once QA approves the implementation, the DevOps team configures the environment, deploys the application, and then monitors and maintains it.