ExtraaEdge Techbook
  • Welcome to ExtraaEdge
  • Onboarding
    • Introduction to ExtraaEdge
  • Tech Architecture
    • Product Tech Architecture
  • Product Delivery & Sprints
    • Sprint Planning & Delivery
    • Git Flow
  • Coding Guide
    • React - Frontend
      • Syntax Standards
      • Project Structure & Standards
      • Functional Standards
      • Code Review Checklist
      • UI/UX Standards
      • Things Not to Do
    • .NET - Backend
    • Android - Mobile
Powered by GitBook
On this page
  • Overall Process
  • Pre-Sprint Start
  • Post-Sprint Start
  • Notes
  • Important Links

Was this helpful?

  1. Product Delivery & Sprints

Sprint Planning & Delivery

At ExtraaEdge we believe in Develop Fast Ship Faster keeping this in mind we always strive to deliver quality and timely updates/release to our customers.

Both Tech & QA team are committed to adhere the timelines and build quality product. We follow Agile methodology and keep updating the product in every sprint.

Overall Process

Pre-Sprint Start

  1. Product Owner & Business team decides on a product roadmap for at least 2 months.

  2. Usually we follow a 2-3 week of a sprint.

  3. Based on the priority and criticality of the features/tasks a set of tasks is decided.

  4. The user-stories are added into the JIRA tool, with the detailed specifications.

  5. Sometimes if the spec is large to fit on JIRA story, we create a DropBox Paper Doc and attach to the story.

  6. Based on the user story and the spec, Dev Team & QA Team starts understanding the spec.

  7. If any concerns/queries are raised in the spec are resolved by the Product Owner.

  8. Once the understanding is complete, an estimate is required from Developer & the QA in days/story estimate.

  9. All the estimates are added on the JIRA board, additionally Dev team gives date estimates for all the tasks delivery.

  10. Based on both the dates, final release date is planned and given to the business team.

Post-Sprint Start

  1. Sprint is marked as started on the JIRA board

  2. Respective developers and QA start working on the assigned tasks

  3. QA to provide Smoke Test Suite for each task in the sprint.

  4. It is required to update the status of the tasks whenever updates are made on the corresponding task.

  5. QA to provide Smoke Test Suite for each task in the sp

  6. Once a developer has complete the task, it is handed over for code review.

  7. Developer needs to run the Smoke Test Suite

  8. After code review is done Release Manager deploys multiple task on the test server.

  9. Respective developer assigns the task to QA & updates the status as Released to QA

  10. Developer needs to update the QA team about the deployment done and update about any open items (IMP)

  11. QA assigns bugs to the Developers under a different JIRA story named as [Testing | <Task No.> ]

  12. Developer again works on the issues and releases same to QA in above mentioned steps.

  13. Daily Scrum call is taken at 6:30 PM to understand the status of ongoing tasks & sprint.

  14. After QA's sign off on the tasks & the issues, the corresponding release is deployed on Staging environment for Sanity.

  15. QA complete the Sanity and post that Dev & QA proceed for Production deployment.

Notes

  1. Most of the times, the production deployment is done only for few customers using the Flighting domains.

  2. The newly updated code is provided only to these customers and once everything seems stable the flighting code is moved to all customers.

  3. Every deployment has involvement for CS team members for Config & English changes.

Important Links

  1. Deployment Plan Sheet

  2. ExtraaEdge JIRA

PreviousProduct Tech ArchitectureNextGit Flow

Last updated 5 years ago

Was this helpful?