Skip to main content

Agile Development Process

We follow the Agile methodology to deliver high-quality software iteratively. This document outlines our Agile development practices.

Sprint Structure​

  • Sprint Duration: 1-2 weeks, depending on the project scope
  • Sprint Planning: At the beginning of each sprint, the team determines what can be completed during the sprint
  • Daily Standups: Daily 15-minute meetings to discuss progress and blockers
  • Sprint Review: At the end of each sprint to demonstrate completed work to stakeholders
  • Retrospective: After each project to reflect on what went well and what could be improved

Note: Sprint planning and review are usually held at the same time.

Task Management​

We use Plane for task management:

  • All tasks are tracked as issues or tickets
  • Tasks are organized into epics, features, and user stories
  • Each task must have:
    • Clear description
    • Acceptance criteria
    • Estimated effort (in hours)
    • Assigned developer
    • Priority level

Sprint Planning​

  1. Backlog Refinement:

    • The Product Manager and Tech Lead review and prioritize the backlog
    • Stories are broken down into manageable tasks
    • Acceptance criteria are defined

  2. Capacity Planning:

    • Team determines capacity for the sprint
    • Tasks are selected based on priority and team capacity
    • Team members self-assign tasks where appropriate

  3. Sprint Commitment:

    • Team commits to the selected tasks
    • Sprint goal is defined
    • Tasks are moved to the sprint backlog

Daily Standups​

Daily standups are held to keep the team aligned:

  • Format: 15-minute timeboxed meeting
  • Schedule: Every day at a consistent time (usually morning)
  • Questions:
    • What did you accomplish yesterday?
    • What will you work on today?
    • Are there any blockers?
  • Focus: Keep discussions brief; take detailed discussions offline

Sprint Review​

At the end of each sprint, we hold a review session:

  • Demo: Team demonstrates completed work
  • Feedback: Stakeholders provide feedback
  • Acceptance: Product Manager accepts or rejects stories
  • Next Steps: Discussion about what comes next

Sprint Retrospective​

After each project, we reflect on our process:

  • Format: 60-90 minute facilitated discussion
  • Questions:
    • What went well?
    • What could be improved?
    • What actions can we take?
  • Action Items: Create actionable improvements for the next sprint
  • Follow-up: Review previous action items and their impact

Project Tracking Metrics​

We track the following metrics to measure progress:

  • Velocity: Average number of story points completed per sprint
  • Burndown Chart: Visual representation of work remaining
  • Cycle Time: Time from when work begins on a task until it's done
  • Escaped Defects: Number of bugs found after story completion

Roles and Responsibilities​

Product Manager​

  • Maintains and prioritizes the product backlog
  • Ensures user stories have clear acceptance criteria
  • Accepts or rejects completed stories
  • Communicates progress to stakeholders

Tech Lead​

  • Provides technical direction and oversight
  • Helps estimate and break down technical tasks
  • Reviews and approves implementation approaches

Developers​

  • Estimate and implement tasks
  • Participate in sprint planning and standups
  • Conduct peer code reviews
  • Write and maintain tests

QA​

  • Validates stories against acceptance criteria
  • Performs regression testing
  • Reports and tracks bugs

Agile Best Practices​

  • User-Focused: Always consider the end user when developing features
  • Iterative Development: Build incrementally rather than all at once
  • Continuous Feedback: Gather feedback early and often
  • Adaptive Planning: Adjust plans based on what is learned
  • Self-Organization: Team members take ownership of their work
  • Cross-Functional Collaboration: Different roles work together

By following these Agile practices, we ensure that we deliver value to our clients in a predictable, iterative manner while maintaining high quality standards.