agile team code example

Example 1: agile

to rapid delivery for high quality product, not to
wait until last part of big project,
To make business happy.
Organize your work with your team.
Take responsibility of your activities.
We are implementing AGILE in our project. We have all scrum
ceremonies.
Our sprint is 2 weeks and we have released every 3 sprints as a
release cycle. We start the sprint on Tuesdays. We have 11 people in
my team:
PO, BA, Scrum Master (---, ---, ----)
5 Developers (---, ---, ---, ---, ----)
3 Testers (-----(team lead), ---- and me). We are all 2 SDET
+ manual.
Our Sprint Ceremonies starts with Sprint Planning Meeting and we
discuss about the team’s priority features and product backlog items
and we learn the part of the application which we are going to
develop throughout the Sprint.
I make sure every user story and respective acceptance criteria are
clear, this meeting is the perfect time and place to ask questions to
clarify if needed. Then As testers we decide who is goanna work on
which user story. Our test lead creates the test plan in Jira-Xray.
And then we choose user stories based on velocity and
capacity.
o - Velocity: Number of story points delivered in a sprint.
o - Capacity: Total number of available hours for a sprint
is Team’s capacity. Calculates holiday and PTO (personal
time off) hours. 5X2X8 = 80 points
Before the code comes to my environment, I start working on the
scenario>test cases>test steps.(2nd 3th days)
Then I start to write test cases(why not write them with scenario
and talk about them during the review meeting) and start to write
scrips.

Example 2: meetings in agile

=Grooming meeting - PO prioritize product backlog,
we are pointing user stories. it takes 2 hours

=Sprint planing meeting - 
when we select user stories from product
backlog to sprint backlog. Takes around 2 hours.

=Daily Standup meeting - everday except first day
and last day of sprint. 15 min

=Demo meeting - When we demonstrate our work.
In our company team lead demonstrate our work to client and po. 
This is where po checks our works if 
it meet with definition criteria

=Retro meeting - Takes usually 1 hour. 
Where we criticese our working process. 
Team members suggest new ideas to improve team.
Last action item we took in retro meeting
was developers sometimes forget to tell
testers when code pushed to test environment
To solve miscommunication we deciced developers
will let tester know on slack group chat
once they push the code.