Agile Applied for Social Cause :experience in Traffic safety campaign “Stop Look Wave”
Agile methodology is not limited to software development but it can be applied beyond. I am sharing the experience of applying the Agile, to drive the volunteering activity for the social cause. Volvo Group’s Global Safety initiative for Kids – Stop, Look & Wave is a program with young children (aged 4-10) at schools or communities – introducing them to Road safety .
The success of the program was based on support from management ,engaging volunteers (team members) and touching the young hearts to become the Safety Ambassador. Agile methodology and Mindset is applied for planning and execution and was very helpful to achieve the objective.
Outline/Structure of the Experience Report
1. Small demonstration "Stop ,Look wave " with audience - 10m
2. Objective and what we want them take back
3. What is the assignment/activity?
4. Why Agile and how was it implemented
5. Campaigns done
6. Closing note
1. Apply agile in beyond software development
2. STOP LOOK WAVE
3 Give back to society
Agile practioners and Social ambassadors
Prerequisites for Attendees
Open mind and interest to take back the message of agile and road safety
schedule Submitted 9 months ago
People who liked this proposal, also liked:
Alex Sloley - The End is Nigh! Signs of Transformation Apocalypse
How can an Agile Coach figure out when an Agile “Transformation” is going wrong? Are there signs that they might see, heed, and take action upon? Of course, there are!
Hindsight is 20/20, but in the moment, these warning signs can be hard to see. Let’s explore some of the more common, and frightening, warning signs that your Agile “Transformation” might be exhibiting. We will discuss transformation provider types, frameworks, keywords, and other anti-patterns that might be signs that THE END IS NIGH.
This session will review common themes and help familiarize you with the warning signs. Armed with this new knowledge, you will be able to plan as appropriate, to help navigate your organization through potential impending doom.
Alex Sloley - Liberating Structures... 36 tried and true facilitation techniques to amp up your org's collaboration
The communication tools of Liberating Structures will teach you how to facilitate the discussions your org needs. I am going to demonstrate how to use these techniques in the workshop. And all the attendees are going to be fully immersed and ready to wield their new knowledge the very next day at work.
Come learn how to help your team(s), org(s), and company(ies)!!!
For more information, watch my video at http://youtu.be/UNOjqMUv8h0
A version of this workshop that was presented at Agile Tour Sydney 2016 is at http://bit.ly/2f4Bie8
Gabor Devenyi / Alex Sloley - The magic number is 10
Why are Agile teams supposed to be small? How big are they supposed to be? Most agilists tend to agree that a team of ten people works well.
But what is it about the number 10 that makes it the “magic” number?
Since the start of human evolution, people formed groups to be more effective. Whether it was the hunt for a mammoth or going to war, working in teams ensured a greater chance of success.
There have been various researches from Dunbar’s paper through the Scrum Guide to military formations about the ideal number of people in a team.
We’ll discuss the historical, scientific and cultural reasons why 10 seems to be the magic number of forming effective teams.
Does the number of team members really matter? Is 10 really the magic number. You will get an answer that will help you to create effective teams with the right amount of people.
Alex Sloley - The Product Owner and Scrum Master Brain Transplant! Mwuhahahaha!!!
Imagine you are a Mad Agile Scientist and have a diabolical experiment to conduct - what would happen if you exchanged the brains of a Product Owner and Scrum Master? Mwuhahahaha!!! How would the body of a Product Owner with the brain of a Scrum Master act? And vice versa?
Perhaps the Scrum Master would now treat the team like a backlog? This Scrum Master would be focused on value and maintaining a coaching backlog of team and person improvements. This Scrum Master is refining the team, crafting a group that delivers value.
And perhaps the Product Owner might treat the backlog like a team? Rather than backlog refining, they coach the backlog. They would be focused on nurturing, protecting, and empowering the backlog. The backlog might transform from an irritation into a labor of love.
Although this experiment sounds terrible, this change of perspective might be what you need to reanimate your dead team or backlog.
Join the fun and come learn what horrifying results await!