Entire Process from Backlog -> Deployment

1. Product Backlog Refinement:

   • Start with a prioritized product backlog, which contains a list of features, user stories, and tasks.

   • The product owner and stakeholders collaborate to refine and prioritize items in the backlog.

   • More info here: Sprint Planning Prerequisites

2. Sprint Planning:

   • At the beginning of each sprint (2 weeks), the team selects a set of top-ranked, backlog items to work on.

   • The team breaks down these items into smaller tasks and estimates the effort required to complete them.

   • More info here: Sprint Planning

3. Development:

   • The development team works on implementing the selected backlog items during the sprint.

   • The QA team starts developing the relevant test-cases in Test-Case management project on Jira.

   • Jira board is updated the with status of the tickets regularly.

   • Daily stand-up meetings are held to ensure everyone is aligned and to address any blockers.

     • More info. here: Sprint Standups

4. Continuous Integration:

   • Code is continuously integrated into a shared repository (version control system), and automated unit tests are run to ensure code quality.

5. Testing:

   • As and when a ticket is marked QA-Ready, QA Team links the corresponding TCs to the ticket and starts test execution.

     • More info here: Jira | Workflows

   • Defects noticed during the tests are reported and assigned.

     • More info here: Defect Reporting and Issue Tracking - Youtap Tech Indonesia - Confluence (atlassian.net)

6. Review and Demo:

   • At the end of each sprint, the team holds a sprint review meeting where they demonstrate the completed work to stakeholders.

   • Feedback is collected, and any necessary adjustments are added to the product backlog.

   • More info here: Sprint Reviews

7. Sprint Retrospective:

   • After the review, the team conducts a sprint retrospective to reflect on what went well and what can be improved in the next sprint.

   • Actions are identified to enhance the team's performance.

   • More info here: Sprint Retrospectives

8. Release Planning:

   • The product owner, Release manager and stakeholders discuss the release goals and decide which features or user stories should be included in the upcoming release, based on business priorities.

9. Release Development and Testing:

   1. Release Process

10. User Acceptance Testing (UAT):

    • There may be a UAT phase where end-users or clients validate the software to ensure it meets their expectations.

    • More info here: Testing Taxonomy

11. Deployment:

    • Release Process

12. Monitoring and Feedback:

    • After the release, the team monitors the software in production, collects user feedback, and addresses any issues that arise.

13. Repeat:

    • The process continues with the next sprint, building on the feedback and lessons learned from previous releases.

Throughout this process, Agile teams prioritize flexibility, collaboration, and delivering value to customers. The key is to maintain a feedback loop, iterate frequently, and adapt to changing requirements and business priorities.