Tag Archives for " continuous improvement "

Sep 04

Top 3 Team Genius Tips for getting the most out of Daily Standups

By Georg Fasching | Team Genius Tips

“The more the team offers and asks for help, the closer they will come together, and the better they will start working together. And the lower the risk for not achieving any goal for any planning iteration.”

Team Genius Tip 1: Work from Right to Left

Spend 15 minutes a day focusing on finishing items rather than getting distracted with starting new ones.

Team Genius Tip 2: Review Challenges

Be boldly honest about the changes, challenges and risks to pursuing your team goal, which in turn helps your team gel.

Team Genius Tip 3: Offer and Ask for Help

The more you ask for help, the more likely you will have a team that will succeed together.

This is going to be a frequent feature on this website and YouTube Channel for busy team development. Have any suggestions for future fast topics? Share in the comments below or sign up for my Team Dynamics Course. See you next time!

Aug 08

The big power of micro retrospectives

By Georg Fasching | blogpost

The big Power of MICRO Retros
Many product delivery teams know retrospectives (aka retros ) from their natural cycle of work, whether in iterations (e.g. Scrum) or in flow-based contexts (e.g. Lean Kanban). The more the team introspects the higher the value of the retrospective. How much they are prepared to do this, depends on where they are in the team development lifecycle. More about this in another article though. This one is about the extra agile version of retrospectives.

The inadvertent complacency of cyclical continuous improvement

We all know about the concept of continuous improvement. Sometimes when we get settled in our ways our minds are left believing that having retrospectives on a regular basis is all that’s needed to continuously improve. Well, it’s certainly a good start. The thing is, most teams only improve their ways of working in retros, and people even either not think about improvements in between retros or defer offering improvement suggestions until the retro. So as a unit the team can be somewhat complacent in the continuous improvement department, because the next proper retro will come eventually.

Continue reading