Moving tech debt grooming calls to Slack


(Sebastian Brudziński) #1

Hello everyone,

  following up our last technical committee call, I wanted to share and open up for a discussion an idea to move tech debt backlog grooming calls entirely to Slack. Here's the summary of the idea:

  1. We continue to use Slack's #tech-debt channel to allow anyone to suggest new tickets marked "Tech Debt" for consideration

  2. One ticket is allowed per one message

  3. The developers on the #tech-debt channel vote on the tickets, using :+1: emojis

  4. If the ticket reaches defined threshold (how about starting with 4?) it gets added to the Tech Debt Next

  5. The tickets are estimated on the #tech-debt channel using the number emojis

  6. In case of a big variety in estimates or questions, we use Slack's thread on the message listing the ticket to discuss it further and come to a conclusion

  7. We appoint someone as a Tech Debt Guard (TDG) to make sure that each Sprint enough tickets are added and that Tech Debt Next contains enough tickets to pull to the sprints; The TDG notifies the #tech-debt channel if there's deficiency in suggested or approved tickets or lack of estimations, so developers can suggest new tickets, review proposed ones or estimate

  8. The TDG is also responsible for setting the estimates and adding the ticket to the Tech Debt Next after it reaches threshold

  If we are fine with this idea, I'll also create a wiki page outlining the process.

  What do you think? Do you see any potential problems with the proposed workflow?

Best regards,

  Sebastian.
···


Sebastian Brudziński

    Technical Leader

sbrudzinski@soldevelo.com

SolDevelo
Sp. z o.o. [LLC] / www.soldevelo.com
Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland
Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41


(Mary Jo Kochendorfer) #2

I look forward to seeing how this process works. The only thing I wanted to flag, which I’m sure y’all considered, is that since we use the free version of slack we cannot reference historical messages. My question would be around how long does the voting period last (or need to be referenced) because if it is too long it would be in risk of being inaccessible.

Thanks,

Mary Jo

···

From: OpenLMIS Dev openlmis-dev@googlegroups.com on behalf of Sebastian Brudziński sbrudzinski@soldevelo.com

Date: Wednesday, July 11, 2018 at 8:32 AM

To: OpenLMIS Dev openlmis-dev@googlegroups.com

Subject: [openlmis-dev] Moving tech debt grooming calls to Slack

Hello everyone,

following up our last technical committee call, I wanted to share and open up for a discussion an idea to move tech debt backlog grooming calls entirely to Slack. Here’s the summary of the idea:

  1. We continue to use Slack’s #tech-debt channel to allow anyone to suggest new tickets marked “Tech Debt” for consideration

  2. One ticket is allowed per one message

  3. The developers on the #tech-debt channel vote on the tickets, using :+1: emojis

  4. If the ticket reaches defined threshold (how about starting with 4?) it gets added to the Tech Debt Next

  5. The tickets are estimated on the #tech-debt channel using the number emojis

  6. In case of a big variety in estimates or questions, we use Slack’s thread on the message listing the ticket to discuss it further and come to a conclusion

  7. We appoint someone as a Tech Debt Guard (TDG) to make sure that each Sprint enough tickets are added and that Tech Debt Next contains enough tickets to pull to the sprints; The TDG notifies the #tech-debt channel if there’s deficiency in suggested or approved tickets or lack of estimations, so developers can suggest new tickets, review proposed ones or estimate

  8. The TDG is also responsible for setting the estimates and adding the ticket to the Tech Debt Next after it reaches threshold

If we are fine with this idea, I’ll also create a wiki page outlining the process.

What do you think? Do you see any potential problems with the proposed workflow?

Best regards,

Sebastian.

Sebastian Brudziński

Technical Leader

sbrudzinski@soldevelo.com

**

SolDevelo** Sp. z o.o. [LLC] /
www.soldevelo.com

Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland

Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41

You received this message because you are subscribed to the Google Groups “OpenLMIS Dev” group.

To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.

To post to this group, send email to
openlmis-dev@googlegroups.com.

To view this discussion on the web visit
https://groups.google.com/d/msgid/openlmis-dev/c67250b4-d336-842e-5e4a-533e80f321b4%40soldevelo.com
.

For more options, visit https://groups.google.com/d/optout.


(Sebastian Brudziński) #3

We currently have about 3-4 weeks of most recent messages available on Slack. The processing of a single ticket shouldn’t likely take more than a single sprint. In case a ticket hasn’t gotten enough attention (votes) for the 3 weeks, I think it would be safe to assume we don’t want to focus on fixing that particular tech debt ticket right now. It can however always be raised for consideration again though.

Best regards,

  Sebastian.
···

On 11.07.2018 18:20, Mary Jo Kochendorfer wrote:

      I look forward to seeing how this process works. The only thing I wanted to flag, which I’m sure y’all considered, is that since we use the free version of slack we cannot reference historical messages. My question would be around how long does the voting period last (or need to be referenced) because if it is too long it would be in risk of being inaccessible.

Thanks,

Mary Jo

From: OpenLMIS Dev on behalf of Sebastian Brudziński Wednesday, July 11, 2018 at 8:32 AM OpenLMIS Dev [openlmis-dev] Moving tech debt grooming calls to Slack

Hello everyone,

      following up our last technical committee call, I wanted to share and open up for a discussion an idea to move tech debt backlog grooming calls entirely to Slack. Here's the summary of the idea:
      1. We continue to use Slack's #tech-debt channel to allow anyone to suggest new tickets marked "Tech Debt" for consideration

      2. One ticket is allowed per one message

      3. The developers on the #tech-debt channel vote on the tickets, using :+1: emojis

      4. If the ticket reaches defined threshold (how about starting with 4?) it gets added to the Tech Debt Next

      5. The tickets are estimated on the #tech-debt channel using the number emojis

      6. In case of a big variety in estimates or questions, we use Slack's thread on the message listing the ticket to discuss it further and come to a conclusion

      7. We appoint someone as a Tech Debt Guard (TDG) to make sure that each Sprint enough tickets are added and that Tech Debt Next contains enough tickets to pull to the sprints; The TDG notifies the #tech-debt channel if there's deficiency in suggested or approved tickets or lack of estimations, so developers can suggest new tickets, review proposed ones or estimate

      8. The TDG is also responsible for setting the estimates and adding the ticket to the Tech Debt Next after it reaches threshold
      If we are fine with this idea, I'll also create a wiki page outlining the process.
      What do you think? Do you see any potential problems with the proposed workflow?

Best regards,

      Sebastian.

Sebastian Brudziński

          Technical Leader

          sbrudzinski@soldevelo.com
      **

          SolDevelo** Sp. z o.o. [LLC] / [
          www.soldevelo.com](http://www.soldevelo.com)

        Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland

        Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41

      You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.

      To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.

      To post to this group, send email to
        openlmis-dev@googlegroups.com.

      To view this discussion on the web visit [https://groups.google.com/d/msgid/openlmis-dev/c67250b4-d336-842e-5e4a-533e80f321b4%40soldevelo.com](https://groups.google.com/d/msgid/openlmis-dev/c67250b4-d336-842e-5e4a-533e80f321b4%40soldevelo.com?utm_medium=email&utm_source=footer).

      For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).


Sebastian Brudziński

    Technical Leader


SolDevelo
Sp. z o.o. [LLC] / www.soldevelo.com
Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland
Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41
openlmis-dev@googlegroups.comsbrudzinski@soldevelo.com
Date:
To: openlmis-dev@googlegroups.com
Subject:

sbrudzinski@soldevelo.com


(Sebastian Brudziński) #4

Hello everyone,

  as there were no objections, I've summarized our tech debt review process on the Confluence: and intend to start using the new workflow this week. I've also linked this doc on the Slack's #tech-debt channel for easy access.

  The doc also contains a summary from Josh's post to the dev group about the TechDebt Next sprint, creating tickets, etc. as I don't think this was documented anywhere.

  Please let me know if you have any questions about the new process here or via comments on the wiki page. We will of course evaluate how it is working for us on the retrospectives and/or technical committee call.

Best regards,

  Sebastian.
···

https://openlmis.atlassian.net/wiki/spaces/OP/pages/416514111/Technical+Debt+Review+Process
On 12.07.2018 09:24, Sebastian Brudziński wrote:

    We currently have about 3-4 weeks of most recent messages available on Slack. The processing of a single ticket shouldn't likely take more than a single sprint. In case a ticket hasn't gotten enough attention (votes) for the 3 weeks, I think it would be safe to assume we don't want to focus on fixing that particular tech debt ticket right now. It can however always be raised for consideration again though.

Best regards,

    Sebastian.


Sebastian Brudziński

    Technical Leader


SolDevelo
Sp. z o.o. [LLC] / www.soldevelo.com
Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland
Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41
On 11.07.2018 18:20, Mary Jo Kochendorfer wrote:

        I look forward to seeing how this process works. The only thing I wanted to flag, which I’m sure y’all considered, is that since we use the free version of slack we cannot reference historical messages. My question would be around how long does the voting period last (or need to be referenced) because if it is too long it would be in risk of being inaccessible.

Thanks,

Mary Jo

From: OpenLMIS Dev on behalf of Sebastian Brudziński Wednesday, July 11, 2018 at 8:32 AM OpenLMIS Dev [openlmis-dev] Moving tech debt grooming calls to Slack

Hello everyone,

        following up our last technical committee call, I wanted to share and open up for a discussion an idea to move tech debt backlog grooming calls entirely to Slack. Here's the summary of the idea:
        1. We continue to use Slack's #tech-debt channel to allow anyone to suggest new tickets marked "Tech Debt" for consideration

        2. One ticket is allowed per one message

        3. The developers on the #tech-debt channel vote on the tickets, using :+1: emojis

        4. If the ticket reaches defined threshold (how about starting with 4?) it gets added to the Tech Debt Next

        5. The tickets are estimated on the #tech-debt channel using the number emojis

        6. In case of a big variety in estimates or questions, we use Slack's thread on the message listing the ticket to discuss it further and come to a conclusion

        7. We appoint someone as a Tech Debt Guard (TDG) to make sure that each Sprint enough tickets are added and that Tech Debt Next contains enough tickets to pull to the sprints; The TDG notifies the #tech-debt channel if there's deficiency in suggested or approved tickets or lack of estimations, so developers can suggest new tickets, review proposed ones or estimate

        8. The TDG is also responsible for setting the estimates and adding the ticket to the Tech Debt Next after it reaches threshold
        If we are fine with this idea, I'll also create a wiki page outlining the process.
        What do you think? Do you see any potential problems with the proposed workflow?

Best regards,

        Sebastian.

Sebastian Brudziński

            Technical Leader

            sbrudzinski@soldevelo.com
        **

            SolDevelo** Sp. z o.o. [LLC] / [
            www.soldevelo.com](http://www.soldevelo.com)

          Al. Zwycięstwa 96/98, 81-451, Gdynia, Poland

          Phone: +48 58 782 45 40 / Fax: +48 58 782 45 41

        You received this message because you are subscribed to the Google Groups "OpenLMIS Dev" group.

        To unsubscribe from this group and stop receiving emails from it, send an email to openlmis-dev+unsubscribe@googlegroups.com.

        To post to this group, send email to
          openlmis-dev@googlegroups.com.

        To view this discussion on the web visit [https://groups.google.com/d/msgid/openlmis-dev/c67250b4-d336-842e-5e4a-533e80f321b4%40soldevelo.com](https://groups.google.com/d/msgid/openlmis-dev/c67250b4-d336-842e-5e4a-533e80f321b4%40soldevelo.com?utm_medium=email&utm_source=footer).

        For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

openlmis-dev@googlegroups.comsbrudzinski@soldevelo.com
Date:
To: openlmis-dev@googlegroups.com
Subject:


Sebastian Brudziński

      Technical Leader

sbrudzinski@soldevelo.comsbrudzinski@soldevelo.com