Designing Environment to Elevate Engagement
Outline/structure of the Session
- Agenda and Intro - 2 min
- State of Employee Engagement. Survey Results - 3 min
- Traditional engagement approaches and implications - 5 min
- Why create environments to engage? - 5 min
- The Science (Neuro-science, Psychology) of Engagement - 5 min
- Measuring Engagement - 5 min
- Strategies to create environments that elevate engagement - 60 min
#1 - Expression
#2a - Clarity
#2b - Table activity
#3 - Responsibility
#4 - Feedback
#5a - Fun
#5b - Group activity (Through a quick 5 minute fun activity I will demonstrate how quickly and simply a facilitator change the group dynamics, energy and engagement of the group. This activity will be loud and cheerful)
#6 - Surprise
- Q&A - 5 min
PS: I've been presenting on the Science of Engagement, Customer Engagement, Employee Engagement topics for few years now. I've presented this session at 4 public conferences / user groups and few in-house groups (half day and full day workshop) in India and USA.
PSS: Alternate to a 90 min workshop, I would love to do it as a evening keynote in a 45 / 20 min talk. However during this I'll only cover 2 of the 6 strategies and no exercise.
- State of Employee Engagement. Survey Results and Implications.
- The Science and Psychology of Engagement
- How traditional engagement approaches fare today
- Strategies that help create environments that elevate engagement across the generations
ScrumMasters, Agile Coaches, Leaders, Anyone interested to create highly engaging environment
schedule Submitted 1 year ago
People who liked this proposal, also liked:
Richard Sheridan - Build a Workplace People Love – Just add JoyRichard SheridanCEOMenlo Innovations
schedule 1 year agoSold Out!
The CIO invited me into his office and closed the door. Before he took me for a tour of his operation, he had a few stories to share. Important stories. Last year’s project was a disaster. Late, lots of quality issues, in short, a failure in every dimension. His boss, the CEO, had just presented him with a very personal ultimatum: deliver the next project by April 4th, "or else".
"Or else what," I asked?
His team was burned out and scared. They were a hard-working and dedicated group, but fear and demoralization had set in and he didn't know what to do next. That’s why he wanted to talk to me, he had heard things about my company, things that seemed too good to be true, but he had to hear them firsthand. He wanted hope, inspiration, and a practical way to get there.
I told him about my own journey from joy to fear to disillusionment back to joy. It was simple, but, of course, simple isn’t easy. I wasn’t sure he and his organization were ready; "manufactured fear" is a powerful drug.
In this talk, I will share with you what I shared with him. I will explore what an intentionally joyful culture must choose as its focus. I will discuss what joy looks like, feels like, how it is organized. Along the way, you will be confronted by paradoxical approaches of how workplace noise increases productivity, how two people at one computer outperforms hero-based organizations 10-to-1, how rigor and discipline emanate from a shared-belief system, how transparency conquers fear, how all of the disciplines you study including agile, lean, and six sigma when done well are really about building human relationships at the intersections of business and technology, between project management and software development, between development and design and how quality can be a natural result of a team built on trust. This is not a theoretical talk, but rather a talk built from well over a decade of experience of leading a team focused on “the business value of joy”. There will be lots of room for discussion with the audience. The audience will begin to understand why thousands of people make the journey to Ann Arbor, Michigan every year to see The Menlo Software Factory firsthand, and why so many more are reading about it in Joy, Inc. – How We Built A Workplace People Love.
Ram Srinivasan - More with LeSS (Large Scale Scrum)Ram SrinivasanAgile Coach and Certified Scrum TrainerIndependent Consultant
schedule 1 year agoSold Out!
How do you effectively do Scrum when you need multiple teams to work on the same product? What kind of patterns and structures should we create to support empiricism and self-organization at scale? And how do you get started?
This session explores these questions by uncovering the rules, principles and guidelines behind Large Scale Scrum (LeSS). Ram Srinivasan also discusses the two LeSS frameworks and provides guidelines on which one may be more appropriate for you. You will learn how the role of management changes in a LeSS organization. Ram also will share his success and failure stories and will provide guidances on what will make your LeSS adoption more successful
Virender Kumar - Are Test Coverage Measurements Unnecessary in TDDVirender KumarSoftware ConsultantConsultant
schedule 2 years agoSold Out!
TDD is based on the premise that automated test is written before we write actual code. In such a scenario, we should be getting very high test coverage by default. I will discuss whether test coverage metrics have any significance in TDD paradigm using a sample program.
I will present an application developed using TDD from scratch. Using this application I will try to answer following questions:
- Do we get very high test coverage by default.
- Do test coverage measurements bring in any value in TDD
- Which coverage metrics might be useful