Skip to the content

What is Scrum?

Scrum is a framework that helps squads\teams work together. Scrum encourages squads\teams to learn through experiences, self-organize while working on a solution, and reflect on their successes and failures to continuously improve.

While the Scrum I’m talking about is most frequently used by software development squads\teams, its principles and lessons can be applied to all kinds of teamwork. This is one of the reasons Scrum is so popular. Scrum describes a set of meetings, tools, and roles that work in together to help squads\teams structure and manage their work.

What to do and not to do?

 

Even with the basics down, most teams will stumble as they start to run sprints. Megan Cook rounds out this discussion with some Do's and Don’ts she's picked up over the years.

Do:

  • Make sure the team sets and understands the sprint goal and how success will be measured. This is the key to keeping everyone aligned and moving forward toward a common destination.
  • Do ensure you have a well-groomed backlog with your priorities and dependencies in order. This can be a big challenge that could derail the process if it’s not properly managed.
  • Ensure you have a good understanding of velocity, and that it reflects things like leave and team meetings.
  • Do use the Sprint Planning meeting to flesh out intimate details of the work that needs to get done. Encourage team members to sketch out tasks for all stories, bugs, and tasks that come into the sprint.
  • Leave out work where you won’t be able to get the dependencies done, like work from another team, designs, and legal sign-off.
  • Finally, once a decision or plan is made, make sure someone captures that information in your project management or collaboration tool, like your Jira tickets. That way, both the decision and the rationale are easy for everyone to see later.
  • While you’re working on being a Scrum all-star with these “do’s,” watch out for a few red flags too:

Don't:

  • Don’t pull in too many stories, overestimate velocity, or pull in tasks that can’t be completed in the sprint. You don’t want to set yourself or your team up for failure.
  • Don’t forget about quality or technical debt. Make sure to budget time for QA and non-feature work, like bugs and engineering health.
  • Don’t let the team have a fuzzy view of what's in the sprint. Nail it down, and don’t focus so much on moving fast that you forget to make sure everyone’s moving in the same direction.
  • Also, don’t take on a large amount of unknown or high-risk work. Break down stories that are large or have high uncertainty, and don't be afraid to leave some of that work for the next sprint.
  • If you hear concerns from the team, whether it’s about velocity, low-certainty work, or work they think is bigger than what they estimated, don’t ignore it. Address the issue, and recalibrate when necessary.

 

Choosing the right work items for a sprint is a collaborative effort between the product owner, scrum master, and development team. The product owner discusses the objective that the sprint should achieve and the product backlog items that, upon completion, would achieve the sprint goal.

The team then creates a plan for how they will build the backlog items and get them “Done” before the end of the sprint. The work items chosen and the plan for how to get them done is called the sprint backlog. By the end of sprint planning the team is ready to start work on the sprint backlog, taking items from the backlog, to “In-progress,” and “Done."

During a sprint, the team checks in during the daily scrum, or standup, about how the work is progressing. The goal of this meeting is to surface any blockers and challenges that would impact the teams ability to deliver the sprint goal.

After a sprint, the team demonstrates what they’ve completed during the sprint review. This is your team’s opportunity to showcase their work to stakeholders and teammates before it hits production.

Light window Image
Tech Agnosticism

The team know their stuff. We went from an on-prem application to SaaS within 18 months. They get tech and us.

Managing Director - FTSE250 Company

JUMP SOFTWARE LTD

39 ASHBURN ROAD

STOCKPORT

SK4 2PU

0808 143 0699

Contact us to talk tech

If you want to talk agile, tech or want to sound off then contact us on 0800 689 1376