-
Notifications
You must be signed in to change notification settings - Fork 3
How To Scrum
Scrum is lightweight, simple to understand and difficult to master.
The essence of scrum is a small team of people, who work together is a highly flexible and adaptive manner.
"A swift and focused stand up is the key to a team's effective collaboration."
Stand ups should be short and concise - remember that a 15min from 4 developers' day is actually an hour to a client. A stand up should only include a quick summary of what you did the day before, what you'll be doing today, and anything that might be blocking you - it's a time to state, not analyse and discuss.
The stand up is not a time to ask specific questions about a feature or a fix. It's also not the time to discuss any change in priorities.
Our stand ups occur every morning, for 10mins, and never for longer than 15mins.
- Make sure work is on track to be delivered within the allocated timeframe.
- Identify any blockers and and work to relieve them.
- Identify any shifts in priorities (if necessary) and pivot team to work towards these changes.
- Make sure all team members understand how they are contributing to the overall objectives of the project.
Decide who will be driving the demo and who will be explaining. It is recommended that these are two separate roles. This is because when navigating through the demo, it can be easy to speed up the pace of the demo as you know the website well and will click through at a speed that suits you. The best way to avoid this is having someone else explain the website, and also practice your demo several times before actually showing it.
Write a list of things you have learnt from previous presentations; things you are keen not to repeat, and others you think really work. Doing this will make sure your whole team are on the same page while presenting.
Know the audience - appreciate that not everyone will be technical, and therefore won't appreciate the technical detail you go into. Make the presentation accessible to the whole audience.
Have a script ready - prepare and rehearse a script which details what you're going to cover during the presentation and the demo. This will make you feel calm, prepared and make sure you don't leave any important bits out!
This is held with the whole team present and should last between 10-30mins. Each team member should have the opportunity to discuss things they feel went well during this sprint and things that could have gone better.
This is reviewing the backlog of work to be completed and outlining what work needs to be done, in line with the client's needs. Although the sprint planning is done for the whole sprint in advance, due to the short amount of time we are spending on this project, the sprint priorities will be reviewed on a daily basis or every two days.
It is important to remember that the aim of sprint planning is to recognise the highest priority issues and how long it would take to complete them.