Content Comparison

Requirement is captured in form of user story

AC’s are captured, reviewed and agreed

Solution or strategy Design for each user story

Solution is reviewed and accepted by story owner

Story estimation in form of points

All the dependencies (including test data for external systems) to implement stories are identified and agreed for resolution during the course of sprint cycle

Data dictionary to be defined along with Single CRM (confirm with Yeng)

Everyone in team are having common understanding of the story and outcome expected

All the necessary access and tools are in place

Change management meeting in place

All the acceptance criteria written in story are met (Unit testing and functional testing)

Implemented stories are tested/reviewed by respective product owners / SME

All the outstanding questions related to implementation are resolved

Stories & Subtask are marked as “Done”

Update the config workbook/Solution Design to keep track of all the configurations done

Code review and unit testing completed

Showcase completed for all completed stories by end of sprint

Hands on training session (minor and medium changes) to be completed for each sprint following sprint Showcase

Knowledge document (SF article, video in MS teams) at feature for completed stories

Regression testing is must, reach out to Brad Fernandes (Unlicensed)