Teams, Coaching & Facilitation
3 Ways Google Creates a High-Performance Culture
A company doesn’t need to be generating millions in revenue to “hack” the fundamental principles that set the Google team apart. Here are the top three lessons every business can learn, and begin to implement immediately, from Google:
Retrospectives for Management Teams
Engaging top management in a recurring retrospective approach can result in long-term value in organizations. Retrospectives can help management teams to explore how they collaborate and cooperate. They can find out whether they should change something and decide on action points that propel the team forward and make them more productive.
16 Coaching Techniques To Help Your Team Overcome Resistance To Change
Many humans are creatures of habit. They like their routine and feel uncomfortable or hesitant when that consistency is broken. However, change is often needed in the workplace, and it’s crucial to get your team onboard.
There are many coaching techniques leaders can use to help overcome resistance to change from their staff. We asked 16 Forbes Coaches Council members to share their best approaches and why they’re so effective.
Tips & Tricks
‘Scrum is an awful project management methodology’
I admit it. We called our previous way of working ‘Scrum’. We thought that we had a business process that was suited for it. But our business process didn’t fit at all. On top of that we didn’t know what Scrum was about. We then moved to a different way of working which was adhering to the spirit of Scrum.
The Latest from Retrium
Retrospective Hot Seat
A great retrospective will lead to exciting ideas and innovative solutions. A bad retrospective leads….nowhere. In this episode from the Retrospective Hot Seat from our Expert Series, the facilitators reflect on the lessons they learned when a retrospective didn’t go according to plan and how they have incorporated these findings into future retrospectives.
Business Agility
Understanding What Good Agile Looks Like
Agile management began as a work of passion. It was born of a fierce desire felt by disgruntled software developers to set things right. Their Agile Manifesto (2001) not only succeeded in its modest goal of "uncovering better ways of developing software.” It had the unintended consequence of generating a candidate as the paradigm for 2020 management generally.
7 Techniques for Better Agile Requirements Gathering
Agile requirements gathering is a practice teams often perform on the fly. For example, developers update requirements between iterations -- if the software project has documented requirements at all. Some Agile practice purists balk at the word requirements. A lack of requirements could throw many business or technical processes into chaos, but Agile development thrives in an iterative approach. Agile trades certainty for adaptability.