<img height="1" width="1" style="display:none" src="https://www.facebook.com/tr?id=344430429281371&amp;ev=PageView&amp;noscript=1">

It's Time To Start Your First Course Development Project in Scrum

Posted by Bill Cushard on Jul 19, 2017 6:00:00 AM

This blog post was co-written by Donna Weber and Bill Cushard. You can learn more about Donna on Linkedin and her work at Springboard Solutions

In this blog, we apply what we learned from the previous three scrum blogs: Five Reasons to Use Scrum for Course Development, A Quick Guide to the Scrum Process, and How to Plug Course Development Elements into Scrum, to start your first project. However, before your first sprint, make sure to complete these five tasks to ensure project success.

  1. Define the project goals

  2. Gather the project team

  3. Select your project management / tracking tool

  4. Determine the length of your first sprints

  5. Schedule stand ups

The ServiceRocket Guide to Better Agile Course Development Using Scrum

Image Credit: https://commons.wikimedia.org/wiki/File:Scrum_Principles.png

Define the Project

Make sure you have a clear project goal before you start your first sprint. Remember, your goals might change based on feedback you receive throughout the process.  As a result, keep your goals high level. For the purpose of this book, we are developing an Administrator 101 course.

Identify the Project Team

Determine who will be on the team and what role they will play. As you learned, there are three main roles on a scrum team: product owner, team member, scrum master. For large-scale course development projects, you may have course developers, editors, subject matter experts, and others. Each of these roles would be a separate team member. For small teams, these roles might overlap and team members might fill multiple roles. For example, a lead instructional designer might also be the scrum master.

Select Your Project Management Tool

Before you assemble your team and schedule your meetings, select a work tool to track the progress of your project. Don't worry about purchasing expensive software. Pick a big, blank wall in your office and use sticky notes. Find free versions of cloud software tools. Use Excel or Google Sheets. While there are many excellent scrum tools to explore, (we cover the tools towards the end of the book to help you sort that all out), select a simple tool to capture and track project tasks.

Define Your Sprints and Schedule First Sprint Planning Meeting

Sprints tend to range from one to four weeks. However, once your team is assembled, then together determine what works for you. There is no magic sprint length. The trick is to make sure your sprints are long enough you can accomplish meaningful work, but short enough that your customers and stakeholders see frequent and regular deliverables. As you gain experience with scrum, adjust the time frames as needed for what works in your environment. Once you determine your sprint length, schedule your first sprint planning meeting, to plan your first sprint.

Schedule Stand Ups

An important part of each sprint is the regular stand up meeting to keep the team on track. This is the daily meeting that occurs with everyone on the scrum team. We used two stand ups per week while developing this book because we thought daily was overkill for this project. Determine what works for your team, and get it on the calendar.

Now that you defined your project, assembled your team, selected your project management tool, and scheduled your first sprint, it's time to start your project.

In our book, The ServiceRocket Guide to Better Agile Course Development, we  walk through examples of what your first sprints might look like, so you know what to expect. We also cover tools and resources to help you be successful.


The ServiceRocket Guide to Better Agile Course Development

Developing courses is hard. It takes a lot of work, and it is time consuming. Depending on the type and length of course you need to develop, it could take weeks to create and ship to your customers. In a fast moving software world, this is too long. We wrote a guide to help you speed things up and build better courses using scrum.

After you read this guide, you will have the tools to build better courses, faster, and more aligned to customer needs. 

Don't waste any more time. Download The ServiceRocket Guide to Better Agile Course Development.

Get the Free Guide

Topics: Customer Education, Agile, scrum, Instructional Design, Course Development

Join our Newsletter

Subscribe now to our Customer Education Weekly newsletter to receive hand-curated content from the customer education space and exclusive content about building and running your education operation that you cannot get anywhere else. Not even from our blog. By subscribing, you will also receive an email each time we publish a new blog post.

Interested in writing for the Customer Education blog? 

We love connecting with software leaders and writers who can help us fulfill our mission to create entertaining AND educational resources that people can put to use. Find out how.

Recent Posts

Popular Posts

Posts by Topic

see all
Bill Cushard

Written by Bill Cushard

Bill Cushard covers the intersection of learning, software adoption, and customer success. His career has focused on helping companies adopt disruptive software through learning, change management, communications, and implementations that help people get the most out the software.

Bill Cushard is also the author of the 2018 book, The Art of Agile Marketing: A Practical Roadmap for Implementing Kanban and Scrum in Jira and Confluence.

comments powered by Disqus