Focus on:  Hide Contributions
Login

Ddev

→ Europe/Zurich
2/R-014 (CERN)

2/R-014

CERN

10
Show room on map
BiLD
Zoom Meeting ID
62504856418
Host
Federico Stagni
Useful links
Join via phone
Zoom URL
Hide

# DIRAC Development Meeting (Ddev)

**At CERN**: Federico, Christophe, Chris, Alexandre, Ryun, Andre
**On Zoom**: Andrei, Heloise, Stella, Loris, Natthan, Mazen
**Apologies**: Luisa, Janusz, Jorge

## Product Goals & Roadmaps

- Transition to DiracX:

```mermaid
flowchart LR
    subgraph CWL["CWL"]
        CWL1("CWL submission endpoint")
        CWL2("CWL production system")
        CWL3("Transformation system machinery"):::blocked
        CWL4("Use CWL natively in new matcher"):::blocked
    end

    subgraph Core["Core"]
        CoreTasks("Tasks")
        Core2("RSS")
        Core3("DMS")
    end

    subgraph WMS["WMS"]
        WMS1("Matcher"):::blocked
        WMS2("Pilot authentication")
        WMS3("Pilot submission"):::blocked
    end

    CWL3 --> CWL4
    CoreTasks --> Core2 --> Core3
    CoreTasks --> WMS1
    CoreTasks --> CWL3
    WMS1 --> CWL4
    CoreTasks --> WMS3

    click CoreTasks "https://www.github.com" "This is a tooltip for a link"

    classDef done fill:#B2DFDB,stroke:#00897B,color:black,stroke-width:2px;
    classDef blocked fill:#BBBBBB,stroke:#222222,color:black,stroke-width:2px;

    subgraph Legend
        L2("Completed"):::done
        L1("Ready for work")
        L3("Blocked"):::blocked
    end
```

- CWL integration:
![](https://codimd.web.cern.ch/uploads/upload_190b20d13cb4b3543a96af631ca1967d.png)


## Refinements 

### Needs triage
https://github.com/orgs/DIRACGrid/projects/30/views/7

**Goal: build a shared understanding of the project.**

> DIRAC
- [DictCache issue? (blocked)](https://github.com/DIRACGrid/DIRAC/issues/8472)
- [Gracefully stop pilots](https://github.com/DIRACGrid/DIRAC/issues/8346)
- [Job grouping in HPC with no ext. connectivity](https://github.com/DIRACGrid/DIRAC/issues/8475)
- [Remove Python2 pilot](https://github.com/DIRACGrid/DIRAC/pull/8339)
- [Certification Instance](https://github.com/DIRACGrid/DIRAC/issues/7658)

> DiracOS2
- [handle updates?](https://github.com/DIRACGrid/DIRACOS2/issues/30)
- [Python warnings](https://github.com/DIRACGrid/DIRACOS2/issues/146)

> WebAppDIRAC

> diracx
- [drop boto](https://github.com/DIRACGrid/diracx/issues/712)
- [doctest](https://github.com/DIRACGrid/diracx/issues/141)
- [Stop using UPGRADE_REQUIRED](https://github.com/DIRACGrid/diracx/issues/542)
- [CLI tests](https://github.com/DIRACGrid/diracx/pull/104)
    - oldest PR in diracx. [name=Chris] will ressurect it later.
- [Config mechanism](https://github.com/DIRACGrid/diracx/issues/830)
- [DiracError](https://github.com/DIRACGrid/diracx/issues/576)
- [Integrate MCP Server](https://github.com/DIRACGrid/diracx/issues/827)
- [RSS](https://github.com/DIRACGrid/diracx/issues/790)
    - [RSS phase1](https://github.com/DIRACGrid/diracx/issues/836)

> Pilot

> diracx-charts
- [Move away from bitnami](https://github.com/DIRACGrid/diracx-charts/issues/181)
- [Swap the default values of enabled](https://github.com/DIRACGrid/diracx-charts/issues/166)
- [Release notes](https://github.com/DIRACGrid/diracx-charts/issues/237)
- [Managing secret updates](https://github.com/DIRACGrid/diracx-charts/issues/84)
    - need design?
- [Gateway API](https://github.com/DIRACGrid/diracx-charts/issues/68)
    - still relevant?
- [Find a way to run the demo completely offline](https://github.com/DIRACGrid/diracx-charts/issues/48)
- [Handling hotfixing](https://github.com/DIRACGrid/diracx-charts/issues/37)
    - still relevant? No

> dirac-cwl
- [assigning an output sandbox to a job from the api](https://github.com/DIRACGrid/dirac-cwl/issues/92)
- [dirac-cwl executor tests](https://github.com/DIRACGrid/dirac-cwl/issues/116)

**External deps**
- [Drop boto]: need to be split into smaller issues, and address signurlity issues (add to the gh project)


### [Temporary Section] In progress, predating the new organization

https://github.com/orgs/DIRACGrid/projects/30/views/8

Various people still need to deal with old and staled PRs. We will take them into account in the next sprints. 


### External dependencies

https://github.com/orgs/DIRACGrid/projects/30/views/9

---

[Planning Poker](https://en.wikipedia.org/wiki/Planning_poker)
Story points values (based on Fibo)
- `1pt`: Trivial, very clear (small bug fix, config change)
- `2pts`: Small, well understood (small feature, clear requirements)
- `3pts`: Medium, some unknowns (moderate feature)
- `5pts`: Large, significant complexity (major feature, integration)
- `8pts`: Very large, many unknowns (should probably be split)
- `13+pts`: TOO BIG - must split!
- `?`: not enough knowledge to answer (remember it's ok to ask any questions)

## Sprints

### Planning (Velocity and Planning Poker)

- Backlog: https://github.com/orgs/DIRACGrid/projects/30/views/3
- Current Sprint: https://github.com/orgs/DIRACGrid/projects/30/views/1

![](https://codimd.web.cern.ch/uploads/upload_2d702f34e53c69f183961383ff041a6c.png)


**Average Velocity: 3.07 x FTEs** *Last update: Jan 21st*

#### :warning: Velocity is a planning tool, not a performance target

- Velocity going down is NOT bad
- Velocity going up is NOT always good (might mean over-estimation)
- Velocity varies sprint-to-sprint
- We track it to improve estimation, not to judge people

**What affects velocity:**
- Estimation accuracy (we're still learning)
- Complexity of work

**Our focus:** Delivering value and hitting commitments, not maximizing velocity numbers.

### April 2nd (IN PROGRESS):

#### Target and Context
> Chris & Christophe still working on the foundations (`diracx-tasks`): any progress?
- Clean up existing issues/PRs: [Burning Charts](https://github.com/orgs/DIRACGrid/projects/30/insights?period=3M)
- Start Phase1 of the RSS migration
- Make diracx-web stable

#### Availability

- [name=alexandre] 70%
- [name=natthan] 20%
- [name=luisa] 0%
- [name=loris] 50%
- [name=stella] 40%
- [name=jorge]
- [name=ryan] 30%
- [name=federico] 20% 
- [name=heloise] 40%
- [name=christophe] 0%
- [name=chris] 0%
- [name=janusz] 
- [name=mazen] 10%
- [name=andrei] 20%

_ FTEs * _ = _ story points

Expected Story Points:
Persons:
Expected Velocity:

#### Sprint Planning: 

- Backlog: https://github.com/orgs/DIRACGrid/projects/30/views/3
- Sprint: https://github.com/orgs/DIRACGrid/projects/30/views/1

### March 19th (DONE):

Expected Story Points: 53
Persons: 3.5
Expected Velocity: 16.5 

*18+5 (signurlarity) Story Points / 3.2 people = 7.2 velocity*

Comments:

#### Sprint review: https://github.com/orgs/DIRACGrid/projects/30/views/11

Related to our goals:
- **DIRAC to DiracX transition:**
    - More DiracX documentation
    - DiracX-Web supports input/output sandbox downloading

- **CWL integration:**
    - New JobWrapper can report job status

- **DIRAC maintenance:**
    - More RSS streamlining
    - Automated releases of the dirac CVMFS repo is back


#### Sprint retrospective

*The sprint is a boat :boat: ; we are trying to reach an island (target); identify anchors (what slowed you down), wind (what helped), and rocks ahead (risks for next sprint)*

:warning: **Focus on the process, not people. We're here to improve together! 🚀**

**:anchor: Anchors (what slowed you down)**
- *Example: Unclear requirements on X; Waiting for Y delayed Z; ...*


**:cloud: Wind (what helped)**
- *Example: Good communication in weekly meetings; Quick code reviews; Clear acceptance criteria on user stories; ...*


**🪨 Rocks (risks for next sprint)**
- *Example: Team member K on vacation; Dependency on external API L; Technical debt in M; ...*

---

### Previous Sprints
#### Summary

- March 5th:
  - *19 Story Points / 2.8 people = 6.8 velocity*
  - Comments:
    - Less people available during this sprint, but more realistic expectation, we almost reached the expected velocity!!
    - LHCb AI hackathon: [name=Alexandre] was much less available than expected.
    - Took into account items that were in progress before scrum process (added some SP): resurrecting diracx-web, RSS simplified...

- February 19th:
  - *38 Story Points / 4.4 people = 8.6 velocity*
  - Comments:
    - French holidays
    - [name=Alexandre] was more available than expected, but did not manage to quickly follow all the PRs.
    - A few tasks have been delayed (10 SP): waiting for further discussion on scheduling and diagrams for new LHCb workflows
    - Lot of "unplanned" items: expected as long as we have to deal with the large backlog of old items.

- February 5th:
  - *29 Story Points / 3.1 people = 9.4 velocity*
  - Comments:
    - LHCb-CERN had a computing workshop
    - Various people worked on old PRs I did not take into account :warning:

- January 21st:
  - *6 Story Points / 2.5 people = 2.4 velocity*
  - Comments:
    - LHCb-CERN had a team retreat, LHCb-Spain had a conference.

- January 7th:
  - *15 Story Points / 3.9 people = 3.8 velocity*
  - Comments:
    - No specific comment, the sprint was split by the holidays.

- December 10th:
  - *6 Story Points / 3 people = 2 velocity*
  - Comments:
    - About the same as the previous sprint: still a gap between expected/actual availability

- November 26th:
  - *6 Story Points / 3 people = 2 velocity*
  - Comments:
    - Much lower than the previous sprint because it included tasks started before the sprint.
    - Lots of "almost done" PRs: we are improving the description of the tasks and their size but still not enough (each task should bring value though).

- November 10th:
  - *22 Story Points / 4.3 people = 5.1 velocity*


#### Actionable Results from the Retrospective

- **Action:** Better view of the PRs ready to be reviewed vs needing changes.
  - Owner: developers
  - When: Sprint8
  - Status: 19/02/26 In Progress
- **Action:** Better communicate when a PR is going to be big, as soon as possible. Split the work in this case.
  - Owner: developers
  - When: Sprint6
  - Status: 21/01/26 DONE
- **Action:** Better use of the mattermost channel to get reviews on a given PR
  - Owner: everyone
  - By when: Sprint3
  - Status: 04/02/26 DONE
- **Action:** Define estimates and velocity based on Sprint2's results, taking into account external contributions (bonus Story Points) and availability
  - Owner: alexandre
  - By when: Sprint3
  - Status: DONE
- **Action:** Better define the scrum roles
  - Owner: alexandre
  - By when: Sprint5
  - Status: DONE
- **Action:** Better define `DONE` criteria (what should be included into the PR, and how to make sure we are not introducing too much technical debt)
  - Owner: everyone
  - By when: Sprint2
  - Status: DONE
- **Action:** Avoid planning dependent tasks in a same sprint
  - Owner: everyone
  - By when: Sprint2
  - Status: DONE

## AOB

 

There are minutes attached to this event. Show them.
    • 10:00 → 12:00
      Dirac(X) developers (Ddev): Dirac(X) developers
      Convener: Alexandre Franck Boyer (CERN)