End-to-End Flow from Teams Group Chat to Roadmap

This guide walks you through an integrated workflow that begins in Microsoft Teams and ends in a fully generated Roadmap in Cortex. The process captures both current and historical conversations (processed once the required consents are granted), converts them into a functional specification, exports to SharePoint, and produces a roadmap linked to Jira.

Step 1: Start with Teams Group Chat

Use Teams to initiate the conversation from which your spec will be derived. In addition to live conversations, you can allow the bot to process historical chats — past conversations in Teams — to ensure that prior decisions, context, and requirements are also captured. This provides continuity and prevents information gaps in the generated roadmap.

How to do it: (For SaaS)

1. Create a Teams meeting and add participants.
2. Add the Teams bot to the meeting:
   1. Click the “+” (Add App) icon.
   2. Search for xnode Meeting Bot and add it to the chat.
   3. Grant all required consents.
3. Start a relevant conversation on your topic.
4. After a few exchanges, check if the conversation syncs with cortx.

How to do it: (For Enterprises)

1. Create a Teams meeting and add participants.
2. Add the Teams bot to the meeting:
   1. Click the “+” (Add App) icon.
   2. Click on Manage Apps
   3. Upload the bot ZIP file manually from the device.
   4. Grant all required consents.
3. Start a relevant conversation on your topic.
4. After a few exchanges, check if the conversation syncs with cortx.

Step 2: Create a Functional Spec Template

Use this step to prepare a reusable template for your spec.
How to do it:

1. Go to the Templates section in cortx.
2. Click New Template.
3. Select Specification as the template type.
4. Fill in the required details:
   • Title
   • Description (what the spec should cover)
5. Click Generate to create the template.
6. Locate the template in My Templates > Drafts.
7. Click Preview, then Edit the template.
8. Add agents as needed. Use Tasks and Threads to generate structure.
9. Click Save and then Publish the template.
10. The published template will now appear in My Templates for future use.

Step 3: Generate the Specification

Convert your synced conversation into a structured specification document.
How to do it:

1. Ensure the Teams conversation is reflected in cortx.
2. Trigger Conversation Summary to clean up the context.
3. User can generate content by either
   • Clicking on ‘Generate Content’ button from the three-dot menu on top right corner
   • Clicking on the ‘Generate Spec’ icon beside agent tray on the text editor.
4. In the panel:
   1. Go to My Templates.
   2. Select your functional spec template.
   3. Click Generate.
5. Review the generated spec:
   1. Ensure all sections are present.
   2. Remove any irrelevant data.

Step 4: Export to SharePoint and Enable Sync

Push your finalized spec to SharePoint and activate bidirectional sync.

How to do it:

1. Confirm your SharePoint integration is active in cortx.
2. Click on the Export icon on the top right corner beside share button
3. Select Export to SharePoint.
4. Once export completes:
   • Use the three-dot menu to select Open with SharePoint.
   • Review the document in SharePoint.

Enable Bidirectional Sync:

1. Make changes in cortx → Click the Export to SharePoint banner to push updates.
2. Make changes in SharePoint → A banner in cortx will prompt Update Spec → Click to sync changes back into cortx.

Step 5: Generate the Roadmap

Transform your finalized spec into a structured roadmap within cortx.
How to do it:

1. Ensure that your project management tool (JIRA/ADO) is already integrated with Cortx in the Integrations section.
2. Go to the Roadmap module.
3. Click Generate Roadmap.
4. In the panel:
   1. Enter Title
   2. Choose the project management tool/software, or Select ‘Other’ if there is no tool/software integrated.
   3. Select Organization
   4. Select target project.
   5. Click Generate.
5. Upon success:
   1. Review the roadmap.
   2. Verify Epics, Features, and User Stories are:
      • Created properly.
      • Linked to each other.
      • Aligned with your original spec.