The kick-off meeting is a pitching meeting where our customers or staff walks through the product idea and what problem it aims to solve. In this meeting the customer value is discussed and the effort of building a prototype to pivit the idea.
Kick-off meetings can also decide to not build a product if the value is low or the effort is to hight compared to the income.
Approved products hava a roadmap that describes the requirements and what prio to start work with. The plan activity is key for our product manager to rank the backlog items in accordance to the stakeholders and bug fixes.
This activity is repeatedly done throughout the lifecycle of the product.
Requirements is the activity of where we breakdown them and prepare the work for the current sprint.
Design goes hand in hand with the next topic which is implementation, at Rixter we aim to get testable designs before developing the product. This could be done by mockups, flowchart or scenario based development.
This is the activity of coding and testing, at Rixter we aim to use as much tests as possible to get stable product out on the market. The development cycle also uses tools like Jenkins and SonarQube to automate and check the code.
On each or every second sprint there is a prototype produced. This is the base for our release candidate and what we show during demos.
At Rixter we test for the top 10 OWASP security vulnerabilities. From time to time an external company is used to assess the security depending on the product.
Performance is a property that we always try to focus on in each sprint, make sure the product is a snappy it can be. For datacenter products we also conduct the yearly performance tests required by Atlassian.
Vulnerabilities is listed here Vulnerability fixes and CVE records
Ship is the activity were we release the product to the market or the customer. For Atlassian products this normally means taking a stable and tested prototype and adding a new version on the Atlassian marketplace. When
For closed software for customers then this process is done using Google drive release folder.
In any time during the lifecycle customer can submit feedback and evaluate the products, these feedbacks is important for us to improve the products. In addition we conduct studies and questions on how customers experience the products.