Usually, when we start cooperation with a new company that has no experience in relations with Software House, or these experiences had – euphemistically speaking – very disappointing, we focus on showing the goodness of the IT world, which non-technical people can use.
This is a milestone because:
- Firstly – a bond is formed between the Business that provides its requirements and the production team that implements them.
- Secondly – we all „learn” each other, and especially how to communicate with each other.
- Thirdly – our and many other organizations’ experience shows that knowledge of ourselves and the tools used at the beginning of the project means that we increase the chances of final success. And that’s what both sides are all about – success and satisfaction.
So let’s get to know the most needed and most frequently used tools in our work today.
Software House agile as Scrum
A Scrum is an agile approach to project management. In this case, we are not talking only about software development. Also about services or any task that has any value for someone. This can be, for example, producing a podcast or planning a marketing campaign. Scrum is largely based on delivering the product in small increments. This causes that at any time, every person – from Business too – involved in the project to a greater or lesser extent knows what stage it is at.
It is also very important to know that Scrum assigns roles to people involved in the project. So that each of them knows what scope of work and responsibilities is entrusted to her.
The most important roles are:
- Firstly. Developers – a team of people (not only programmers) who have all the skills and resources to deliver the final product.
- Secondly. Product owner – a person or a team of people who have a vision of the entire product. Thanks to it and the knowledge they have, they can decide what is the most important to be delivered at the moment.
- Thirdly. Scrum Master – a person who observes the progress of the project and talks with team members. Thanks to his knowledge and experience, he can advise and help increase the effectiveness of cooperation between members of the project team. This may affect the deadlines of the product.
In conclusion, Scrum is not only about roles, but also processes. It is they who largely create the culture of agility and speed in the project.
The most important processes and tools in Scrum
- Product Backlog – to clarify, is a place where the Business, Product Owner lists his needs and visions. The principle of placing the most important needs at the top and the smallest ones at the bottom must be respected.
- Sprint – within Scrum, we work in maximum monthly (but usually 2-week) iterations. In each iteration, everyone works to achieve and deliver the Sprint Goals, as set out in:
– Sprint Planning – a meeting during which sprint goals are set, the scope is planned, risks and any ambiguities are discussed.
– Daily Scrum – daily meetings of all stakeholders. During this, they discuss the progress of project work and whether the sprint goals are still realistic. If anyone needs any help, they report such a need during the Daily Scrum. Then also such support and help are organized.
- Product Backlog Refinement – or meetings within. in which the Product Backlog is organized, the tasks are detailed, estimated, and discussed.
- Sprint Review – a meeting during which Developers and Product Owner discuss and show Stakeholders what was done during the last sprint. This is the penultimate so-called Scrum Rite.
- Sprint Retrospective – is the last of the Scrum Rites. A meeting during which the Product Owner, Developers, and Scrum Master discuss everything that has been done right and wrong. Determine how to work better and more effectively.
As you can see, getting to know Scrum can help the Business to tame the entire project. At any time, the Business knows where the project is and can decide whether or not to change something (agility).
Getting to know the assumptions, roles, processes, and tools of Scrum is one thing. The second important thing is to use these elements effectively. It is best if it is implemented through dedicated tools.
How is it with us? In cooperation with our Clients, we use Jira software with appropriate plugins, which greatly facilitate both the implementation of Scrum and the ongoing monitoring of progress. Also providing information on current expenses for Software House.
In addition to Jira, we use Google Meet for everyday meetings, which facilitates remote work. We use a dedicated tool for Sprint Retrospective.
Event Storming – an eye on the project
In addition, most important tool we use is Event Storming. Here, for general information, please refer to our previous post about ES.
However, how to use Event Storming throughout the project?
Begin all work with the so-called Big Map session – showing the entire problem/vision of the product. On the other hand, from time to time to meet Business to detail individual processes or commands.
Continuity – speed and savings
From the point of view of the Software House, it’s a very important thing. The point of view of the Business is even more important.
Start working on a new project or with a new software supplier from the implementation of CI/CD (Continuous Integration and Continuous Delivery). As a result, you will always be able to view the current version of the product being created. The supplier will probably know how to choose the right tools. And what the sequence of implementing CI/CD to the project should be.
Sometimes, however, with mutual consent, the Ordering Party agrees to use the infrastructure and tools of the Software Provider’s CI/CD for development and testing purposes. This is what we often do to speed up the work and save the Client from infrastructure-related expenses.