Agile/Scrum Way of work - Framework Thinking

1. Daily Routine in an Agile Scrum Team

Meeting at start, mid, end of the day.

1.1. Morning — Daily Stand-up

Format (each member answers 3 questions):

  1. What did I do yesterday?
  2. What will I do today?
  3. Are there any blockers?

1.2. Focus Work — Coding, Reviewing, Testing

  • Coding: Work on stories/tasks assigned in the sprint backlog (from Jira).
    • Implement features, fix bugs, or improve performance.
    • Follow coding standards and write unit tests.
  • Code Reviews:
    • Review pull requests from teammates for quality, style, and logic.
    • Give feedback and approve when ready.
  • Collaboration:
    • Pair programming or discuss solutions with the team.
    • Communicate with QA, DevOps, or Product Owner when needed.

1.3. Midday — Collaboration and Refinement

  • Backlog Refinement / Grooming (once or twice a week):
    • Review upcoming stories with Product Owner.
    • Clarify requirements, estimate effort (story points), and split large tasks.
  • Design Discussion:
    • Discuss architecture, data models, or API design with other engineers.
  • Testing & QA:
    • Deploy to test environments, verify functionality with QA.

1.4. Afternoon — Focus & Delivery

  • Continue development or integration tasks.
  • Fix issues found during QA or testing.
  • Update task progress in the sprint board.

1.5. End of Day — Sync and Documentation

  • Update Jira tickets or Scrum board status (e.g., In Progress → Code Review → Done).
  • Commit and push code changes.
  • Document technical notes, API changes, or troubleshooting steps in Confluence or README files.

2. Rule of works

  • Step 1: Requirements and Timelines (Only when communicate with clients or business)

  • Step 2: Design and dive deep, analyze and find out multiple solutions, analyze bugs.

  • Step 3: Implement

  • Step 4: Deployment

  • Step 5: Feedback loop.

Last Updated On November 2, 2025