Culture for Great Team and Results: The Core Protocols
IntermediateYour team can be ten times better.What does that mean? That means your professional team can accomplish 10x more work, do it with 10x more quality, 10x faster, or with 10x less resources. Your family can be 10x happier. Your school can be 10x more effective at helping people learn. Your community group can be 10x better at making life better for the people it serves. Even you yourself can be 10x more effective at getting what you want.In other words, you can be great. Your team can be great.GreatnessCan you say these things about your teams?
The Core Protocols are one way to make teams that have these characteristics.Some of the things you’ll learn:
- My projects are completed effortlessly on schedule and in budget every time.
- Every team I’ve ever been on has shared a vision.
- In meetings, we only ever do what will get results.
- No one blames “management," or anyone else, if they don’t get what they want.
- Everybody shares their best ideas right away.
- Ideas are immediately unanimously approved, improved, or rejected by the team.
- Action on approved ideas begins immediately.
- Conflict is always resolved swiftly and productively.
- Results-oriented behaviors,
- How to enter a state of shared vision with a team and stay there,
- How to create trust on a team
- How to stay rational and healthy
- How to make team decisions effectively, and
- How to move quickly and with high quality towards the team’s goals
The Smell of Agile CultureGurpreet Singh
schedule 1 year agoSold Out!
Culture is the most widely talked in societies, religion, race, region and workplaces as well. Organizations are the Second Homes as people spend their better half of their time in their offices. Hence, Culture is an integral part (good or bad) for driving the happiness of clients and the colleagues, and success for the products/projects and growing / sustaining business. Agile Implementation is highly dependent upon the Culture of the Organization.
How does a Manager transition to the Role of a Product Owner? What happens to a Product Owner who wants to retain his control on the team rather than working on the Product? Some developers think that Scrum, for instance, brings a lot of meetings and these meetings are a waste of time. The Scrum Master’s role is not a full time role in many companies. Leadership thinks Agile can solve most of their issues without even knowing the root causes of the issues.
Come to this talk and we will discuss a selection of real-life experiences to tackle these cultural issues and the actual/suggestive steps taken to improve the culture of organizations.
Presented at Qcon Rio International Software Conference: