SCRUM method because it WORKS

TRANSPARENT cooperation

SCRUM is one of the most popular software development method of working between the client and the software house. SCRUM allows to produce software faster and high quality. This method clearly defines the role of individual people involved in the project.

The basic unit in the SCRUM is the sprint, which is a separate stage of work.
We can therefore specify the individual steps:


Sprint planning

During which it is determined what will be executed in the course of the next sprint and what is planned to be executed within the entire project, in accordance with the current state.


Sprint execution

Meaning the proper sprint. During the next phase the changes previously determined by the “Team responsible for the development” are being executed.


Daily Scrum

Stands for the team’s daily short meetings with a “Scrum Master” concerning the progress of works in terms of the Scrum and any possible risks.


Sprint overview

Constitutes a meeting after ending the sprint which aims at discussing the course of works and functionalities provided by a given sprint.


Sprint retrospective

Is a meeting which is also referred to as “lessons learned”, during which all issues concerning a product and work organization are discussed, as well as those concerning the recommended improvements for future Scrums.



The stages listed above concern one sprint and are repeated in an iterative manner throughout the entire project. Thanks to this, versions of the software which meet the client’s requirements in accordance with determined criteria are being successively provided.

SCRUM ROLES in project

The name “SCRUM” comes from a formation used by rugby players. It means teamwork – which constitutes the base of success when playing the game, but also analogically applies to a software company. As it was mentioned before, SCRUM defines only the basic roles necessary for an efficient execution of sprints. These are:

Product Owner

Constitutes the connection between the work team and the client. The product owner is responsible so that everything meets the client’s expectations. Together with the client, the product owner creates the product’s vision, orders tasks assigning them with priorities, but also controls and works closely with the “Team responsible for development”.

Team responsible for development

Stands not only for developers modifying the code, but also testers, analysts, and specialists in given fields – everyone whose scope of knowledge meets all aspects of manufacturing software.

Scrum Master

Is a person responsible for taking advantage of SCRUM so that it is used throughout the entire duration of the project. The Scrum Master controls the process of creating software during specific sprints and also the work of the “Team responsible for development”.


Many IT projects are complicated due to the complexity of requirements, integration with other systems, the need to import data from old systems, etc. Much depends also on the communication within the team, as well as between the team and the client. Only a systematized production process can ensure the system’s efficiency as well as the satisfaction of the client with the provided software and quality of cooperation. Scrum constitutes an example of this.

Taking advantage of Scrum at a software company reduces the risk of providing non-functional software, one which does not meet the client’s requirements, including errors, or providing it exceeding the deadline and budget.

Scrum limits this risk by taking
advantage of
three pillars of operation:



Provides the “Team responsible for development”, specific people within the organization, and also the client with access to all works, the same understanding of each Scrum element, and mutual evaluation principles. Thanks to this, the entire process during all sprints, as well as its control and goal are clear and “transparent”.



Allows to monitor and verify the work of the
“Team responsible for development” in real time. It assumes that controlling work progress should be frequent enough to detect the possibility of improvement or prevent errors as quickly as possible. Thanks to this we avoid situations in which for example a functionality is implemented, which the client does not need, or it is a change
which is not quite urgent.



Should constitute the result of an Inspection and leads to necessary changes guiding the “Team responsible for development”. It constitutes a change in the approach to the method of work which happens basically overnight.

Working with SCRUM allows to plan and execute goals on schedule.
And we know how important is time in software development cooperation.

Mike Jackowski
Paul Jackowski


If you’re still in doubt, we will help you find the answers you need.
Just contact us and let’s software together!