Take It Further Scenarios

Scenario 1

Scrum retrospective to be carried out using Scrums for Group Chat.

Suggested Solution: Implement the feature to trigger a retrospective meeting which will be triggered using a command explicitly or initiated automatically on every sprint end and can be made to work in the following manner

• Users will mark the current sprint start and end dates and assign a scrum master through an adaptive card/task module
• Once the sprint end date is elapsed, on the next working day the bot can initiate the retrospective meeting automatically or explicitly through a command
• The scrum master can capture retrospective details using an adaptive card/task module
• The bot will post the retrospective details in the form of an adaptive card in the group chat

Pros:

• Code extensibility

Cons:

• Dev effort costs

Scenario 2

Extend the bot to be used in a teams scope.

Suggested Solution: The bot code can be changed to enable support in a teams channel instead or in addition to group chats.

Pros:

• Minimal code changes

Scenario 3

Link Scrums for Group Chat with DevOps platform like Azure DevOps, GitHub, Jira, etc.

Suggested Solution: Extend the existing implementation of update scrum further by connecting your DevOps platform. Once the scrum is submitted the records will directly be saved into the DevOps scrum board.

Pros:

• Code extensibility