Scrum methodology is an agile framework for product development that utilizes iterative cycles and story points, which represent varying levels of effort and unpredictability in task estimation. Techniques like planning poker help teams estimate these points collectively while minimizing cognitive biases. The document also outlines roles in sprint planning, including developers, contractors, and team leaders, illustrating how story points are allocated and the authentication process for code changes during the development cycle.

1. Scrum methodology
SCRUM IS AN ITERATIVE AND INCREMENTAL AGILE SOFTWARE
DEVELOPMENT FRAMEWORK FOR MANAGING PRODUCT DEVELOPMENT

2. Scrum life cycle

3. Story point is an arbitrary measure used by Scrum teams. The idea is that the larger the story is,
the more uncertainty there is around it and the less accurate the estimate will be.
Using the Fibonacci sequence 1,2,3,5,8,13,21,34,45 helps teams to recognize this uncertainty, deliberately creating
a lack of precision instead of wasting time trying to produce estimates that might also carry a false degree of
confidence.

4. Planning poker, also called Scrum poker, is a consensus-based, gamified technique for estimating,
mostly used to estimate effort or relative size of development goals in software development. In planning
poker, members of the group make estimates by playing numbered cards face-down to the table, instead of
speaking them aloud.
The cards are revealed, and the estimates are then discussed. By hiding the figures in this way, the
group can avoid the cognitive bias of anchoring, where the first number spoken aloud sets a precedent
for subsequent estimates.

5. Your regular developer (which is working on the
project for a long time) usually can close 10 story
points in 2 weeks of development (which is 1SP
per day).
How many story points can close your regular
developer? THE ANSWER TO THAT IS: IT DEPENDS!

6. New developer or temporary contractor can close
from 1 to 10SPs. However, do not expect them to
work equally as a regular developer since they
always need time to understand the business logic,
architecture, potentially study new specific
technology etc.
How many story points can close new developer or
temporary contractor?

7. Team leader can close from 1 to 10SPs. However his
role not just to execute and close the story points, but
also control the execution of tasks on the architecture
level. He needs to spend time to help other team
members with their tasks, organize cooperation inside
the team, perform code reviews etc.
How many story points can close a team leader?

8. Feature freeze or code freeze
– Once the code is ready for beta and frozen, all
source code commits require bug id. No new
feature check in will be allowed and source tree is
locked.
The code will be reviewed by code reviewer. Once
it is reviewed, the QC project lead will open the
permission for the developer to check in.
– Any last minutes bug fixes require a review by
two chief architects.

9. Example of sprint planning
 Sprint duration – 2 weeks
 Code freeze – 1 week
 Team – 3 stable developers, 1 contractor(temporary resource), 1 team
leader
 Story points in the sprint:
 3 developers – 3*10 = 30 Story points
 1 contractor – 3-5 Story points (since new person always requires involvement
into the project)
 Team leader – (0-2) story points
 Totally = 35 story points

10. Sprint Planning
During the Spring Planning Meeting - Team mutually
distributing the tasks between developers and assigning
them in the issue tracking system like Atlassian JIRA.

11. JIRA is an issue tracking product, developed by Atlassian. It provides bug tracking, issue tracking,
and project management functions. Jira is fully adjusted for SCRUM methodology.
Product owner has an ability to control the development
life cycle and always be up to date using scrum board,
burn down chart etc.
Developer can always see his outstanding tasks for the
Sprint and check if there is any bugs was spotted but QA
team in order to fix them during Code Freeze period.
QA team can observe which particular task is completed
and ready for testing. Tester can register any bug spotted
during the testing and assign on the appropriate person
to fix.

12. Agile Testing
 - Agile team tests continuously and continuous testing is the only way to ensure continuous
progress
 - Agile testing provide feedback on an ongoing basis and the product meets the business
demands.
 - Each and every iteration, Business team
involved and continuous feedback
shortens the feedback response time and
cost involved in fixing is also less.
 - Testing is done while implementation

13. Regression testing
Once all the tickets tested from the Sprint QA team start performing regression testing of
the system according to all Test Cases in the system. Below demonstrated an example of few
test cases from the system. Each test case must be tested by automation or a manual test.

14. twitter.com/Diceus_com
facebook.com/diceus linkedin.com/company/diceus
empower your business with diceus
diceus.com
info@diceus.com
blog.diceus.com
Thank you!