Software Engineering Practices Insights
via Github Actions
Automated capture of net experience and behavioural traits
Github actions that capture sentiment and experience behind each merged pull request
Automated capture of joint sentiment behind each pull request
Always-ready retrospective conversation
boards
Holistic picture of team's experiences
Always-on infographics for introspection, communicating out and storytelling
A better way to self-reflect and grow together as a team
Sentiment of PR Reviews
Create automatic, measurable and contextual team journal posts based on keywords mentioned in PR comments.
Sentiment of Practices
Create automatic, measurable and contextual team journal posts based on PR characteristics - size, time taken to merge, number of commits.
Real Conversations
Adopt a holistic and reflective approach to team conversations with Team Journal and auto-populated retrospective boards.
Innovative Team Engagement
Build a great team culture with conversations that focus on joint work and experiences.
Give data its own voice:
- Easy to use Team analytics
- Retrospective boards that can be auto-populated from data points captured in Team Journal (Github actions and feedback posted by team members)
- Live Pulse feedback pushed directly from Slack or MS Teams
Build Great Team Culture
Innovate and Reduce Ritualism
Embracing the true spirit of the Agile mindset entails transcending boring ritualism that can hinder progress. Merely adhering to rituals for their own sake can impede a team's growth. Neelix.IO platforms fosters innovation by enhancing the effectiveness of collaborative discussions within teams.
Humour assisted, measurable and contextual reflections aggregated by Neelix.IO empower teams to break through barriers and address challenging conversations constructively.
Core resons for reflective experience sharing is the creationf of a conducive environment for open dialogue and problem-solving. This approach not only promotes transparency and trust but also leads to a more cohesive and effective team dynamic, ultimately driving progress and improvement.
Examples of how Neelix.IO disrupts ritualism:
- If you prefer having a retrspective board for team conversations, then cards can be automatically created based on the ongoing experience data points
- If retrospective board is not your thing, then an interactive infographic of ongoing experience data points (with links to PRs) can facilitate a great evidence-based and humoiur assisted conversation
Get started:
- Create a confidential journal for your team on Neelix.IO platform
- Add Github actions to your workflow for capturing autogenerated reflections on sentiment as part of PR reviews, or implied from PR characteristics
- Empower team member to push their own feedback directly from Slack or MS Teams
Reflect on What Matters
Create rails for smart transparency in your team by leverage internal humour and capturing reflective data points on specific context.
Configure any context categories that matter to internal team conversations:
- Experiences related to long lived PRs
- Themes related to velocity
- Technical debt
- Team experience
- etc.
Capture measurable posts in Team Journal that speak to a joint team experience and effectiveness of joint output.
Retrospectives Without Ritualism
Boost effectiveness of retrospectives with feedback entries auto-created by Neelix on the basis of team journal posts.
All retrospective events are subject to three key challenges:
- people tend to mutate memories of emotions, and even facts
- people get tired of rituals
- allocated time is always limited
Humour assisted data points help authentic conversations that focus on joint experiences.
Team Analytics
Neelix Feedback Platform aggregates measurable real-time feedback and provides insights into Culture, Alignment and many other factors. Neelix uses human-centric approach - insights are built from data points "pushed" on the back of real experiences.
Self-Aware and Teachable Culture
Self-aware teams do significantly better. Revolutionize the approach to culture with organizational and team level self-awareness powered by contextual and measurable Live Pulse feedback model.
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
Build Culture of
Systems Thinking and
Smart Transparency
ONE TEAM. ONE DIRECTION.
