Scrum is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. Scrum is founded on empirical process control theory, or empiricism, which asserts that knowledge comes from experience and making decisions based on what is observed. It helps us to become a high performing team and manage our work by ourselves without a need for a assigned manager.
Scrum Roles
Product Owner
The birthday child deciding his party’s theme dictates the event’s flavor. Similarly, a Product Owner specifies the product’s features and their priority.In Scrum: The Product Owner champions the product, understanding user needs, and conveying them to the team.
Scrum Master
A coach ensuring everyone knows the soccer game rules parallels the Scrum Master, who ensures Scrum practices are followed.
In Scrum: The Scrum Master is the guardian of Scrum processes, aiding the team in following them efficiently.
Development Team
A group of chefs collaborating on a grand feast is emblematic of the Development Team, jointly crafting the product.
In Scrum: This is a cross-functional group responsible for delivering potentially shippable increments every sprint.
Scrum Artifacts: The Tools
Product Backlog
Your bucket list of dream destinations is akin to the Product Backlog, where desired features are listed and prioritized.
In Scrum: This is an ever-evolving list of all features, enhancements, and bug fixes required in the product.
Sprint Backlog
Breaking down study chapters before finals mirrors the Sprint Backlog, where specific tasks are earmarked for the sprint.
In Scrum: Chosen from the Product Backlog, these items are what the team commits to delivering during a sprint.
Increment
Creating a layered cake, with each layer adding value, mirrors how post-sprint, there’s always a potentially deliverable product segment.
In Scrum: An increment embodies all the items from the Product Backlog completed during a sprint, cumulatively with previous sprints.
Scrum Events
Sprint
Your decision to declutter the entire house in a weekend sets a clear goal. In Scrum, a sprint is a fixed period where teams aim to complete specific tasks.
In Scrum: Sprints, usually lasting 2-4 weeks, result in a potentially deliverable product increment.
Sprint Planning
Mapping a vacation route mirrors sprint planning, where teams discuss the tasks and their execution strategy.
In Scrum: This is where the team aligns on the sprint’s objective and crafts a game plan to achieve it.
Daily Scrum
A quick morning family meeting to layout the day’s plan mirrors the daily Scrum, where updates and strategies are shared.
In Scrum: These are short, daily stand-ups where teams align on the day’s work and discuss potential blockers.
Sprint Review
After a movie, you discuss its highlights. Similarly, post-sprint, teams review their work with stakeholders.
In Scrum: The team showcases the increment to the stakeholders, gathering feedback for future sprints.
Sprint Retrospective
Reflecting on a year gone by, teams in Scrum too discuss what went well and what could change.
In Scrum: This is a post-sprint reflection, determining the successes and areas of improvement for the next sprint.
Scrum Values
Courage
Imagine standing up in a group when everyone else holds a different opinion. Just as you’d muster the courage to voice out in real-life situations, in Scrum, teams are emboldened to confront and address obstacles and challenges.
In Scrum: Courage entails the team’s ability to take on tough projects, address issues without fear, and commit to delivering despite challenges.
Focus
Think of reading a book in a quiet corner, committed to finishing a chapter. Like this undivided attention, Scrum teams zero in on specific tasks during a sprint without wavering.
In Scrum: Focus is all about zeroing in on the sprint and its goals, ensuring that any external distractions are kept at bay.
Commitment
Like promising to help a friend move, once you’ve committed, you make it a point to be there. In a similar vein, Scrum teams pledge to deliver particular work and see it through.
In Scrum: Commitment doesn’t just mean taking on tasks. It means dedicating oneself to the sprint goals and ensuring they’re met.
Respect
Remember patiently hearing out a friend’s perspective, sans interruption? This quality parallels Scrum, where members appreciate each other’s roles and viewpoints.
In Scrum: Respect is fundamental. It’s about valuing everyone’s input and acknowledging the diverse skills each member brings to the table.
Openness
Sharing your concerns or joys with a confidant is akin to the openness Scrum teams maintain about progress and hurdles.
In Scrum: Openness implies transparent communication about progress, challenges, and feedback throughout the project.
The Three Pillars
Transparency
A transparent jar showing its contents is akin to how, in Scrum, work stages are visible to all involved.
In Scrum: Transparency ensures that every team member understands the task at hand, its requirements, and the progress made.
Inspection
Before sipping milk, you’d check its expiry. Analogously, Scrum teams regularly examine their work to ensure they’re on the right track.
In Scrum: Inspection involves periodically checking the product to ensure quality and alignment with user requirements.
Adaptation
If your soup is too salty, you adjust the recipe. Scrum teams, when sensing something’s off, pivot their approach.
In Scrum: Adaptation signifies the team’s agility in adjusting their strategies based on inspection outcomes to improve product value.
Conclusion
By juxtaposing Scrum’s elements with our everyday experiences, it becomes evident that many of its principles resonate with actions and decisions we make daily. It’s all about collaboration, transparency, and delivering value, principles we live by in myriad ways in our lives.
