Release KAKI - A release/signonff Audit Tracker BOT

About

In an agile scenario, Release Management is a pain where multiple parties are involved including Dev, BAs and End-Users.
Here is a small illustration of the events which take place on usual iteration/sprint.

graph TB
    D[Dev Group] -- Sends email that build is ready --> B((Users))
    B -- Test all scenarios without any status --> B
    B((Users)) -- Send Signoff email --> D
    D -- Attaches signoff for Production push --> D

Loading

Issues with the above model :

• Dev and BA's are working in Silos.
• No visibility of the state of the email sent.
• Release work often gets in the middle of sprint work and developers have to own the whole process.
• No single point of tracking mechanism.
• Need to dig through the email to figure out whole process.

Solution workflowEntity

graph TB
    Developer[Dev Group] -- Posts message --> B((Chatbot))
    B((Chatbot)) -- Creates action items --> App[App Service]
    App((App Service)) -- Notifies users --> E[End Users]
    E[End Users] -- Signoff message --> B((Chatbot))

Loading

 graph LR
        od>In-app Bot] -.-> Chatbot engine
        di{Diamond with <br/> line break} -.-> ro(Rounded<br>square<br>shape)
        di==>ro2(Rounded square shape)
 end

Loading

Main Components

1. Workflow API - To track user conversation states [Answered, Unanswered, Error, In progress] allowing it to locate users based on their streamId.
2. Audit API - To log & query the incoming data to a persistent store
3. Lang API - API to support NLP semantics and conversation
4. Service API - Listener & Responder for incoming chats to the bot.

graph LR
    Client --> Service[Service API]
    Service -- Logs + queries --> Lang[Lang API]
    Lang    -- User Intent --> Service
    Service -- Logs --> Audit[Audit API]
    Service -- Update conversation state --> Workflow[Workflow API]
    Workflow -- Next state --> Service
    Service --> Client

Loading