Process - FEUP-MEIC-DS-2024-25/ai4sd GitHub Wiki

The process adopted for the AI4SD project is based on the Scrum framework and LeSS Huge, to cope with the 33 teams.

You can find below details about some of the key activities.

Sprint Planning

Define the sprint goal and what PBIs will be considered for the sprint, based on past velocity, and assign them to specific teams. See the Sprint Planning pattern, and the descriptions of Sprint Planning One and Sprint Planning Two as established by LeSS.

Sprint Planning One

Product Backlog was previously ordered by the Area PO's and then by the Chief PO. Teams move PBIs from the Product Backlog to their own Sprint Backlog, tagging them.

Sprint Planning Two

A realistic Sprint Backlog is defined according to past and expected velocity. Sprint Backlog doesn't contain epics, only work items and stories.

Sprint(ing)

Sprint Backlog items are assigned to team member(s) when started (and not before!). Work in progress (WiP) is kept low (team avoids "paused" work).

Backlog Refinement

Discuss, estimate, break down, specify as much as needed, and order PBIs (especially those near the top of the backlog) throughout the ongoing sprint. POs should schedule meetings with Clients (teachers and others) to gain a deeper understanding of the product needs (go into these meetings well prepared, and make the best of the available time). POs and Developers should work together to refine the backlog. See the Definition of Ready and the Refined Product Backlog patterns.

Product Increment

Increment clearly adds value to the end-users. Increment description exists and mentions closed PBIs (CHANGELOG.md), PBIs that reached the status of "Done Done Done", satisfying all the conditions of the Definition of Done (DoD). Increment is appropriately tagged in version control. Increment has been delivered to servers and they are accessible. Undelivered items are incorporated again into the Product Backlog.

Sprint Review

In the end of each sprint do a demonstration of the product increment to the POs and Client. Use small animated GIFs or videos to record the new functionalities. Feedback provided is recorded in the PBL as updates of existing PBIs or eventually created new PBIs. As many members of the team as possible should attend the reviews. See the Sprint Review pattern.

Team Retrospective

See the Sprint Retrospective pattern.

Overall Retrospective

See the Overall Retrospective as described by LeSS.