Skip to main content

Planning for Lifecycle

Having a detailed, actionable, and time-bound implementation plan is one of the most important indicators for which customers are successful in taking control of their software supply chain. This page outlines the key elements for a successful Sonatype Lifecycle implementation plan.


  • Understand the installation process.

  • Define your Primary Desired Outcome (PDO)

  • Create a success plan and timeline for adoption.

  • Identify key stakeholders and project leaders.

Action Items

  1. Review installation materials

  2. Review Deployment Best Practices

    • Project Initiation (1st month)

    • Project Pilot (first 2 months)

    • Project Commencement (1st year)

  3. Create your Success Plan - The success plan is a document drafted by the team to identify the individuals responsible for your Sonatype Lifecycle deployment and identify how you'll all work together. Your success plan should be written down and available to all relevant stakeholders.

    • Define your Primary Desired Outcome- Your Primary Desired Outcome (PDO) is the reason you are using Sonatype Lifecycle. A good PDO is a specific, measurable, and time bound goal. It should also be focused on an outcome not a task.

    • Identify Key Stakeholders

      • Administrators - Individuals with Administrative access to Lifecycle and are responsible for its configuration and operation.

      • Champion - This person is an advocate for Lifecycle's adoption and works to develop strategies and success plans.

      • Developer Advocates - These people represent the other developers at your organization. They'll help define a workflow that's compatible with your existing development processes.

      • Executive Sponsors - The executive sponsor is the organizational leader advocating for the use of Sonatype Lifecycle. It is vital that the Executive Sponsors are able to make changes in your organization

      • Legal Representative - The legal representative is the expert on the legal risk for your application. They will help establish workflows and risk tolerance from open source licenses

      • Application Security Representative - The Application Security expert will help establish workflows for the development and application security teams. They will also be your experts on acceptable open source security risk.

    • Establish Communication Cadence - Define how your implementation team will communicate. Identify the channels you'll use to communicate and how often you'll meet.

    • Set time bound goals for the next phase of your deployment - Plan your deployment one phase at a time. Set goals for the next phase as you complete the current phase. This will be easier than planning a months long project in its entirety and allow you to be more adaptable.