Scrum is a way of working which can fall under the Agile methodology. Wider research around scrum will lead you to the framework definition of what scrum is and how it used in software development or for projects which require a high level of day-to-day management. From an academic perspective we are simply interested in what is referred to as Daily Scrum
So what’s required:
Ideally a daily 10 minute meeting (Even once/twice a week can work too).
A scrum master (Teacher/Student).
A scrum board (Electronic/designated whiteboard).
Scrum Stories (Homework/Coursework/dental/medical appointments/Parental meeting).
Scrum Participants (Students).
Recommended: A diary/planner which serves as a data provider for non-enthused students.
The Daily Meeting
In industry scrum (standup’s) occur each and every day, naturally, in education other time constraints and registration requirements may take priority over having a daily standup. This is fine and i have seen scrum work effectively when used just once a week as long as the stories are created and updated accordingly. Students should all stand up and located themselves near to the scrum board in advance of providing updates to the scrum master for their stories.
The Scrum Master
The scrummaster chairs the entire meeting and is the only person permitted to talk, unless a response is invited from a student for updating a story. Initially the teacher should assume the role of scrummaster and once you have scrum practice embedded then the role of scrum master should be rotated around the class, or used as a reward mechanism.
The Scrum Board
In industry the scrum board is usually a dedicated wall/whiteboard that is designated as the resource for holding the stories as part of a sprint (A sprint is an identified period of time to complete set work) instead of the word sprint and the time framework, teachers could easily use a half term. The board is broken down into a few key areas, but you can add your own areas, build your board for your own needs. I have seen some scrum boards organised via student name as column headers, which worked equally well. A word of caution, some students may be tempted to move notes around on the board if you are out of the room, and it is for this reason that i have two available options, take a photograph of the board after scrum has finished. Alternatively there are some excellent scrum boards available electronically. Check out my article on Kanbanchi
Stories can be used for absolutely anything, it does not always have to contain stories which are related to academic work and a stories details are usually recorded on a post it note. Stories can serve as reminders to bring money in for a school trip, a dentist appointment etc. However, the primary focus of the board is for ensuring that all your students are organised, on track for delivering home/coursework on time, every time. You can also use different coloured post-it notes for different categories of stories.
A story should be created for each individual piece of work and usually contains the following information wrote upon a post-it note:
Short Description of work
Maths: Algebra Homework
Dentist Appointment AM
The Scrum participants
You and your students
Feel free to invite anyone else.
You will need to get your students to initially create one story. In industry, stories are usually generated by a business analyst or a project manager who oversee the client or project needs. It is very different in school, as you are essentially requiring your students to give you visibility over their work requirements. Whilst some students understand and buy into this, there will always be students who are not keen on giving you awareness of their coursework and homework expectations for obvious reasons. This is when you need the helping hand of a data provider. Usually this is a school planner, however, for this to work well you need to have consistent use of planners across the school for the setting of work. If a student lacks the motivation to participate, or responds that they have no homework, then a quick double-check of the planner will inform the outcome and creation of stories. As a side note, try getting those who are disinterested the role of scrum master to get buy in once you are up and running.
Facilitating the session
Hold your scrum at the beginning of your registration class. Everyone should stand, and the scrum master selects the first story from the top of the board from the to-do section. The story owner is then asked to provide a status update, now we have a few scenarios for Student A:
Scenario 1: Student A responds that for example, the homework has been started. Therefore the scrum master then moves the story to the doing section and moves onto the next story.
Scenario 2: Student A, responds that they are unable to start the homework as they do not have a worksheet. This is known as a blockage. Therefore the scrum master/teacher makes a note of this for the student to go and get a worksheet. Alternatively, another student may advise that a worksheet can be obtained from a specific location, such as Google Classroom etc, cross-collaboration.
Scenario 2: Student A, responds that they are struggling with an IT homework for creating a simple website, as the student missed an HTML lesson. Again another blockage, another student who is good at HTML offers to help student A with his website skills so Student A can complete the work. Teamwork and skill sharing with cross-collaboration
The aim here, is to identify problems and resolve them with minimal disruption. Instead of a student ignoring the problem in the hope that it will go away.
You will proceed to get an update for each and every story. This process can last a few minutes, but should never exceed ten. At the end of the session, provide an opportunity for students to add new stories to the scrum board. For large courseworks, students should break down large projects into small stories to serve as small milestones.
You can shape scrum to work for you, like i said earlier, nothing is set in stone and everyone’s classroom is different. Feel free to contact me, if you need clarification of any of the areas. Equally do get in touch if you want to share your success stories.
Andy @ TeacherTech
You can discuss this article over at the Teacher Tech Facebook page, click here to request access.