Tiketit
- Harjoiteltiin tikettien arvottamista.
- Todo: Koha-toimiston pitää siivota käytännössä resolvoidut ja vanhentuneet pois kuleksimasta.
- Ensi kerralla: ainakin uudet arvotetaan.
- Tähtäimessä: top lista = backlog.
- Kohti kokonaisuuksien ratkomista, esim. varastotietueet.
Tilastointi
- Ks. Tilastoselvitys
Jira tickets analysis rehearsal
The formula below.
KOHA-88 - Getting issue details... STATUS
Business Value: 20
Time Criticality: 13
Risk/Opportunity: 13
CoD: 46
KOHA-386 - Getting issue details... STATUS
Business Value: 5
Time Criticality: 13
Risk/Opportunity: 13
CoD= 31
KOHA-176 - Getting issue details... STATUS
Business Value: 13
Time Criticality: 8
Risk/Opportunity: 8
Cod = 29
KOHA-45 - Getting issue details... STATUS
Business Value: 13
Tme Criticality: 8
Rusk/Opportunity: 8
CoD= 29
KOHA-275 - Getting issue details... STATUS
Business Value: 13
Time Criticality: 8
Risk/Opportunity: 8
CoD = 29
KOHA-288 - Getting issue details... STATUS
Business Value: 8
Time Criticality: 5
Risk / Opportunity: 13
CoD = 26
Is this resolved?
KOHA-377 - Getting issue details... STATUS :
Business Value: 8
Time Criticality: 3
Risk/Opp: 13
CoD= 24
KOHA-377 - Getting issue details... STATUS :
Business Value: 8
Time Criticality: 3
Risk/Opp: 13
CoD= 24
KOHA-69 - Getting issue details... STATUS :
Business Value: 5
Time Crit: 3
Risk/opportunity: 5
CoD = 13
KOHA-384 - Getting issue details... STATUS
Business Value: 3
Time Criticality: 1
Risk/opp: 1
CoD = 5
KOHA-91 - Getting issue details... STATUS related toi KOHA-88
KOHA-257 - Getting issue details... STATUS : resolved? Related to KOHA-251
KOHA-265 - Getting issue details... STATUS : Resolved?
KOHA-289 - Getting issue details... STATUS : Resolved?
KOHA-381 - Getting issue details... STATUS : Resolved? At least, instructions sent.
KOHA-245 - Getting issue details... STATUS : Resolved?
KOHA-373 - Getting issue details... STATUS : Resolved?
KOHA-383 - Getting issue details... STATUS : waiting signoff: https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=34281
KOHA-258 - Getting issue details... STATUS : Remove? Seems that no changes requires.
Tasks Management
- Koha Team has looked at
- labels to be used: Jira Labels (Draft)
- workflows (more internal question)
- Thoughts about how Jira contents will be reviewed:
- Review = General outlook, not the technical details of the tickets
- Asiantuntijaryhmä is the proper forum
- Standing item in every meeting
- Weigh the tickets on the Cost of Delay
- CoD =
- Customer Business Value: Is this a shared priority? Is this very useful (saving time, efficient circulation, books don't get lost etc.)? Does this affect customer satisfaction? Are there regulations to comply with?
- Time Criticality: is there a deadline? Is it urgent?
- Risk Reduction or Opportunity Enablement: Does this mitigate risks? Does this enable new ways of using the system?
- Using values 1, 2, 3, 5, 8, 13, 20
- So the CoD varies btw 3 (1+1+1) and 60 (20+20+20)
EXAMPLE
Ticket | Business Value | Time critical | Risk/opportunity | SUM= Cost of Delay |
---|---|---|---|---|
1 | 5 | 8 | 1 | 14 |
2 | 3 | 5 | 3 | 11 |
3 | 1 | 1 | 5 | 7 |
- Koha team will asses the Job size on the same scale, 1, 2, 3, 5, 8, 13, 20,
- We tend up with Weighted Shortest Job First score
- WSJF varies btw 0,15 (3/20) and 60 (60/1)
Ticket | CoD | Duration | WSFJ= CoD/Du | → |
---|---|---|---|---|
1 | 14 | 5 | 2,8 | 3 |
2 | 11 | 3 | 3,67 | 1 |
3 | 7 | 2 | 3,5 | 2 |