-
Notifications
You must be signed in to change notification settings - Fork 4
Home
[glitch] schedule scrum at [cron] in [room name]
-cron Cron expression specifying when to run scrums. -room name The name of the Gitter room where a scrum should be started; should be someting like AleksueiR/CyberTests -glitch The name of hubot
glitch should acknowledge the scrum is scheduled
[glitch] list scrums
-glitch The name of hubot
glitch lists scheduled scrums in the following format
[id] [room name] at [cron] [id] [room name] at [cron] [id] [room name] at [cron]
where -id is a unique id of the scrum used to identify it
[glitch] cancel scrum [id]
-glitch The name of hubot
glitch cancels scrum with the specified -id and acknowledges the cancellation
at the specified time glitch posts to the room:
"""Scrum time! Please provide answers to the following:
- What have you done since yesterday?
- What are you planning to do today?
- Do you have any blocks
- Any tasks to add to the Sprint Backlog? (If applicable)
- Have you learned or decided anything new? (If applicable)"""
glitch starts listening to people talking and collects their posts grouping them by the person; glitch parses posts extracting five lines corresponding to five questions; when a person posted five answers, glitch posts a positive, Dan-like comment (something like "great job", "Awesome, thanks.", etc.); if the person posts answers to fewer than five questions, he doesn't get a thanks response but his answers are still recorded;
if glitch can determine that all people posted all answers (check against the list on people in the room), glitch announces the end of the scrum; if this can't be determined (someone didn't post his response, or someone didn't post all five answers), glitch waits 15 minutes after the last post and announces the end of the scrum;
after glitch ends the scrum, glitch writes scrum log into a file on the ftp share; the format of the file should be similar to how scrumminator does it (daily questions on top, followed by a summary of people responses, followed by a complete log of the scrum)