Small Scale Scrum Principles

Principles presented below address (1) what approach towards communication should be taken in Small Scale Scrum, (2) what processes should be introduced to ensure the highest quality of delivery, and (3) what are the benefits behind implementing Small Scale Scrum for the business.

Small Scale Scrum principles are non-negotiable.

Agnieszka Gancarczyk, Small Scale Scrum Principles, 2018

Value-based Communication — This principle emphasizes the inner and outer communication within development team and the customer and is focused on delivering a value. Understanding of the solution, its purpose and its desired functionality is based on effective communication. Initiating and maintaining communication between parties requires openness and dedication in looking for the best solution to a given functionality request. Openly discussing and sharing steps to be taken or taken to fix an issue or to implement a feature is part of effective communication and it may lead to some further discussions around progress made in software delivered which can in turn uncover any potential omissions in the requirements. With finite time, all communication should be valuable.

Quality-first Development — This principle focuses on taking a quality approach to software development each Sprint. This means ensuring that features are delivered as per acceptance criteria, solution is bug free (or at least free from any evident bugs), any inconsistencies in the software are removed, solution is tested, any edge case bugs along with any omitted features are reported, logged and considered by the customer.

Delivery Ownership — This principle is about taking initiative in driving software delivery by Development Team on a Sprint-to-Sprint basis. Enabling the team to consult the customer directly is seen as having a positive impact on the overall performance of the team and customer satisfaction. Removal of micromanagement barrier in a project, if such exists, is critical to allow the team to take ownership in delivering software solutions.

Iterative Sign Off — This principle focuses on reducing technical debt and identifying gaps in requirements through iterative sign off approach. As the solution evolves and matures, business requirements change. With iterative development, functionality delivered within a Sprint should be signed off on Sprint completion. Similarly, requirements for the upcoming Sprint should be signed off prior to a new Sprint commencement.


From “Small Scale Scrum: A Framework for Successful Implementation of the Scrum Methodology for Small Sized Teams” by Agnieszka Gancarczyk and under the supervision of Dr Leigh Griffin.

Welcome to a place where words matter. On Medium, smart voices and original ideas take center stage - with no ads in sight. Watch
Follow all the topics you care about, and we’ll deliver the best stories for you to your homepage and inbox. Explore
Get unlimited access to the best stories on Medium — and support writers while you’re at it. Just $5/month. Upgrade