K2 is a powerful workflow and online forms platform. Building a K2 solution requires a few key ingredients to ensure its long-term success.
K2 Automated Testing Software
rnBenchQA allows full test automation of K2, including fully automated K2 SmartForms and K2 Workflow testing. It promotes test driven development for K2 and ensures continued quality assurance for K2 solutions. Easily apply changes to test cases to accommodate changes to K2 apps and ensure all apps are regression tested to avoid defects and assure continuous quality.
Although K2 is a very easy to use and an intuitive workflow platform, having full project lifetime experience is essential to ensure every K2 project is a success and that its benefits are fully exploited.
Steps to K2 success:
1. Process discovery and analysis workshops
Understand what the short and long-term project goals are and what the existing business challenges are that the solution will address. The aim is to identify an overall high-level requirement, and also a set of initial detailed ones and their position in the bigger picture. This small set of requirements will be implemented in the initial K2 development sprint. This phase should be kept short and focused.
2. Modelling a solution
The next step is to model a solution that will fulfil the initial requirements. The solution also needs to be flexible enough to accommodate future enhancements and additions and reach the end goal as defined in the first step. Use a modelling tool that is easy to use and understood by non-technical users. Review the models with project stakeholders and apply any changes as required.
3. Implement the K2 solution
Use K2 to implement the solution models. The output of the solution modelling should reflect the K2 solution as close as possible to ensure it will fulfil the business requirements and to ensure that the K2 implementation is easy.
Quality check the K2 solution to ensure it is defect free and fulfil all functional needs. Schedule an acceptance session with the users to ensure all the required features are available. Because a visual model of the system was produced and reviewed earlier in the project iteration, acceptance should be easier.
Ensure the production system is fully supported and maintained to ensure its long-term success. Fix all issues quickly to ensure users don’t loose confidence in the system. Do user surveys and feedback responses to the next project iteration. This ensures continued buy in from the users.
Repeat the 5 steps as often as required to meet long-term project goals. The key is to keep each iteration as short as possible, but long enough to ensure meaningful change is achieved with each.