Maxcode uses Scrum to deliver projects, and we added commitment and prioritisation as key factors to maintain project success.

1. SCRUM
Commitment and
Prioritisation

2. Scrum is a powerful approach to effectively
book project results. It keeps costs and time
manageable and provides practical solutions to
build functionality in a flexible way.

3. Moreover, the method is transparent and very
understandable. Within Maxcode we use
Scrum in our projects since 2009 and we’ve
created an environment to optimally apply it.

4. Duration, cost and functionality

5. Scrum makes a project manageable, yet flexible:
• Fixed duration due to clear agreements about the
duration of a Sprint (a development period) and the
number of Sprints.
• Cost Control by agreeing on a certain capacity per
sprint.

6. The short-cyclical nature of Scrum adds to the
flexibility. The team is working on the current
Sprint, while the Product Owner (customer
representative) freely makes changes for future
Sprints.

7. Functionality can expire, it can be replaced by
other, become more or less important, or it can
receive another interpretation than initially
foreseen, as a result of detailing.

8. The short duration of Sprints makes it possible
to regularly show results and avoid too long a
continuation in a wrong direction.

9. To smoothly manage this flexibility,
Scrum depends on some basic rules.
We’ll highlight two of those rules.

10. Two Scrum Rules

11. 1. Only the development team estimates the
amount of work and determines how much
work fits into a Sprint.

12. 2. The Product Owner determines on behalf of
the stakeholders the development sequence of
the functionality (The Stories in the Product
Backlog).

13. Consequently, the achieved results are variable,
but very predictable by applying the rules.
Moreover, the key functionality is built first.
Correctly applying the rules prevents
undesirable effects on cost, time or quality.

14. Maxcode interprets these rules by:
1. Actually offering the team the chance
to commit.
2. Helping the Product Owner prioritise.
Flickr user Thomas Heylen

15. Commitment
Flickr user Jim Larrison

16. Scrum uses the term 'commitment'. The team
will endeavour to achieve a certain quantity of
functionality in a Sprint. The team gives this
commitment or devotion.

17. If you want the team to be accountable for
performance or if members should be able to
address each other on performance, the
amount of work should never be imposed by
pressure or desire.

18. Excessive workload leads to errors. The danger
of a negative spiral is at hand: More pressure,
more mistakes, more irritation, more errors,
etc.

19. Prioritisation
Flickr user Lars Plougmann

20. Besides commitment, prioritisation is an
important component. In Scrum, this means
maintaining a Product Backlog, which records
the to-be-built functionality (expressed in
Stories), in desired order.

21. An experienced team does this by asking
critical questions about specific functionality
and by composing understandable (not too
technical) Stories.

22. The Product Owner needs to do a lot in the
short period of a Sprint (usually two weeks).
Every Sprint he needs to evaluate the results
and ensure that the order and detailing for at
least the coming Sprint is ready in time.

23. The Product Owner needs to do a lot in the
short period of a Sprint (usually two weeks).
Every Sprint he needs to evaluate the results
and ensure that the order and detailing for at
least the coming Sprint is ready in time.

24. At Maxcode, personal responsibility is
key. We create an environment that
suits the above described way of
working.
Flickr user EG Focus

25. Scrum at Maxcode
Flickr user Florent Darrauilt

26. We directly involve the full team in the
preparation of a proposal. First, a general
description of what needs to be developed is
written. A user model identifies different users
and roles.

27. Only after this has been agreed with the
customer, the Stories are composed and
assessed. We encourage team members to
take a critical look at the order of these Stories.

28. From the moment we hand over the proposal
to the customer, the Product Backlog becomes
his responsibility. Is it clear enough? Is the
order in line with the priorities of the
customer?

29. During the project, the team constantly checks
whether the most relevant aspects are handled
first. They challenge the Product Owner to
make choices if needed.
This creates a good consultative structure, sets
the focus to the most relevant first and gives
the project the cadence it needs.

30. READ MORE
DOWNLOAD THE
FULL WHITE PAPER

31. Maxcode
Deliver your next finance or ehealth application.
Maxcode is an IT service company building tailor made applications
for the European market. We focus on financial and healthcare
industries. Maxcode is located in The Netherlands with offices in
Romania, and the Republic of Moldova. We are a modern company
and a reliable partner for our customers and employees.
Koninginnegracht 19
2514 AB Den Haag / The Hague
The Netherlands
info@maxcode.net

32. Disclaimer
The materials in this document may contain inaccuracies or typographical errors.
Maxcode does not warrant the accuracy, reliability or completeness of the
materials, advices, opinions, statements or any other information displayed or
distributed in this document. All information in this document is provided “as
is” and “as available”, and shall not be binding nor shall it be construed as
constituting any obligation, representation or warranty on the part of Maxcode.
You acknowledge that any reliance on any information in this document shall be
at your sole risk. Maxcode mentions others, their products and ideas as a
convenience to you. Those others, products and ideas are not under the control
of Maxcode. Accordingly, Maxcode makes no representation or warranty in
relation to others, their products, or ideas, other than simply listing them as
relevant for your consideration. By listing them, Maxcode is not endorsing or
recommending them to you.