Showing posts with label Agile Sprint Planning. Show all posts
Showing posts with label Agile Sprint Planning. Show all posts

Agile - Sprinting and the Daily Scrum



In our previous article on Agile meetings, we discussed sprint planning.  Let’s look at what happens next.

Sprinting and the Daily Scrum

Once we’ve finished sprint planning and have a commitment, we are ready to start the sprint. This is a two-week time box in which the team creates a tranche of working, potentially deliverable software.

During a sprint the team will hold a daily scrum, a 15-minute meeting in front of the sprint backlog (a visual display of what needs to be done, usually in the form of a whiteboard covered in written-on Post-It notes). This provides an opportunity to synchronise as a team and talk about what we’ve done, what we plan to do and anything standing in our way.

The scrum master oversees the meeting and listens out for any problems that may have arisen that could cause a delay.  It’s their responsibility to remove impediments and mitigate any future risk.  The scrum master uses a number of charts and techniques to understand if the team is on track and, if it’s lost direction, how to get it back on track.

We encourage continual feedback, so outside of the daily scrum there are regular conversations within the team and with the product owner to ensure we’re on the right path. The sprint is finished at the end of two-week time box.

Keep an eye out for our next article on the ‘Sprint Review’.

Agile Sprint Planning


In our previous article on Agile meetings we discussed how we prepare user stories for the teams. Let’s look at what happens next.

Sprint Planning

Once a user story has been prepared and given priority in the product backlog the team will take this work into the sprint planning meeting. This session is where the team plans out what must be done to deliver it. This will include tasks around design, development and testing, including performance. Some of these sessions can get quite technical and detailed so we need to make sure it is facilitated well, which is the job of the scrum master. It’s likely that a lot of questions will crop up, so having the product owner at hand is recommended.