There are many flavors of agile software development. Programme where multiple teams work together to deliver a programme, sometimes use SAFE (Scaled agile framework) approach .Some experts say scaled scrum is still a scrum. Important thing is to identify the features of your product and deliver them end to end.
I have worked in both safe and scrum deliveries.
SAFE is good process for an enterprise delivery. Scrum is good for a start up or standalone project.
I have even experienced 2 flavours of SAFe. In first, we had small scrum teams with 6-8 team members, in the second we had a team of 13-14.
The first delivery team was working on different features e.g. login logout, payment in the second delivery teams were working on components.
Teams focus on delivering a working software which could be a group of features or a single feature covering a number of user stories. During this sprint team members attend a daily stand up with the whole team to understand what is going on in each area of the project and who is doing what and when. It is an opportunity to align your tasks with the whole team, discuss blockers , see issues and show progress.
In my latest project we used story grooming sessions as a walkthrough of the future sprint user stories. This is a quite effective technique of identifying issues and risks for future sprints.
At the end of two weeks, organize a sprint review session, invite stake holders, dependent projects and give them a demo on what you have done, get the feedback and adapt accordingly.
Sprint retrospective is the last stage of the sprint delivery. There are quite a few ways of doing retrospective
Sprint actually starts with sprint planning. Team members are advised to list down the tasks for testing. I have been using test design, execution, automation tasks for each user story. Try to make automation activity as a must do activity. You don’t have to automate everything but at least try to do have bare minimum business processes automated.
Anyway in some projects we ended up having more tasks for testing than development. So sometimes we just kept one task as testing.
In some projects we were told to split tasks in 6 hours slot, The idea is to finish task everyday so that scrum master can see them in the hours burndown chart in Jira. Story points burn down charts have been the most preferred way of tracking the progress in the agile teams though.