Nonprofits can start using Scrum for one agreed-upon focus area, such as a fundraising committee, and forming a cross-functional team of 3 to 9 people. By following a structured checklist that includes setting Sprint goals and maintaining work visibility, organizations can create twice the impact in less time.
How to Build Your First Scrum Team
To begin your Agile journey, you must first identify which area of your organization will benefit most from the Scrum framework. Many nonprofits choose to start with a specific program, a grant-writing team, or a fundraising committee. After you have selected a focus, you should outline high-level goals so that you can form your initial Product Backlog.
The next step involves assembling a cross-functional team. An ideal team size is 4 to 6 people to ensure optimal performance, though any group of 3 to 9 people can work. Every team requires two specific roles:
- Product Owner: This individual is responsible for prioritizing the work.
- Scrum Master: This person facilitates team self-organization and removes obstacles.
To inspire your team, encourage everyone to read Scrum: The Art of Doing Twice the Work in Half the Time by Jeff Sutherland. This resource helps shift the team’s mindset toward more efficient ways of working.
Setting Up Your First Sprint
A Sprint is a consistent time period, usually 1 to 4 weeks, during which the team completes specific tasks. Shorter Sprints are often better because they allow for faster feedback. Before you begin, you must determine where to make your work visible. While virtual whiteboards are popular for remote teams, physical whiteboards in a shared office space can work effectively as well.
Make sure to gather the necessary supplies, such as whiteboard markers and “Super Sticky” sticky notes, to keep your tasks organized. At the start of the process, your team should set a clear goal for the first Sprint. This goal helps you identify which items from your backlog will form the Sprint Backlog.
Communication is vital during this period. Your team should meet for a 15-minute Daily Scrum every day, ideally as early in the day as possible. At the end of the Sprint, invite your primary audience—such as leadership or constituents —to a Sprint Review to review the latest progress. Finally, conduct a Retrospective to discuss how to improve your way of working for the next cycle.
Key Takeaways
- Start Small: Select one committee or program to test the Scrum framework.
- Define Roles: Ensure you have a Product Owner to prioritize tasks and a Scrum Master to facilitate the process.
- Prioritize Visibility: Use whiteboards or digital tools so that everyone can see the progress of the team’s work.
- Iterate Constantly: Use the Retrospective at the end of each Sprint to select a “Kaizen,” or a priority for improvement.
FAQ
What is a Kaizen in Scrum? A Kaizen is a specific priority for the upcoming Sprint that the team believes will make them happier and faster. It focuses on testing one change to the process itself to improve the way everyone works together.
How long should a Daily Scrum last? The Daily Scrum should be a brief check-in that lasts only 15 minutes each day.
How many people should be on a Scrum team? Although a team can range from 3 to 9 members, the most effective teams typically consist of 4 to 6 people.
Ready to Create More Impact?
Starting a new way of working can feel like a big shift, but you do not have to do it alone. We have helped many organizations transition to Agile to meet their goals more quickly. You can learn more by exploring our other resources on getting started with Scrum.
Download our Free “Getting Started with Scrum” Checklist here!