RuFaS Team SCRUM Process#
Welcome to the RuFaS team’s SCRUM process wiki page. This document outlines the key aspects of our agile development process, including task sizing, priorities, ceremonies, and the Definition of Done (DoD).
Task Sizing#
We use t-shirt sizes to estimate the size of tasks. Each size corresponds to a rough duration in days:
XS: Less than a day.
S: Approximately one day.
M: Around two days.
L: Approximately three days.
XL: About five days.
Epic: Large tasks that need to be broken into smaller sub-tasks.
Task Priorities#
Tasks are categorized based on their priority:
Wishful: Nice-to-have, low-priority tasks.
Low: Lower-priority tasks that can be addressed if resources are available.
Mid: Medium-priority tasks.
High: High-priority tasks that are important for project progress.
Urgent: Critical tasks that need immediate attention.
Sprint Process#
We work in bi-weekly sprints, which include the following ceremonies:
Ceremonies#
Backlog Grooming: Regularly reviewing and refining our task list to ensure it’s up-to-date and prioritized.
Sprint Planning: Determining which tasks will be tackled during the upcoming sprint.
Sprint Retrospective: Reflecting on the sprint’s performance and identifying areas for improvement.
Definition of Done (DoD)#
For a task to be considered complete, it should meet the following criteria:
PR Review: A Pull Request must be reviewed by the relevant individuals, including the development team and SMEs.
Merged to Main: The PR should be successfully merged into the main branch.
Documentation (if applicable): If a task requires documentation, it should be provided and meet the necessary standards.
Continuous Improvement#
We encourage open communication, collaboration, and a commitment to continuous improvement. Regularly review and adapt our processes based on team experiences and feedback.
Tools and Automation#
We make use of project management and collaboration tools to streamline our SCRUM processes, ensuring better visibility and efficiency. TBD