The document outlines the agile development process, specifically using Scrum methodologies, detailing various ceremonies such as sprint planning and reviews. It describes the workflow from planning and estimation of tasks to development, testing, and final review, emphasizing the 'definition of done' and 'definition of ready' criteria for tasks. Additionally, it highlights the importance of collaboration within teams and the need for clear communication regarding user stories and acceptance criteria.

1. Development process
agile | programming | teams

2. DEV. Process - overview & example

3. SCRUM
ceremonies
next
iteration
1. PLANNING
2. REFINEMENT
(GROOMING)
3. REVIEW (DEMO)
4. RETROSPECTIVE
daily

4. sprint 2
10AM SPRINT
PLANNING
sprint 1
QA
Release person
Mon Tue Wed Thu Fri Mon Tue Wed Thu Fri Mon Tue Wed Thu Fri MoWed Thu Fri
bugfixing/dev DevelopmentDev Team
1-2 days to fix leftovers (if any) Code Freeze
release “develop”
branch to staging
1-2 days of regression
testing on staging
2PM SPRINT
REVIEW
(on develop branch on UAT env.)
testing on staging
Release to
PROD on Wed
testing on staging
bugfixing/dev Development
Testing, Automation Testing, Automa
UAT on
PROD
10AM SPRINT
PLANNING
UAT on
PROD
SCRUM
ceremonies

5. SCRUM Process - PLANNING

6. Planning
ceremonies
prioritized
backlog
backlog
items
effort
involved for
each item
iteration
forecast
iteration
forecast
PO & team discuss
PO brings
team estimates
team makes
work becomes
team prepares for
planning (e.g. questions
to User Stories in Jira)
team creates tech. tasks
for User Stories
1
1
1
2
1
3
1
5
1
8
1
1
3
1
2
0
?
!
!

7. Estimations
ceremonies 1
1
1
2
1
3
Estimation is hard.
Agile estimation is a team sport.
effort
involved for
each item
team estimates
team makes
iteration
forecast
story points
for User
Stories
hours for
tech. tasks
team estimates
team estimates

8. Dev & QA process

9. TODO
DEVELOPMENT
CODE REVIEW
TESTING
PO SIGN OFF
DONE
REOPEN
IMPLEMENTATION APPROVED BY
PRODUCT OWNER
MANUAL TESTING
PASSED
CODE REVIEW PASSED
READY FOR TESTING
READY FOR
REVIEW
START
DEVELOPMENT
workflow
process

10. TODO DEVELOPMENT CODE REVIEW TESTING PO SIGN OFF DONE
process Board
process

11. step 1
developer
get newest code
from master
dev & qa
dev process

12. step 2
developer
create new branch
for feature/bug
step 1
developer
get newest code
from master
dev & qa
dev process

13. step 3
developer
implement new
feature / fix bug
step 4
developer
add unit tests
step 2
developer
create new branch
for feature/bug
step 1
developer
get newest code
from master
dev & qa
dev process

14. step 5
developer
rebase with master
and squash commits
step 6
developer
push to Github
and create Pull Request
step 7
developer
code review by
another developer
step 8
tester
manual testing of feature
branch on Testing instance
step 3
developer
implement new
feature / fix bug
step 4
developer
add unit tests
step 2
developer
create new branch
for feature/bug
step 1
developer
get newest code
from master
dev & qa
dev process

15. step 9
developer
merge to master - if code review is done,
and testing passed successfully
step 10
tester
final testing of feature on UAT
instance on master branch
step 5
developer
rebase with master
and squash commits
step 6
developer
push to Github
and create Pull Request
step 7
developer
code review by
another developer
step 8
tester
manual testing of feature
branch on Testing instance
step 3
developer
implement new
feature / fix bug
step 4
developer
add unit tests
step 2
developer
create new branch
for feature/bug
step 1
developer
get newest code
from master
dev & qa
dev process

16. Agile process

17. Definition of DONE
agile process
A task is done only when the following points are met:
● the implementation is completed according to description/acceptance criteria,
● if applicable implementation is covered by unit tests,
● all unit tests pass on Jenkins build,
● the code is reviewed and accepted by other developer, giving +1 when all comments are actioned,
● testing scenarios are prepared and documented,
● all tasks are tested and pass all testing scenarios and acceptance criteria,
● implementation works on the newest versions of browsers,
● code is merged into the main development branch,
● story is done when the PO has signed it off.

18. Definition of READY
agile process
Minimum Required Information
● Stories with description in User Story format and acceptance criteria.
● Bugs description according to bug reporting template.
● Chores and Spikes with defined expectations.
● Any changes to non-functional requirements highlighted.
● Sprint backlog is prioritized.
● Designs are available when required.
Additionally for a Sprint
● Project goal/roadmap updated and dates/meetings clarified.
● Sprint theme with SMART goals.
● Teams should understand business value/justification.