Paying it Forward on Scrum & Agile Training
By Bachan Anand / Filed under Info tech / June 6th, 2011
Irvine Class – Go Game
Irvine Class – Scrum Simulation
Boston Class – Scrum Simulation Review
Why ‘Pay it forward’?
It is an undeniable fact that Scrum has reformed many of our lives for the better. Agile and Scrum have changed our world of work from a dull, mechanical one to a vibrant, thriving and joyous one, that develops close bonding within the team, so that Work is Good.
We wish to spread the awareness and invite others to the world of Agile and Scrum, to share the knowledge, through our training sessions.
For anyone in transition or others who are unable to pay for the classes, we offer the option of donation. “Paying it forward – Donation only” is our way of giving back to the community.
Previous sessions
In the last five weeks, there were five Pay it Forward classes on Agile & Scrum across 4 cities: Boston, Seattle, Irvine and Denver.
I wish to thank my mentor Tobias Mayer, who always reminded me that the Scrum method of working is a gift we have received, which alters the way we perceive work. He inspired me to conduct more trainings and introduce people to the joys that I experienced when I came across Scrum.
Gratitude is also due to Erin Beierwaltes for facilitating the class in Denver, and RightNow (Erin’s client) for donating the venue.
It is always a pleasure to have other Scrum enthusiasts facilitating the classes. Jeff Lopez-Stuit, who is the ScrumMaster at World Vision, facilitated the class with me in Seattle.
Thanks to Scrum Alliance for inviting me to the Scrum Gathering, which made it easier for me to run the session in Seattle. Carlos Buxton and Kriss Aho were of great help at the class in Boston.
Upcoming trainings
In the coming months, we have a few classes on Agile and Scrum scheduled in Boston, Seattle, Irvine and Denver. We look forward to your presence, to share your views, experiences and thoughts on the topics.
If you wish these trainings to be conducted in other cities, please contact us using this form.

Boston Class – Scrum Simulation
Participants Speak:
Bryan D. Mize, Participant, May 15th One day class in Seattle wrote:
“I was fortunate enough to take Bachan’s one day Intro to Scrum training course recently in Seattle. Not only was the course well organized and implemented, but it was implemented using the Scrum methodologies, so the participative/self organizing concept was more than conveyed, it was experienced. Bachan’s abilities to facilitate successful interactions amongst total strangers speaks volumes of his knowledge and experience in team-building. I took many “lessons” and experiences from that day, and will be able to apply what I learned in many aspects of my life.
If you are fortunate enough to have this opportunity, it would be my suggestion that you take it!”
Dan Goddu, Participant, May 20th One day class in Boston wrote:
“Bachan and his team delivered an excellent day-long seminar in the true Agile/Scrum fashion. For someone like myself who had only brief academic exposure to Agile, I left the seminar at the end of the day with a solid understanding, ready to discuss it, debate it, and apply it.
I would highly recommend this seminar to anyone who was new to Agile or needed a refresher.”
Joshua Potts, Participant, June 4th One day class in Irvine wrote:
“Bachan’s course on Agile concepts combined with group activities demonstrating them was a high-quality presentation that I will definitely recommend to others. He has an excellent sense of timing, allowing you to really grasp and absorb the concepts.”
Pay It Forward Trainings by Conscires
8 Agile UNfriendly Scenarios
By Bachan Anand / Filed under WORK is GOOD / November 24th, 2010
It seems Agile is everywhere: haunting my Twitter feed, invading LinkedIn, creeping into all my favorite blogs. However, Agile is NOT for everyone. While perusing LinkedIn, I stumbled upon a few lively discussions debating when Agile is or is not appropriate. What did I take away? Read on.
Don’t use Agile if…
- You hate delivering value but love spending money.
- You despise customer involvement and early feedback.
- Collaboration nauseates you. Who wants to see her team self organize around a challenge and maximize potential? Sickening.
- Understanding of the overall system and/or product vision is only intended for an elite few in your organization. (This one is especially important if you are a subject matter expert and love being allocated to bazillions of projects and gazillions of teams.)
- Change requests are your guilty pleasure and you dream of contract re-negotiations. This rule also applies if customers are your worst nightmare.
- Your QA team only likes to find bugs (and lots of them) hours before production.
- You are of the strong belief User Acceptance Testing should be saved until the most irresponsible moment (again, try a few hours before production).
- The developers in your company favor creating the most technical solution rather than the solution of most value for the customer.
What is Agile, anyway? Is it just an annoying buzz word for new age geeks (the kind that embrace principles and values over static practices). How did it ever become so popular? Doesn’t it only applies to the very small number of projects with fuzzy or changing requirements? Isn’t the worst part the way Agile fosters a collaborative environment AND ongoing communication with customers? Waterfall gods save us!
Choices, Autonomy, Expectation, Pressure at Work and… SOLUTIONS!
By Bachan Anand / Filed under Agile / November 16th, 2010
A self organizing and emergent system is sustainable.
Self organization grows autonomy
Autonomy necessitates choices and commitments
Choices leads to responsibilities
Responsibility creates too much pressure to succeed
Pressure breeds stress.
Stress yields failure.
Solution:
1.) Exercise autonomy with borders. Self organize under a context or vision, whatever is most important to you. Don’t be afraid to use time as a boundary ( SHORT time box/rhythm) in an effort to get results. When under pressure, simply acknowledge the situation and come up with goals to improve for the next (SHORT) time box. Consistently reflect at the end of each time box: what worked well? what can be improved?
2.) Have an environment that considers failure as a stepping stone. Nobody goes into a task with intent to fail. Why treat people in this manner? Come out of each time boxed boundary with a true belief that everyone did his best. As a result, commitments and choices will be made as a team not as individuals. The wisdom and emotional support of the group will be leveraged and maximized. Interdependence can be utilized to overcome the extreme pressure of expectations.
Most importantly work for a purpose and vision. Do all that you can to become fully engaged in all you do!
WORK is GOOD !!
Here are two video about Choices and emergent behavior that created internal dialogue that lead the above words.
PS I hope you get the message it should be a SHORT time box.
Reflections from Scrum Beyond Software event in Phoenix
By Bachan Anand / Filed under WORK is GOOD / September 28th, 2010
Go beyond names. Go back to values and foundation when in doubt with practices. Think beyond words and reflect on what a word mean to you. We can all be prisoners and be limited by the very names that made us discover our passion ( inspired by @tobiasmayer and @lyssaadkins)

Core of Agile and Scrum
By Bachan Anand / Filed under Uncategorized / May 5th, 2010
The deeper I practice principles and values of Agile and Scrum it makes me believe that these principles and some of the core practices can be used in non software development scenario. When I reflect on my own journey these are the answers that come to me:
Agile and Scrum principles,
- Show the effectiveness of breaking down your goals into small stories that can be achieved in shorter durations to gain success.
- Draw attention to the importance of taking a breather in between your work execution to reflect on quality of work and most importantly making personal commitments to improve them.
- Show the importance of collaboration between team members and customers to be successful.
- Highlight the importance of informing your customer what you have done during regular intervals to increase transparency and receive feedback.
- Point out the importance of delivering business value at regular intervals to stay competitive
- Create an environment that allows you to focus on work that provides the highest business value.
- Help you find a rhythm in your work and strive for continuous improvement.
- Help limit the impact of failures by time boxing work to small duration and provide you opportunity to reflect on them and make necessary corrections.
- Draw attention to the importance of laying down a product vision and roadmap.
- Provide opportunity for people who are doing the work to self organize around the work, determine the highest value and excel in creating it.
- Promote transparency by allowing the team’s goals and tasks to be visible to team members, management and business.
- Create an environment where team members’ failures can be discussed openly.
- Draw attention to the importance of business by determining business priority.
- Promote creativity by giving them autonomy on how they do the work.
- Foster courage by providing an environment where early failure is promoted to achieve long term success.
- Support the emergence of strong design and architecture by allowing continuous improvement of the design.
- Keep the team focused by planning work only for shorter durations.
- Commit to short increments to avoid changes to scope of work that is already in progress.
- Embrace change in scope and business priority for items that are not in progress.
- Promote consistency and quality of work by clearly defining what DONE means.
- Provide an environment where leadership can focus on strategy and vision and not worrying about how the team does the work.
- Create an environment that embodies quality by working at a sustainable pace.
- Keep the team members engaged by clear and consistent communication of goals from management.
- Allow transparency at all levels to expose company purpose and goals to everyone in the organization.
- Create an environment that encourages open discussion about challenges and leaving room for situations to take a political turn.
- Expose disruptions and eliminate them so everyone can focus on the work they are responsible for.
- Keep quality consistently high by finishing up work in smaller chunks to the committed quality before moving to the next set of work.
- Visualize flow of work and make each other aware of what the team is focused on to promote compassion among the team members, management and business.
What do Agile and Scrum principles mean to you?
