Project Management for BioPharma, LIMS, and Shop Floor

As a requirements engineer, project manager, and developer , I consider business requirements, regulatory constraints, and technical feasibility together.

My approach combines agile flexibility with governance requirements from GxP, CSV, and FDA-related environments.

Specialization: LIMS projects, BioPharma systems, shop floor data acquisition, and healthcare IT — in other words, initiatives where compliance and agility need to work together cleanly.

PRINCE2 Agile

PRINCE2 stands for a structured project management approach with clear roles, processes, and documents.

Agile emphasizes flexibility, iterative development, and continuous feedback.

PRINCE2 Agile combines both: the governance structure of PRINCE2 with the flexibility of agile methods such as sprints, user stories, and retrospectives.

Why This Matters in Regulated Environments

Regulated environments need governance, documentation, and clean stakeholder alignment.

  • CSV, GxP, traceability, change control, and quality gates
  • URS, FS, validation plans, test scripts, and SOPs
  • Alignment between QA, IT, business teams, management, and regulatory functions

At the same time, complex IT projects need flexibility, early feedback, and incremental delivery.

PRINCE2 Agile is the bridge here: governance without rigidity, agility without chaos.

LIMS Projects

Governance requirements:

  • CSV with URS, FS, IQ/OQ/PQ, and traceability matrix
  • GxP compliance, 21 CFR Part 11, EU GMP Annex 11, and data integrity
  • Change control with impact assessment, QA approval, and re-validation
  • Vendor management for providers such as LabWare, PerkinElmer, or Thermo

Agile adaptations:

  • Iterative validation with incremental test scripts
  • Living documentation instead of frozen requirements
  • Early demos for lab scientists and rapid feedback

BioPharma Systems

Governance requirements:

  • Process science compliance for upstream, downstream, and fermentation contexts
  • Batch record integrity, audit trails, and QA sign-offs for each phase
  • Inspection readiness for FDA and EMA

Agile adaptations:

  • Risk-based validation for critical features first
  • Continuous integration for faster feedback loops
  • Cross-functional teams from process science, IT, and QA

Shop Floor / IPC

Governance requirements:

  • OT/IT convergence between PLCs, SCADA, cloud, and databases
  • Cybersecurity, access control, and industrial networks
  • ALCOA+-compliant real-time data and multi-vendor coordination

Agile adaptations:

  • MVP for critical data flows first
  • Pilot lines before wider rollout
  • Reproducible deployments and DevOps-oriented operating models

QIAGEN: Shop Floor Data Acquisition

Context: Transition from manual workstations to a fully automated production line with IPC data acquisition via Azure IoT Hub and Event Hub.

Project management responsibilities:

  • Stakeholder management across hardware engineering, data science, QA, production, and IT
  • Vendor coordination with Mettler-Toledo, B&P, and Microsoft
  • Interface definition, risk management, and change control

PRINCE2 Agile in practice: stage gates from pilot line to full production, two-week sprints for interfaces, and formal quality gates before each stage.

LabWare LIMS: v6-v7 Migration and Integration

Context: LIMS migration combined with the integration of new instruments in a regulated BioPharma environment.

Project management responsibilities:

  • Requirements workshops with lab scientists, QC/QA, IT, and process science
  • Migration strategy, validation planning, and resource planning
  • Go-live coordination including cutover, rollback, and hypercare

PRINCE2 Agile in practice: iterative validation, UAT in sprint reviews, and formal traceability for every user requirement.

MCC.NET: Healthcare IT Integrations

Context: Integration of PACS, archiving, and multiple dictation systems into an HIS in a critical production environment.

Project management responsibilities:

  • Multi-vendor coordination with PACS, archiving, and speech system providers
  • Clinical workflow analysis for physicians, nursing, laboratory, and radiology
  • Downtime minimization, training, and change management

Methods: Scrum with two-week sprints, sprint reviews with clinical users, and continuous delivery.

PAuLa LIMS: Peptide Automation Lane

Context: From Excel and paper to a connected LIMS — without an existing base system, built completely from scratch.

Project management responsibilities:

  • Workflow audits and modeling of existing production processes
  • Stakeholder alignment across production, QC, QA, management, IT, and ERP context
  • Scope creep management and bidirectional ERP integration

Approach: MVP-oriented introduction, continuous further development, and robust design for low-maintenance operation.

Typical Responsibilities

Project Planning and Control
  • Project charter, business case, WBS, and realistic milestones
  • Resource planning, budget management, and timeline control
Stakeholder Management
  • Stakeholder analysis and communication plans
  • Requirements workshops, change management, and training
Vendor Management
  • Vendor selection, SLA definition, and interface coordination
  • Audit rights and alignment across multiple providers

Risk, Validation, and Go-Live

Risk Management
  • Risk identification, assessment, mitigation, and issue management
Testing and Validation
  • Test strategy from unit test through IQ/OQ/PQ
  • Defect management and validation documentation
Change Control and Hypercare
  • Formal change requests, impact assessments, and approval workflows
  • Go-live planning, rollback, hypercare, and lessons learned

Agile & Governance

What Agile Brings

  • Early feedback and faster correction of requirements
  • Risk reduction through incremental delivery instead of big bang
  • Flexibility with changing requirements
  • Better team dynamics through cross-functional collaboration
  • Faster time-to-market through MVP and staged expansion

What Governance Brings

  • Traceability from requirement through test case to approval
  • Formal quality gates before productive steps
  • Compliance and audit readiness
  • Clear roles, responsibilities, and decisions
  • Structured risk management with traceable processes

How the Bridge Works in Practice

  • Stage gates plus sprints: clear phases, but agile iteration within each phase
  • Living documentation: versioned, traceable, and still adaptable
  • Risk-based validation for critical features
  • Iterative validation instead of documentation backlog at the end of the project
  • Continuous integration with governance-compliant traceability

My approach: agile sprints, early stakeholder feedback, incremental delivery, and at the same time formal quality gates, traceability, and clean documentation.