Welcome to the Exact Product Blog

On this blog we will cover stories from all around the Exact ecosystem.

The power of Scrum: the business drives IT!

Written by Bert Siekmann on . Posted in Exact Globe, Exact Synergy

Since the start of 2010 we have developed both Exact Globe and Exact Synergy with the help of the Scrum methodology. Scrum is an iterative, incremental framework for agile software development.

Mmm, are you lost? Do you understand what this is about? Maybe you do, but let me explain how we and our customers benefit from Scrum. The power of Scrum is continuously focus on quick delivery of maximized business value.
Through early feedback we can react faster so quality, understandability and predictability of software development can improve. This will give us an agile development process in which we can deliver better products in a shorter time frame.

Scrum contains sets of practices and predefined roles. The main roles in Scrum are:

  1. the “Scrum Master”, the facilitator. A key part of the Scrum Master’s role is to protect the team and keep them focused on the tasks in hand.
  2. the “Product Owner”, who represents the voice of the customer. He/she ensures that the Scrum Team works on the “right things” from a business perspective.
  3. the “Team” has the responsibility to deliver the product. A team is made up of 5–9 people with cross-functional skills who do the actual work (design, develop, test, technical communication, etc.).

During each “sprint”, in Exact a two-week period, the team creates a shippable product enhancement (for example, working and tested software). The set of features that go into a sprint come from the product “backlog”, which is a prioritized set of high level requirements of work to be done. Which backlog items go into the sprint is determined during the sprint planning meeting. During this meeting, the Product Owner informs the team of the items in the product backlog that he or she wants completed. The team then determines how much of this they can commit to complete during the next sprint. During a sprint, no one is allowed to change the sprint backlog, which means that the requirements are frozen for that sprint. After a sprint is completed, the team demonstrates how to use the software.

An important advantage of the Scrum approach is that planning is a continuous repetitive activity. Scrum does not try to predict the future at the start of a project, but aims at continuously improving the estimates based on experience. Each sprint the productivity of the team is determined and this knowledge is used to make a more accurate estimate for the next sprint. Furthermore estimating tasks are being performed by the team itself, and the whole team is doing it. This has two major advantages. First, the estimate are based on the knowledge and vision of all team members and therefore more realistic. Second, everyone is committed to the estimate, because everyone must agree on an estimate during planning. Another important advantage of Scrum is it always serves the business. A Scrum team is always working for the actual most important business goals, and the business may if necessary adjust quickly. And because a Scrum project should yield operating software on a regular basis, and the product owner determines what functionality should be delivered, it is not possible to pass difficult problems to the back. Finally, the Scrum approach has some financial benefits. With Scrum key functionality can be taken in production as soon as possible. The return on investment is higher, and the financial impact of any delay is smaller.

Please share your experience and ideas via a comment to this article  and use the ‘share and enjoy’ buttons!

Tags: , , , ,

Comments (5)

  • jzk



    Are you using eSynergy for tracking tasks?


  • Bert Siekmann


    Hi JZK,

    No, we manage all tasks manually with sticky notes on the walls. This way of working empowers scrum within our development center! It’s transparent, it’s visualizing and gives a lot of positive dynamics at the office floor.



  • Jzk


    Hi Bert,

    Thanks for answer.

    You know, I’m asking ’cause we are looking into using eSynergy as a scrum tool. Do you know any success stories in this field?

    Thank You,


  • Ronald Voets


    Hi Jzk,

    as an addition to what Bert mentioned above. Indeed, the scrum teams (software engineers, QC, architects, etc) use sticky notes on the wall. Besides that, the rest of our development process is largely using the power of Synergy. Examples:
    – Release planning
    – Project planning
    – Change planning and tracking
    – Defaults/bug tracking
    – Documentation
    – Communication to custoemrs on new improvements (release notes)
    – Targets and sources are stoed within Synergy (as items/item attachments) so custoemrs can download it from Synergy as well
    – Forum for discussions and Q&A

    We’ve quite a few customers using Synergy to manage their development process so it’s well suitable for that purpose. To replace the sticky notes with Synergy “tasks” is easily possible but we consciously decided not to do so, for reasons Bert explained.

    Hope this helps you.


  • Jzk


    Thank You, now it’s more-over clear to me.

    Thank You for your responces guys.


Leave a comment