Together with the customer's business, we set goals and define key results of digital transformation efficiency.
We use this method to generate product hypotheses based on product goals and research conducted previously
We hold regular meetings with the team, define and refine the terms of reference, detail and discuss every aspect of the task to deliver them quickly, accurately and efficiently.
We use these methods to generate product hypotheses based on product goals and previous research
We use these methods to generate product hypotheses based on product goals and previous research
We divide the large product hypothesis into as small tasks as possible to improve delivery efficiency by parallelising the work and reducing the risk of incorrect estimation of the delivery time.
When a user first arrives on the site, he or she will understand where exactly he or she is going from the very first seconds, thanks to a well-designed design and a system of hints that will guide him or her right up to the point of purchase. In our design, we have differentiated the content to help the user not to get confused on the site and to fulfil the target action faster.
Plan in detail for the next iteration (sprint) of 2 weeks based on the volume of tasks completed in the previous iterations
Plan in detail for the next iteration (sprint) of 2 weeks based on the volume of tasks completed in the previous iterations
We use these methods to generate product hypotheses based on product goals and previous research
Select the most effective product hypotheses in terms of team time spent on development, resources required and potential benefits to be gained
We divide the large product hypothesis into as small tasks as possible in order to improve delivery efficiency by parallelising the work and reduce the risk of incorrect estimation of the delivery time.
We assess each task in terms of the amount of work to be done, the complexity of the competences required to solve the task and the risks the team may face during implementation
Module
Integrational
Smoke
Regressive
End-2-end
Module
Integrational
Smoke
Regressive
End-2-end
A rally where we present the new functionality to stakeholders that we have implemented in a sprint to get feedback.
Sending code to server
Setting up dependencies
Building
Migrations
Launch
Sending code to server
Setting up dependencies
Building
Migrations
Launch
DevOps teams should evaluate each release and create reports to improve future releases. By collecting continuous feedback, teams can improve their processes and incorporate customer feedback to improve the next release
A meeting where the work of the past sprint is analysed according to the principle: "What was good? What could be done better? What is worth trying?".