Innovative Team Engagement

Example: Automatic Reflection on Velocity

Practices Experience  Github action uses PR characteristics to generate an automatic Team Journal post.

Additional Commits

Number of commits created after PR was opened and before merged. Can be zero or more.

Days to Merge

Number of days from when PR was opened until it was closed, rounded up to the nearest day. Can be 1 or greater.

Code Changed

Number of new lines plus number of lines deleted in the whole PR. Multiple changes to the same line in separate commits should only be counted once. Can be zero or more.

Create a measurable and contextual Team Journal post:

• Define a positive or not desirable scenario based on the combination of  days-to-merge-limit, code-changed-limit, additional-commits-limit
• Specify a positive or negative impact weight to measure the significance of the experience
• Apply team humour for the summary description
• Specify which activity and team this experience relates

What you can do:

• created experience posts can be grouped and automatically pulled into a retrospective conversation board
• explore experiences via interactive infographics
• view overall experiences via dashboards
• identify trends and compare change between periods

name: Create Experience for Nice and Fast PR

on:

 pull_request:

  types:

   - closed

env:

 SIMPLE_EXP_SUMMARY: 'A nice and fast PR experience...'

jobs:

 create-experience-nice-and-fast-pr:

  if: github.event.pull_request.merged == true

  runs-on: ubuntu-latest

  permissions:

   pull-requests: read

  steps:

   - name: Create Experience for nice and fast PR

    uses: neelix-io/practices-experience-action@v1

    with:

     api-token: ${{ secrets.NEELIX_API_TOKEN }}

     consortium-id: ${{ vars.CONSORTIUM_ID }}

     commentary: "A nice and fast PR experience"

     weight: 1

     activity-id: 49

     category-ids: 96,95

     team-ids: 7164

     days-to-merge-limit: 0,1

     additional-commits-limit: 0,2

Example: Automatic Reflection on Sentiment

Simple Net Experience  Github action uses resolved comments to generate an automatic Team Journal post.

Agreed as a team which keywords or phrases within review comments are worthy of capturing as an experience post.

Each trigger can be associated with a positive or negative experience impact weight.

Create a measurable and contextual Team Journal post:

• Define the list of keywords or phrases
• Apply team humour for the summary description
• Specify which activity and team this experience relates

What you can do:

• created experience posts can be grouped and automatically pulled into a retrospective conversation board
• explore experiences via interactive infographics
• view overall experiences via dashboards
• identify trends and compare change between periods

name: Create Experience Something is Fishy

on:

 pull_request:

  types:

   - closed

env:

 SIMPLE_EXP_SUMMARY: 'Something is fishy about this PR...'

jobs:

 create-experience-smth-is-fishy:

  if: github.event.pull_request.merged == true

  runs-on: ubuntu-latest

  permissions:

   pull-requests: read

  steps:

   - name: Create Experience - Something is fishy

    uses: neelix-io/simple-net-experience-action@v1.0.0

    with:

     api-token: ${{ secrets.NEELIX_API_TOKEN }}

     consortium-id: ${{ vars.CONSORTIUM_ID }}

     experience-summary: ${{ env.SIMPLE_EXP_SUMMARY }}

     keywords: 

      {

       "not quite correct": -1,

       "needs improvement": -1,

       "will suffer": -2,

       "fishy": -1,

       "smashed it": 2

      }

     activity-id: 49

     category-ids: 96,30108

     team-ids: 7164