Agile and Scrum
At just two pages long the agile manifesto is a set of values and principles to adhere to, but it does not give much guidance on how to successfully accomplish this. Many frameworks, methods, practices, and tools have evolved that can help become more agile, some independent of the agile manifesto, others in some way connected to it.
For example, the agile manifesto states that working software should be delivered to customers frequently, but does not go into detail how to make that happen. Scrum, arguably the most popular agile framework, provides a more well defined approach to doing so: through a series of recurring meetings new versions of a product are planned, built, reviewed, and released to customers every 2-4 weeks. While the agile manifesto does not specify roles, Scrum defines three distinct roles: the Product Owner, the Scrum Master, and the cross functional Development Team.
Scrum was created before the Agile Manifesto, and the creators of Scrum were signatories to the Agile Manifesto.
So how does one approach things in an agile way? There is an evolving body of techniques and frameworks that are either founded on - or compatible with - the agile manifesto that help companies be more agile. One of the most well known of these frameworks is Scrum.
This collaborative approach to product development allows teams to self organize, make changes and adapt quickly.
Scrum is a lightweight framework that includes three roles:
- Scrum Master – the facilitator for the agile development team who manages the process but is not in charge
- Product Owner – prioritizes the backlog while keeping the product vision in mind and has decision-making authority
- Developers – the dedicated professionals who develop, text and deploy the product
These three roles regularly interact to continuously deliver valuable product updates every few weeks.
Check out this video from the Scrum Alliance on How Scrum Works
https://links.klose-coaching.com/SA-how-it-works
The nature of their interactions, including four recurring meetings, is outlined in the “Scrum Guide”. We will go into far greater detail on Scrum as we move into the course but for now, recognizing these roles is key to understanding how the process works.