The talk covered the following points.
We will select one model and do Retrospective for the session.
Replay Pakistan Agile Scrum Exchange (PASE) talk recording: https://www.youtube.com/watch?v=szkODE9Q004
Are you using any metaphor in your Retrospective meetings?
Using Metaphors in our conversations can help us to understand an object, conversation or action from a different perspective. They can also serve as a powerful tool leading us to think in new or a different way.
This post describes a Plane Refutro Model, a model to talk about possible improvements and future uncertainty in particular.
In the Agile world, ScrumMaster and Agile Coaches are often referred to as a gardener that helps a seed grow to provide shade and/or a fruitful tree. You need to prepare the ground, remove weed and give enough nutrition for good growth. At workplace, this resembles creating a safe environment for a person to do the work.
After getting inspiration from High-Performance Tree metaphor, I thought about why not create a retrospective model from it. You can use this retrospective model for Sprint or any other project closure as well.
Reading time (8-10 mins)
In this post, I have shared my thoughts about getting value from different frameworks while keeping the focus on achieving organizational goals.
Question: What is more important for you and your organization?
a) Being Agile (Leadership Agility, Organisational Agility)
b) Achieve Organizational goals (More sales, Happy customers and Teams)
Please go ahead and share your thoughts in the comment section, meanwhile, I can share what are my thoughts.
When working in an agile team, what’s the first thought that comes to mind when you hear “Team Velocity“, or “Sprint Burndown“? and yes, both are related to Estimation.
I’ve experienced that some agile teams found estimation useful while others considered it less beneficial to the team and process. However, for the management, perhaps it is important to know how the team is progressing on the Product/Sprint Backlog and achieving Sprint Goal. Thus “Team Velocity” and “Sprint Burndown” are there for planning purposes in terms of next Sprint velocity, release planning, resource planning, budgeting, and XYZ.
A facilitation guide for Team Building for Distributed Agile Teams (DAT). It might be helpful for someone working with remote teams and want to break the ice among teams.
My philosophy is that to build innovative software products, a company need to focus 
and allocate time for building Team(s) as well.
Yes, that’s what I think when building and working with Agile Teams, both co-located and remotely distributed. It is the Psychological, not the Physical distance. It is a great interest for me to understand Team dynamics and foster psychological safety as well.
Have you worked with Distributed (Agile) Teams, what was your experience, what did you like most about it and what were the challenges?
For me, I have worked with remote teams earlier as well, however, recently I have started working extensively with Distributed Agile Teams and the experience has been so far fulfilling and really interesting. I am working as Agile/Scrum coach, and building the sense and feeling of “Team” for people sitting in the remote location is challenging and exciting as well.
Coaching a Potential 