Scribd
Upload
103 views1 page

AO Agile Methodology WorkFlow

The document describes the agile methodology workflow which includes backlog grooming meetings to prioritize user stories, sprint planning meetings to assign stories to developers and estimate story points, daily scrum meetings for status updates, sprint reviews at the end of each sprint, retrospectives after each sprint to improve, and RCA meetings to resolve previous sprint challenges. Developers implement features while testers design test cases, then QA signs off before user acceptance testing and deployment to QA environments.

Uploaded by

Prashant Gupta
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
103 views1 page

AO Agile Methodology WorkFlow

The document describes the agile methodology workflow which includes backlog grooming meetings to prioritize user stories, sprint planning meetings to assign stories to developers and estimate story points, daily scrum meetings for status updates, sprint reviews at the end of each sprint, retrospectives after each sprint to improve, and RCA meetings to resolve previous sprint challenges. Developers implement features while testers design test cases, then QA signs off before user acceptance testing and deployment to QA environments.

Uploaded by

Prashant Gupta
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

AO_BJSHUB -- >>> AGILE METHODOLOGY – Complete works flow

Start a New
Sprint again
RCA Meeting to resolve
previous sprint
challenges/mistakes
BA – Create user
stories and Keep
into Backlog
Retrospective meeting
after sprint completion

What was good ?


Back-Log grooming What went wrong ?
meeting – Priorities
the user stories
which need to Sprint Review Meeting
implement first at the last day of sprint

Sprint Planning
meeting : Assign the After QA Sign-off , BA
Story to Devs, And /Client will perform
ask Story points to UAT testing into UAT
devs
env

QA Will start the test case


Start the Sprint execution / Defect Reporting
and go through Sign-off
Activity

Scrum Meeting at daily basis : After Feature


Implementation by Devs :
1. What I have done yesterday Devs will deploy the build
into QA
2. What I will do today

Devs will start the Testers will start


Feature designing test
implementation scenario/test
cases/RTM

ion

You might also like