IT Scrum organizations
Teams organization
All tasks in English
IT Definition of Done
Analyze task
The diagram on confluence after discussion with the Team
Team meeting explaining subject + next steps
Next tasks in JIRA
Technical task
Unit Test Code coverage - 80% for changes
A merged task in master branch
Check transaction DEV/STG.
Prepared migration script.
Finished Review - We need 5 points to merge task. AP RS point does not counts.
Documentation update.
Comment under the completed task, what was done, how to test
Leave
Send email to kadry@autopay.pl
Set up autoresponder in English!
Leave a comment on every task in the sprint assigned to You
What has been done
What more should be done?
Can we deploy that?
Put a summary of Your tasks on chat for the rest of the Team.
Sprint
General
1 Story Points task - A small change like Typo goes through the whole process and DoD.
There is no left task in sprint take first task from next sprint.
Document what you’ve learned - immediately!
Use Wiki for documentation of every knowledge that we asses
Technical team meetings ad hoc if there is problem.
Timeframe
Default 1 week, but can be extended on planning to 2 weeks.
We stick to the meeting time frame.
Flagged task
Tasks that are critical for Sprint Goal / Project goals.
Daily
We talk only about blockers. Everything else is in JIRA.
Last man on meeting starts.
Backlog refinement
One of developer is host of the meeting.
We use Magic Estimation for estimation - https://bluemedia.atlassian.net/plugins/servlet/ac/com.magesti/estimate
Filtr
project = CPD and "Story Points" is EMPTY and status NOT IN (Closed , Resolved) order by rank asc
Change request classification
Epic | Description | Business reason | Technical reason | Priority |
|---|---|---|---|---|
Changes request from client. Its business request. | YES (client needed) | No | TOP PRIO | |
Tasks with decision to make with compliance. Only decision task - no task to do. | N/A | N/A | TOP PRIO | |
Ideas for business improvements. They can affect on production. | YES | YES (can cause additional work) | MID PRIO | |
Ideas for technical improvements. They do not affect on production now but they can.
| DEPENDS (can impact on production) | YES (can impact on production) | LOW PRIO | |
Ideas for future use. For now nice to have as there is no business needed for now. | No | No | NO PRIO | |
Tasks for Fenige to get / understand system. | N/A | N/A | N/A |