Agile: Project methodology

1.  Kliknij, aby edytować styl wzorca podtytułu
vContact: | www.britenet.com.pl | tomasz.kostienko@britenet.com.pl | (+353) 85 126 1081
Agile Process

2. SCRUM methodology ensures control at each stage of the project. Full
transparency of the project is provided and close cooperation with the customer
is maintained at all times. We understand and fully expect that requirements can
change, and that projects often need re-defining. Our focus is on meeting the
customer’s requirements, which is not always the same as “compliant with the
documentation”. Agile methodology represents a successful implementation for
our clients.
Why we choose SCRUM.

3. The “big picture” is a multi-level presentation of our
understanding of the project requirements .
This is the foundation of our understanding of:
who will use it and what for,
whether it will communicate with other systems and, if so,
with which ones,
what are the most important business needs that the
system will address.
This will provide a comprehensive overview of the total
project
An example of a requirement phrased as a User Story:
Asthe owner of a bank account
The project pricing is carried out by determining the level of
complexity of individual requirements. Our evaluation of
particular stories (use cases) is based on the knowledge and
experience gained with many years experience. Based on this
experience, we are able to compare the requirements and
define the complexity.
From the entire Product Backlog, we choose the least and the
most complex story and several intermediate ones and we
discuss them with the customer in detail. Those stories are
the reference point for the other requirements.
The complexity of each story is estimated by the team based
on the values of Fibonacci numbers.
The sum of points from the stories and the average number of
points implemented by the team, determines the
date of project completion.
The final stage – the pricing„Big picture” in order to achieve
something
As whom
I want to do
something
in order to be able to withdraw money when
the bank is closed
I want to withdraw money from the ATM
User Stories should also contain Approval Criteria, i.e. a
set of requirements whose completion allows both the
team and the customer to be sure that the client criteria
has been met. For the initial pricing, general criteria is
sufficient, for example:
entering of the correct PIN code authorises the user;
entering of the incorrect PIN code causes display of a
message on an unsuccessful attempt;
after 3 unsuccessful attempts, the card is blocked by
the ATM.
Product Backlog is a set of business requirements
arranged by priority. Primarily, there are features without
which the system cannot function, i.e. those that meet
the most important business needs.
Product Backlog elements most often take the form of
User Stories. The requirements are phased:
Product Backlog
How is a project priced ?

4. How do we organise work in a project?
The team delivers and presents the functional
software after each iteration (the so-called
sprint). Presentation of the performed work
takes place in a test environment. It is always a
functional application, which allows for on-
going control of work progress and the
possibility to verify the requirements defined at
the beginning of the project.
Each sprint is a cycle of events taking place
sequentially:
Planning
choosing User Stories for the next sprint
from the Product Backlog;
setting the goal of the sprint;
accepting the scope by the Team and the
Product Owner.
Daily Scrum Meeting
an everyday 15-minute meeting to
organise the entire day of work and
indicate the blockers;
full control, eliminating blockers;
self-organisation.
Grooming
refinement of the requirements;
joint development of the Approval
Criteria.
Review
presentation of the features implemented in a functional
application;
the customer continuously sees the progress;
we can make and react to comments on an on-going basis;
formal approval of the work performer.
Retrospective
after each sprint, we indicate how to improve the process and
effectiveness of the team;
we identify and eliminate our weaknesses;
resolutions in a visible place – we control each other;
the customer actively participates in the meeting; full
transparency of the team.

5. Our methodology requires full control at each stage of the project, working
closely with the client's Product Owner.
The Product Owner should have the authority to make decisions, and answer the
team's questions within the shortest possible time. It is recommended that the
Product Owner works in the same location as the Team. This ensures a high level
of communication, which is the basis of the agile methodology.
What do we need from
the customer?

6. Quality!
v
Definition of Done (DoD) is the completion of the
common criteria of application quality as defined by the
team and the Product Owner. DoD is defined for each
sprint and defines when the requirements are met, other
than from the Approval Criteria.
Definition of Done
They indentify the detailed conditions and requirements
that have to be met by a feature to be considered
implemented. The Approval Criteria is verified at several
stages:
Only those user stories that are not linked to any errors,
Approval Criteria or DOD are considered implemented. Only
then we do state the application is functional.
Approval Criteria DONE means DONE!
coding tests review

7. How we know we will
make it on time.
Burndown Chart for sprints
The progress of work in a sprint is represented on a chart of implemented stories. Each story
has a certain amount of points assigned to it; those points indicate its level of complexity. The
chart is updated live and is available to all the people assigned to the project.
Burndown Chart for the project
The progress of work in a sprint is represented on a chart of implemented stories. Each story has a
certain amount of points assigned to it; those points indicate its level of complexity. The chart is
updated live and is available to all the people assigned to the project.
The progress of works in a project can be represented by the chart of “burnt down” points. When
the sprint is over, it means that a certain amount of points have been burnt down, based on this a
simulation of the project progression is created. Using historical data, we are able to foresee various
scenarios for the project and promptly react to any possible deviations from the scenario that would
impact it.

8. for your attentionThank you
vContact: | www.britenet.com.pl | tomasz.kostienko@britenet.com.pl | (+353) 85 126 1081