in Tech
1 min read

Example: 3 Amigos story lifecycle process

  • Example of high level 3 Amigos (Business, Development, QA) story lifecycle process

Process teaser

Info

Business "PO", Development "DEV" and Quality Assurance "QA" should be understood as roles, not necessarily different persons at all times. E.g. if a QA specialist is unavailable, a DEV can also focus on the QA perspective during refinements.

StoryStoryStoryStoryStoryStoryStoryStoryStoryStoryPOStoryDEVQAPOPOStoryStoryDEVDEVQAQAStoryStoryStoryStoryStoryStoryStoryStoryStoryStoryNew Requirement[OPEN]ACsRefinementscheduleRefinement(1-2 sprints ahead)[REFINEMENT]SubtasksDefine allinterfacesas early as possibleInput:"What can go wrong?"Input:TestabilitySketchingE2E (acceptance/sanity) testsbased on ACsEnsuredependencies to stakeholders/other teamsare adressedEnsureno open questions or uncertaintiesas far as possibleEnsuringDoREstimation(Story points)Prioritization[READY]Sprint PlanningSprint (capacity)Planningcommunicatedependencies to affected teams againdependencies managed, sprint goal defined...alt[Development][DEVELOPMENT]Implementationincl. developerwhitebox tests(Unit etc)Blackbox smoke +sanity testingon integrated system("Main AC working from end user perspective?")[PEER REVIEW]Peer ReviewApproved& deployed foracceptance test[ACCEPTANCE TEST][QA]Development of SIT E2E tests incl. test data and error paths(manual/automated, for regression and acceptance testing)Reviewof E2E testsApprovalExecution ofE2E testsFinal approvalof ACs basedon- Feedback fromDeveloper tests-> technical functionality (Whitebox) and- Feedback fromE2E tests-> technical functionality (Blackbox) & domain correctness[RELEASE]ReleaseDeployto PROD(considering deployment checklist + rollout strategy)Deploymentstablefor 1-24h(depending on traffic, cron jobs...)Updaterelease notesCheckDoD[DONE]
StoryStoryStoryStoryStoryStoryStoryStoryStoryStoryPOStoryDEVQAPOPOStoryStoryDEVDEVQAQAStoryStoryStoryStoryStoryStoryStoryStoryStoryStoryNew Requirement[OPEN]ACsRefinementscheduleRefinement(1-2 sprints ahead)[REFINEMENT]SubtasksDefine allinterfacesas early as possibleInput:"What can go wrong?"Input:TestabilitySketchingE2E (acceptance/sanity) testsbased on ACsEnsuredependencies to stakeholders/other teamsare adressedEnsureno open questions or uncertaintiesas far as possibleEnsuringDoREstimation(Story points)Prioritization[READY]Sprint PlanningSprint (capacity)Planningcommunicatedependencies to affected teams againdependencies managed, sprint goal defined...alt[Development][DEVELOPMENT]Implementationincl. developerwhitebox tests(Unit etc)Blackbox smoke +sanity testingon integrated system("Main AC working from end user perspective?")[PEER REVIEW]Peer ReviewApproved& deployed foracceptance test[ACCEPTANCE TEST][QA]Development of SIT E2E tests incl. test data and error paths(manual/automated, for regression and acceptance testing)Reviewof E2E testsApprovalExecution ofE2E testsFinal approvalof ACs basedon- Feedback fromDeveloper tests-> technical functionality (Whitebox) and- Feedback fromE2E tests-> technical functionality (Blackbox) & domain correctness[RELEASE]ReleaseDeployto PROD(considering deployment checklist + rollout strategy)Deploymentstablefor 1-24h(depending on traffic, cron jobs...)Updaterelease notesCheckDoD[DONE]

This post is licensed under CC BY-SA 4.0 by the author. | Share:

Propose edit | Keep up-to-date via RSS | Support via PayPal

Comments