Skip to content

Latest commit

 

History

History
53 lines (36 loc) · 2.42 KB

standuplyReports.md

File metadata and controls

53 lines (36 loc) · 2.42 KB

Dixi Reports

Here at Expertizo, we utilize a service called Geekbot. Geekbot is a program that runs stand-up meetings in text format in Slack. It helps our distributed teams organize and run stand-ups no matter the distance.

These reports provide critical information and updates from engineers that helps better improve engineering's context for overall work and progress throughout the GitHub organization.

There are two Geekbot Reports.

  1. "Standup Beta": This prompts at 6 PM daily on working days.
  2. "Weekly Progress": This prompts at 11 AM weekly on Monday.

Standup Beta:

Following template to follow is must:

Q1) What tasks you completed today?

  1. “Fixed the scroll bug on Contact Us Page”
    I’ve integrated a new package (react-scroll) to fix this.
  2. “Fixed forgot password API”

Q2) Anything remaining from the above described tasks?

  1. “Fixed forgot password API”
    Testing it with different edge cases is remaining.

Weekly Progress:

Following template to follow is must:

Q1) What was your last week's progress?

Week: 29th Jan 2024 - 9th Feb 2024

  1. Fixed Patient Interactions as client said to focus on it first (This should be linked with the project management tool)
    Est. Hours: 5
    Spent Hours: 8
    Reason for exceeding hours: I didn’t plan properly. After looking into the code, it took me time to debug the bug.

  2. Reviewed someone’s code (This should be linked with Github’s PR or Slack’s conversation)
    Est. Hours: 2
    Spent Hours: 2
    Reason for exceeding hours: Not applicable …

Q2) What's your plan for this week?

  1. I will Patient Interactions as client said to focus on it first (This should be linked with the project management tool)
    Est. Hours: 15
    Optional Info: It should be completed around 10 hrs but 15 hrs are just for any unforeseen issue.

  2. I will review someone’s code (This should be linked with Github’s PR or Slack’s conversation)
    Est. Hours: 10
    Optional Info: Not required