...
Kick-off
The kick-off meeting is a pitching meeting where our customers or staff walks through the discovery and decision-making session where the customer or internal stakeholders present a product idea and what the problem it aims to solve. In this meeting the customer value is discussed During this session, we explore customer value, feasibility, and the effort of building needed to build a prototype to pivit validate or pivot the idea.
KickA kick-off meetings can also decide to not build a product if the value is may also conclude with a decision not to proceed, especially if the projected value is too low or the estimated effort is to hight too high compared to the incomepotential returns.
...
Planning
Approved products hava product ideas are translated into a roadmap that describes the outlines high-level requirements and what prio to start work withpriorities. The plan activity planning phase is key essential 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
Requirements is the activity of where we breakdown them and prepare the work for the current sprint.
Design
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.
Implementation
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.
Prototype
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.
Security & Performance review
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
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 managers, helping them rank backlog items based on stakeholder input, customer impact, and technical needs (e.g., bug fixes).
Planning is an ongoing activity, revisited regularly throughout the product’s lifecycle.
Requirements
In this phase, we break down prioritized roadmap items into actionable requirements, preparing them for inclusion in upcoming sprints. This ensures that all team members have clarity on scope, dependencies, and deliverables.
Design
Design works hand-in-hand with implementation. At Rixter, we aim to develop testable designs before development begins. These can include mockups, flowcharts, or scenario-based diagrams to ensure shared understanding across teams.
Implementation
This phase covers coding, testing, and integration. Rixter emphasizes test-driven development and uses tools such as Jenkins and SonarQube for CI/CD and code quality assurance.
We strive to maintain a high level of test coverage to ensure product stability and maintainability.
Prototyping
We produce a working prototype at least every second sprint. These prototypes serve as internal release candidates and form the basis for customer demos and feedback.
Security & Performance Review
Security is integral to our process. We routinely test for OWASP Top 10 vulnerabilities and, where appropriate, engage external security firms for independent assessments.
Performance is a continuous focus. We optimize product responsiveness in every sprint and, for datacenter products, conduct annual performance tests in line with Atlassian’s standards.
Known vulnerabilities and CVEs are tracked and prioritized for resolution.
Release (Ship)
The “Ship” phase marks the official release of a product to the market or customer.
Atlassian Products: We package stable, tested prototypes and publish new versions to the Atlassian Marketplace.
Custom Deliverables: For closed or client-specific products, releases are shared via a structured Google Drive release folder.
Evaluation & Feedback
In Feedback can be submitted by customers at any time during the product 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. This feedback is crucial for continuous improvement. Additionally, we conduct surveys and usability studies to better understand the customer experience and identify improvement areas.