[yast-devel] Planning the Next Sprint (#12)
Guys, As you can see in Trello, I'm currently planning new sprint (planning meeting will be tomorrow for both sub-teams). This time, the focus should be "The future of SLE 12 (SP2 + Leap 42.2) & Critical SLE issues (SP1-P1s and Maintenance updates)". Team A ====== - In general, I wanted to continue with the trend set by Jiri before he left for his vacation, just check the current Sprint Backlog Team 1 ====== - The team has some PBIs under waterline in the current backlog, but I believe you can make all of them and then there are some new interesting PBIs the Incoming Board. For both teams ============== - This time, I'd like to focus more on development (with refactoring) than on fixing P1s - we do not have that many P1s now anyway - I would like you all to check the current queue (first the current backlog, then the planned one) and think about it: Is this what will bring the best value for customers/us? Isn't there anything more important? Considering what we know now, is it important at all? - Please, suggest shifting priorities, adding important stuff that has been left out of planning, or suggest removal of items if you believe they are unimportant (now). Always provide explanation "why". Thanks in advance Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 11/10/2015 09:45 AM, Lukas Ocilka wrote:
Guys,
As you can see in Trello, I'm currently planning new sprint (planning meeting will be tomorrow for both sub-teams). This time, the focus should be "The future of SLE 12 (SP2 + Leap 42.2) & Critical SLE issues (SP1-P1s and Maintenance updates)".
Team A ====== - In general, I wanted to continue with the trend set by Jiri before he left for his vacation, just check the current Sprint Backlog
Team 1 ====== - The team has some PBIs under waterline in the current backlog, but I believe you can make all of them and then there are some new interesting PBIs the Incoming Board.
For both teams ============== - This time, I'd like to focus more on development (with refactoring) than on fixing P1s - we do not have that many P1s now anyway
Not many P1s, but we have 90 bugs assigned to yast-internal (i.e. expected to enter some sprint at some point). If that amount continues increasing it's going to be hard to keep the overview.
- I would like you all to check the current queue (first the current backlog, then the planned one) and think about it: Is this what will bring the best value for customers/us? Isn't there anything more important? Considering what we know now, is it important at all?
Directly related to the paragraph before. With 90 bugs don't expect your PO to catch all the important ones. So highlight those you care about. Then it will be PO decision if they are more important than new development or refactoring.
- Please, suggest shifting priorities, adding important stuff that has been left out of planning, or suggest removal of items if you believe they are unimportant (now). Always provide explanation "why".
Thanks in advance Lukas
Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 11/10/2015 10:11 AM, Ancor Gonzalez Sosa wrote:
Not many P1s, but we have 90 bugs assigned to yast-internal (i.e. expected to enter some sprint at some point). If that amount continues increasing it's going to be hard to keep the overview.
Regarding this, we probably need to introduce some checks to verify that: a) All bugs assigned to yast-internal have a card in Trello. Otherwise, they will simply rot since nobody will look at them. b) Bugs referenced in the incoming board are not already resolved. To reduce noise in Trello (it's already quite a big board). Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
On 11.11.2015 09:24, Ancor Gonzalez Sosa wrote:
On 11/10/2015 10:11 AM, Ancor Gonzalez Sosa wrote:
Not many P1s, but we have 90 bugs assigned to yast-internal (i.e. expected to enter some sprint at some point). If that amount continues increasing it's going to be hard to keep the overview.
Regarding this, we probably need to introduce some checks to verify that:
a) All bugs assigned to yast-internal have a card in Trello. Otherwise, they will simply rot since nobody will look at them.
b) Bugs referenced in the incoming board are not already resolved. To reduce noise in Trello (it's already quite a big board).
Yes, and additionally the PO will need the team help to set priorities for these bugs. - Some bugs might be more important than they seem: Changing bug summary should help with that - Some bugs have misleading summary: Again, changing bug summary from "A is broken" to "Do B to fix A" or similar might help - Some bugs are not that important actually, and they are just hiding there - Some bugs are hidden features Thx Lukas -- Lukas Ocilka, Systems Management (Yast) Team Leader SLE Department, SUSE Linux -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
Dne 11.11.2015 v 09:24 Ancor Gonzalez Sosa napsal(a):
On 11/10/2015 10:11 AM, Ancor Gonzalez Sosa wrote:
Not many P1s, but we have 90 bugs assigned to yast-internal (i.e. expected to enter some sprint at some point). If that amount continues increasing it's going to be hard to keep the overview.
Regarding this, we probably need to introduce some checks to verify that:
a) All bugs assigned to yast-internal have a card in Trello. Otherwise, they will simply rot since nobody will look at them.
b) Bugs referenced in the incoming board are not already resolved. To reduce noise in Trello (it's already quite a big board).
I have checked https://github.com/mvidner/ytrello and I'm adding some synchronization script which would report (and optionally fix) such issues. The initial version found 79 bugs assigned to "yast-internal@suse.de" which URL attribute does not link to Trello. Now I'm adding the reverse check to find missing Trello cards and already closed bugs. Stay tuned... -- Best Regards Ladislav Slezák Yast Developer ------------------------------------------------------------------------ SUSE LINUX, s.r.o. e-mail: lslezak@suse.cz Lihovarská 1060/12 tel: +420 284 028 960 190 00 Prague 9 fax: +420 284 028 951 Czech Republic http://www.suse.cz/ -- To unsubscribe, e-mail: yast-devel+unsubscribe@opensuse.org To contact the owner, e-mail: yast-devel+owner@opensuse.org
participants (3)
-
Ancor Gonzalez Sosa
-
Ladislav Slezak
-
Lukas Ocilka