Scrum Method

Clear, transparent, and empirical. We master complex projects using Scrum Methodology

Get a quote now

Why The Scrum Method?

At Pentalog, we’re proud of the agile mindset we’ve developed over the years.  Using the Scrum framework, agility is at the heart of how we work.

Scrum is a lightweight, flexible framework used to manage innovative or complex projects. The goal of Scrum is to improve team productivity and promote client/provider dialogue to ensure project success.

Based on a set of linear instructions, traditional project management has proven to be ineffective in modern business – both because of its rigidity and the lack of communication which creates a “tunnel effect.”

The principle of Scrum is to develop software incrementally by maintaining a transparent list of features, changes, and requests called a “backlog.” With frequent deliveries, the client consistently receives new functionalities in working condition. This method is based on iterative developments at a constant rate of 1-4 weeks.

Scrum Organization

The agile Scrum method is built around three central roles:

  1. The Product Owner: The Product Owner defines and prioritizes the list of product features and chooses the date and content of each sprint based on values (or loads) communicated by the development team. 1 out of 5 Pentalog projects has a Pentalog PO; for the others a PO works on the customer side.
  2. The Scrum Master: The Scrum Master works to eliminate obstacles and protects the team from external disruptions. He or she also pays particular attention to the respect of the DoD (Definition of Done) as well as the teams’ agreed upon rules to make sure tasks are done according to what was defined.
  3. The Development Team: Ranging from 4-10 people, the development team includes all of the required project skills necessary for a project, including the architect, designer, developer, tester, etc. The team is self-organized and focuse on continuous improvement.

As part of Scrum project management, the team regularly holds four types of scheduled events or “ceremonies”:

  • Daily Scrum: Every day, the team gathers for approximately 15 minutes to answer three questions: What did I do yesterday? What am I going to do today? Do I have any blockers?
  • Sprint Planning: The team decides on features for the next sprint and updates the backlog.
  • Sprint Review: Everyone presents the work done at the end of the sprint. The team also presents new functionalities or technical information. The Sprint Review ends with a collective conclusion that is shared with everyone involved.
  • Sprint Retrospective: At the end of each sprint, the team takes stock of what worked and what didn’t. During this last 15-30 minute event, everyone speaks on their own behalf and a vote of confidence is organized to decide on improvements.

The main advantage of the Scrum Method lies in minimizing the amount of documentation in order to gain productivity. That being said, it is far from Scrum’s only advantage.

The Advantages of Scrum

Scrum is a pragmatic response to client constraints:

  • Iterative and incremental method: This helps avoid the “tunnel effect” so frequently seen in projects using V-cycle development (i. e. seeing results only during final delivery.)
  • Maximum adaptability for product and application development: The chronological nature of sprint content allows the integration of modifications or functionalities not included in the original plan.
  • Participatory method: We encourage each team member to express their opinion and participate in all project decisions – building motivation and promoting a sense of involvement.
  • Improved communication: By working in the same office or connecting through various means of communication, the team can easily anticipate and overcome obstacles.
  • Maximized cooperation: Daily exchanges facilitate mutual understanding and teamwork between the client and Pentalog’s team.
  • Productivity improvement: As the Scrum Master continuously handles impediments, team productivity is reinforced.

Who is Scrum Organization for?

The Scrum method can be used in most projects, but is particularly well-suited for those without a strict scope and projects where the client expects progress updates throughout the development cycle.

Client availability can be a significant factor in choosing Scrum. Depending on the size of the team, a full-time or part-time Product Owner is essential.

For projects in which clients are not able to promise a high level of involvement, we will provide an experienced Product Owner to ensure project success.

Concerning projects where development is in “pull flow”, we recommend using the agile Kanban method.

Reach out to us,
describe your project

Choose a development category





QA Testing


Technologies you will need

Technologies you will need

Choose the type of contract