Our workshop uses the Scrum methodology. This is not an acronym as you might assume, but a framework for project management that is generally connected to Agile. This process consists of some setup steps and a cyclical development rotation. 

Setup

• The first step is creating a Project Charter 
  • This is the agreement that dictates what we are developing. 
  • Think of it as our contract. 
• Next, we determine Requirements
  • This includes things like what we need to connect to your system, any and all licensing required, and access to the code base.
  • Think of this as getting all the keys together to hand over. 
• Finally we have Product Backlog Creation
  • This is the list of tasks that we will need to be updated or added to your system.
  • This master backlog will be curated as we begin the Scrum cycle. 
  • Think of this as your wishlist for your product. 

Scrum Roles

Here are some common roles and terms that will come up in the Scrum process.

• Scrum Master 
  • This is the person who oversees that the typical Scrum process is followed.
  • This is the Coach who directs the play.
• Project Owner
  • This is your person from our team that is your advocate. 
  • The PO will be your guardian, making sure everything is going exactly to your specifications.
  • Wire Framing
    • This role involves creating functional renderings of your application so that the developers can create the exact code you need. 
    • This is the outline for your app.
• Development Team
  • This is the group that will execute on the design. 
  • They meet daily to make sure that every step of the process is going as planned.  

Scrum Ceremonies

The Scrum process uses four types of meetings to make sure work goes right.

• Sprint Planning
  • This meeting will be once per sprint, for us that is once per month.
  • It will be between your team and your PO, that’s it.
• Backlog Grooming
  • This is a meeting to go over the backlog of tasks to make sure everything is still in line with what the application needs. 
• Daily Scrum
  • This is a 15 minute meeting that takes place every day of the sprint.
  • Goal is to determine what progress has been made and how to help.
• Sprint Review
  • These are meetings for you to meet with the developers.
  • You can talk with them directly, generally at a secondary location.
  • This is your main chance to really show the team your vision.
• Sprint Retrospective
  • This is an internal meeting that covers the process of that sprint.
  • What worked well? What didn’t?
  • Then we take what we learned and make the next sprint even better!

The Scrum Lifecycle

SCRUM revolves around sprints. Typically, we will run a month long sprint cycle. 

• Planning
  • This is when the Sprint Planning ceremony happens.
  • We work together to plan what can be done in this sprint.
• Implementation
  • Daily SCRUM meetings happen here. 
  • This is where the bulk of the month is spent iterating on your product.
• Review
  • This is the Sprint Review. 
  • Time to party and see what we accomplished together.
• Retrospect
  • This is the Sprint Retrospective meeting.
  • We’ll figure out how to do better each and every sprint.
• Deployment
  • If this sprint had a goal of deploying new updates or changes, this will happen at the end of the month.