Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Get aware and assess relevance

    1. Get in contact with GovStack and get aware of compliance opportunity (Event, Website, Impact Exchange)

    2. Inform about Compliance Process (Confluence)

    3. Select matching BB(s) to own Software Product (Gitbook)

  2. Conduct and publish Self-Assessment Compliance Concept

    1. Deployment Compliance: Link to container and documentation (Manual, Confluence Compliance Evaluation: Template )

    2. Interface Compliance: Provide report of the executed test harness (Automated, Test Harness Steps to check compliance against a GovStack API spec )

    3. Requirement Specification Compliance: Conduct FitGap Analysis (Manual, Template on Confluence Compliance Evaluation: Template )

    4. Wait for verification of documents regarding completeness and plausibility by GovStack Team (Track via Jira Ticket)

  3. Offer Software (and optionally adapt software)

    1. Once software achieves at least one compliance category level 1, the software gets listed on GovMarket with a badge visualizing the degree of compliance and a link to confluence Self-Assessment (Website, Impact Exchange)

    2. Once software achieves deployment compliance category level 2, the software is a candidate to be integrated into the GovTest Sandbox (Sandbox)

  4. Take Opportunities

    1. Get contacted by governments or other clients via GovMarket contact details

    2. Monitor GovMarket RFP Radar, apply and demonstrate compliance in a transparent manner via linking to GovMarket

    3. Create a “Vendor Storefront” to increase visibility and state offered services/products more clearly

Action Items

  •  Create Confluence Template for Self-Assessment Nico Lueck
  •  Release Test Harness
  •  Adapt Impact Exchange Platform