SyncForce has 16 major releases per year, delivering about 200 new or improved features annually. We have a standard method to define the order in which features are built.
Short URL to this page: https://synf.co/priolevel
At the start of every development sprint of three weeks, the latest priorities are used to define the feature list of the next release.
Feature priority is first based on six ranked feature levels (L1 until L6). Within each level, there is a secondary system to prioritize the features.
Feature Priority Levels
L1 | High Information Security Risks
- Based on new security risks discovered in the market or through results from our annual penetration tests.
- These will be addressed as soon as possible; high information security risks are treated as bug fixes.
- Bug fixes go live via a daily minor release.
- SyncForce will prioritize and plan high-risk features based on internal evaluation.
- Priority date stamp (YYMMDD) is the date that the security risk was identified
L2 | Features Required Due to New Regulations
- The priority of features required due to new regulations is driven by regulatory deadlines, combined with the development, text, and data transformation/collection effort.
- SyncForce will prioritize and plan these features based on internal evaluation.
- Priority date stamp (YYMMDD) is the date that new regulations becomes active
L3 | Breaking Changes in Data Channels' APIs
- Most DataPools and other data channels have regular updates. The most dynamic ones are the national GS1-GDSN DataPool updates.
- The priority of features required due to Data Channel connector changes is driven by the deadlines in the communicated change, combined with development time and effort, and the time needed for product managers to collect and submit any new data points in SyncForce (e.g., Form Type for Polymer Packaging Materials mandatory as of ...).
- Priority date stamp (YYMMDD) is the date that the API changes will go live
L4 | 100% Customer-Funded Features
- Requested features that are fully funded by the requesting company receive priority level 4.
- Within Level 4, features are built based on the signed order confirmation date.
- Priority date stamp (YYMMDD) is the date that the order confirmation was signed
L5 | 50% Customer-Funded Features
- Requested features that are 50% funded by the requesting company receive priority level 5.
- Within Level 5, features are built based on the signed order confirmation date.
- Priority date stamp (YYMMDD) is the date that the order confirmation was signed
L6 | Backlog Unfunded Feature Requests
- Level 6 features include all remaining requests based on submissions posted on Club SyncForce, feature gaps identified during the design phase of new SyncForce implementations, generic maintenance features, etc.
- Funding of Level 6 Features: SyncForce funds Level 6 features as part of your SaaS license.
- Prioritization of Level 6 Features: The SyncForce team prioritizes these features based on internal considerations such as development effort, frequency of requests, user benefit, commercial strategy, etc. By posting your feature request on Club SyncForce and encouraging other customers to support it, you may help elevate the priority of your request within the backlog.
- Development Timeline of Level 6 Features: Until a feature is planned for development (i.e., scheduled in an upcoming major release), there is no indication if or when a requested feature will be built. The number of Unfunded Backlog Features that can be planned per release depends on the volume of features in the other priority levels.
- Priority date stamp (YYMMDD) is the date that SyncForce decided to start developing this feature.
Quotation requests
We distinguish two types for quotation requests
- Ballpark: Based on T-Shirt sizes we give a first rough indication of the expected development investment.
- Mandatory Input for Ballpark estimates : Deck with high level situation, challenge/opportunitiy and requested solution direction.
- Invest: Based on a detailed the design a cost estimate will be made. Invest requests are assign a priority level and intake take.
- Mandatory Input for Invest estimates : Deck with current situation with full as-is analyis, challenge/opportunities and detailed requested or suggested solution direction.
- Invest proposals including the solution designs will be made based on the following prioritization
- First on priority level (QL1,QL2,QL3)
- Then on intake date (oldest first.