Agile Process in any company

 *** QA Agile Process Sequence ***

User Stories (sprint Planning)-Sprint Backlogs

Effort estimation – Product backlog grooming

Sprint kick-off meeting

Sprint starts (Daily stand up meetings)

Developers will develop code and testers will write test cases

Once test cases are written, testers will start testing user stories 

After all stories are tested (code freeze will be there)

Then testers start with regression testing to make sure nothing is breaking

Once testers complete with the regression testing, QA manager will give QA sign off

Then Release items will push into production à after production deployment sanity will be done

 Then sprint retrospective (liked,learned,lacked,action items)

-------------------------------------------------------------------------------------

Random distribution - Effort estimation techniques in Agile process

Also known as an ordering protocol, this technique places items in an order from low to high. Each person takes a turn, choosing either to move an item up or down one spot, discussing an item, or passing.

Your process is done once everyone passes on their turn.

-------------------------------------------------------------------------------------------

1.       Product Owner creates user stories (Requirements are what the customer provides. User stories are derived from requirements), they are called backlog items, During a sprint or iteration planning meeting, the team decides what stories they'll tackle that sprint.

2.       Then from those user stories they pick some user stories in a particular sprint and they are called sprint backlogs

3.       After sprint backlog, effort estimation will be done, which is also called product backlog grooming (product owner, scrum master, QA and development team), they group the user stories and they will do the effort estimation on the basis of different methods

4.       Once estimation is done, then sprint kick off will be done

5.       Then the regular sprint starts -Then they will schedule daily stand up meetings (what you have done yesterday and what you are going to do today)

6.       first of all, developers will develop the code, testers will write test cases, once test cases are written they will start testing of user stories which are part of a release, after all the stories are tested, they start with the regression testing (before regression there will be a code freeze, developers don't add nothing else to the code) and on that fixed code regression testing will be done to make sure that nothing is breaking. after QA sign off the release items will push to production, after production release there is a sanity which will be done on production environment to make sure nothing is breaking.