mindworks develops individual web applications according to customer requirements. In an agile process, we record your requirements, formulate user stories with acceptance criteria based on them and offer you implementation at a fixed price. In this way, you receive an MVP (minimum viable product) quickly and at clearly calculated costs, which we develop further in the long term in line with your requirements. Our approach: QUOTE mindworks offers agile software development at a fixed price. We achieve this by identifying the features and functions of the software to be realised together with our client and specifying them in the form of user stories and acceptance criteria. For each user story with acceptance criteria, we calculate the respective implementation effort and thus the costs associated with the implementation. After approval by the customer, we implement the user stories quantified in this way within the framework of an agile software development process. IMPLEMENTATION Ticket system In order to manage the project efficiently and transparently together with our client, we set up access to our ticket system (Atlassian Jira Cloud) for our client and create a separate ticket for each user story, which from then on serves as a container for all information on this user story. Sprint planning The software is implemented in iterations of two to four weeks, so-called sprints. At the beginning of a sprint, a planning meeting takes place in which our project team identifies the tickets that are to be implemented in the corresponding sprint together with our customer. Sprint During the sprint, the mindworks project team coordinates intensively with each other in order to process the tickets efficiently and in high quality and thus implement the specified requirements. For this purpose, there is usually a daily meeting. The software developers at mindworks create a separate branch (development branch) in the version control system for each ticket and, once the work has been completed, transfer it to another developer who checks the programme code and then transfers it to the master (main branch). This dual control principle ensures high code quality. Sprint review At the end of a sprint, a review meeting takes place in which our project team presents the implemented tickets to our customer. Together with the customer, the project team checks whether the tickets have been implemented according to the specification. The tickets identified as implemented in the review meeting are assigned to the customer for final acceptance. If the implementation of a ticket does not correspond to the specification and therefore cannot be accepted, it is taken back for reworking. Acceptance At the time of the review meeting, the current implementation status is available on a so-called "preview server" from mindworks for inspection by our client. On this server, the client can extensively test the functionality and finally accept the implementation of the corresponding tickets. If the implementation of a ticket does not meet the specification and therefore cannot be accepted, the client can return it for reworking. Settlement After the review meeting, mindworks invoices the tickets implemented in the corresponding sprint. The amount invoiced is exactly the amount at which the implementation was offered before work on the corresponding ticket began. CHANGES If, after calculating the implementation effort of a user story or a ticket, there is a need for changes to its specification, the implementation effort must be recalculated. If changes are required after the implementation of a ticket, a new ticket must be created and costed for these changes.