Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 12 Next »

a. Get aware and assess relevance

  1. Learn about GovStack and get aware of compliance opportunity (Event, Website, Impact Exchange)

  2. Inform about Compliance Process (GovStack.global)

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

b. Conduct and publish Self-Assessment

See Compliance Concept

  1. Deployment Compliance: Fill in form with link to container and documentation (testing.GovStack.global)

  2. Interface Compliance: Provide report of the executed test harness (testing.GovStack.global Steps to check compliance against a GovStack API spec )

  3. Requirement Specification Compliance: Fill in form with conducted FitGap Analysis (testing.GovStack.global)

Submitting one of the above creates a Jira Ticket, notification that ticket is being created.

  1. Wait for verification of submission regarding completeness and plausibility by GovStack Team (Track via Jira Ticket) Who? TC? PC?

c. Offer your Software

  1. Once software achieves at least one compliance category level 1, the software gets listed with e.g. a badge visualizing the degree of compliance and a link to testing.GovStack.global (GovStack.global and mid-term Impact Exchange)

d. 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

  • No labels