|Examples / Useful URLs|
|1||Get registered in Jira/Confluence.|
|2||Get registered in Slack, join main channels and make sure your team has a separate channel on Slack.||https://folio-project.slack.com/|
|3||Review documentation on Confluence to get acquainted with the project.|
|4||Review test envs to play with functionality.|
Login: diku_admin / admin
Create Team Page on Confluence.
Organize team calendar.
Use Calendar in confluence to visualize availability of distributed teams.
Configure Scrum Board for the team.
Make sure you have admin permissions to the board and involved JIRA projects.
|8||Add your team to Perf under FOLIO project||https://perf.delivery.epam.com/projects|
Schedule Scrum Ceremonies
|Release Planning / Roadmap|
Quarterly Releases are planned by POs.
High-level roadmap for the next quarter consists of the the least of features assigned to PO.
Features are created in UXPROD project in jira.
Stories are created in corresponding JIRA projects (each module has a separate JIRA project) and must be linked to a feature in UXPROD project.
PO is responsible for adding stories to the backlog.
Prioritization of backlog must be done by PO.
Backlog grooming are held using https://www.planitpoker.com.
Stories/Bugs are estimated in Story points (no estimations in hours!).
In case Story/Bug cannot be estimated and additional investigation is required, a spike can be added (in a form of story) to investigate before assessing an actual story and taking in to Sprint.
All Folio Teams share Sprints timeline: two-week sprints, Sprint 55 will start on Jan 14.
Usually sprints are closed on Thursday/Friday and started on Friday/Monday.
|Daily Stand-ups||Taking place the same time and place every work day.|
|Sprint Review / Internal Demo|
The meeting is to review the board and understand the amount of spillover, reasons for the stories to be incomplete and to present completed work internally to the team-members and PO.
Sprint Retro is held using https://funretro.io/.
The team is to add cards before the meeting to save time.
Likes and dislikes are discussed during the meeting and Action plan is created.
Action plan is updated on team's confluence page to track progress on completion.
System Demo is a joint demo for all the teams and is organized once per two sprints.
The team and PO should decide whether to present anything on System demo.
Slide deck must be updated to outline major updates for two previous sprints.