When it comes to web and application development, our programmers always take your personal requirements and needs into account using a 2-stage strategy:
Phase 1: Creating a concept, UX Design and specification
At the outset, the experts in our app development agency work with you to define your KPIs (Key Performance Indicators) and company goals. Then, we set up the right B-works project team to develop your website and/or app. Team members each have different industry expertise and specific project experience.
Based on the overall goals that we define at the outset with our customers, we divide the project into user stories. These user stories are written in concise every-day language and set the scene for the subsequent programming requirements. User stories are one of the most important methods we use to steer an agile project. Working with our customers, we prioritise user stories to fulfil important initial requirements and make quick-win adjustments early on.
Then, we create individual customer personas and plan the UX process. Based on these customer personas and the user stories specified at the start, we create a responsive web design using the ‘Sketch’ design tool. Our UX designers share Sketch prototypes with our customers using InVision. We synchronise prototypes with individual artboards to give you, the customer, an insight into the work of our designers and the opportunity to easily specify your requirements.
In terms of costs when setting up individual user stores, we base our estimate on similar successfully completed B-works projects. We also use our design and user stories in order of priority to form the basis for specifying a MVP (minimum viable product) and an initial go-live schedule. Following these initial specifications, we then formulate an offer for the second phase of the project.
Phase 2: Development
In the second phase of our web and app development, project, we use the agile Scrum system. A Scrum team consists of a product owner (a digital project leader in charge of products), as well as individual team members who have the right skills and experience (e.g. back-end developers, front-end developers, designers, etc.). The second phase begins with a kick-off meeting for the customer and all team members. During this meeting, we clarify any outstanding issues and fine-tune the specifications. The next step is to record user stories as backlog items using the Jira ticketing system. This estimates the time required for each task.
Sprint planning takes place once a week or once a fortnight during the project phase. Specific planning features are the Sprint Retro-perspective and Sprint Review. We discuss and approve the tasks completed during the previous week, then define the tasks for the week ahead. This ensures that the project runs to time (and to budget). After each Spring planning meeting, if required, the product owner can fine-tune everything with the customer. This helps us to identify ready-made software packages and clarify any issues that may arise, using feedback to ensure the best possible results. Our B-works team meets every day. Every team member briefly explains what he/she is working on and identifies any barriers that might be in the way of progress. The Scrum Master then deals with these barriers and removes them, so team members can focus on completing their tasks. At the end of each month, the customer receives a breakdown of the hours spent working on the project using the Jira ticketing system.
During the project, our testers and developers carry out ongoing tests and bug fixes (= debugging). When all tasks have been completed, we publish an initial version of the website or application on a test server (i.e. a password-protected server that isn’t accessible to online users). After testing is complete, we ensure that all the user stories and requirements listed in the customer’s specifications have been included. Then, we schedule a go-live when we activate the website and/or application on a live server, i.e. open for public online access.
All B-works developers use the Github source-code management system. This allows them to work together on projects and file and document program codes. All codes are open-source, so you won’t have to pay any license fees and benefit from unlimited usage rights.
Find out more about this process in our Pistor project case study!
If you already have a website or application and would like us to work on this, we’ll need the source code and possibly access to the code repository (e.g, Github or FTP), as well as access to the existing system, such as the Drupal login data.
Please don’t hesitate to contact us if you have any questions! We look forward to hearing from you and providing further assistance.