feedback loop and inspect & adapt

> what could be considered a feedback loop in scrum?
> how does the feedback loop relate to inspect and adapt principle?

A Sprint is one example of a Scrum "feedback loop". In this loop, a product is delivered iteratively and incrementally. Each Sprint therefore provides a discrete opportunity for feedback and for improving the product and adjusting the process.

The principal opportunities for Sprint inspection and adaptation are the Review, Retrospective, and Planning sessions. Feedback might come from:

- the Development Team (regarding the efficiency of development practices),
- the Product Owner (regarding the applicability of the evolving product and its Return on Investment), and
- the Scrum Master (regarding the optimal application of the Scrum Framework).

> can the daily scrum be considered as a feedback loop? 

No, in this narrower case the feedback loop would be the day itself. The Daily Scrum is a suitable juncture (event) at which daily work can be inspected and adapted.

In principle inspection and adaptation should be conducted by those who are closest to the work, and at the closest time to the work being done.

I think the cycle that runs from Daily Scrum to Daily Scrum could be considered a feedback loop.. not on the product, but on the process. So, I would consider the DS to be a feedback loop.

Agree, Daily Scrum is an Inspect & Adapt Event and I see it as a feedback loop on the progress In the Sprint.

to me, Ian's answer makes most sense, since Daily Scrum is a short time-boxed meeting during which each Dev Team member answers 3 questions only and makes a plan for next 24 hours. The others listen (inspect) and adapt their plans according to what they hear.

Naturally they will discuss all details, give feedback outside this meeting.

although, if i were sure of this answer, i wouldn't have taken it to this forum.

The three pillars - Inspect, Adapt and Transparent.

The Transparency pillar is the key for "feedback (loop)" which would evolve during all scrum meetings (that may include daily meetings as well I believe). The more the transparency the team demonstrates the more feedback they'll receive which helps to inspect and adapt.

The other two are where SCRUM team themselves / or out of planned and offline discussions learns their mistakes and rectify.

I think we can  consider Daily Scrum as "Feedback (loop)"

bellow are the things we ask or discuss in the daily scrum :

How did we progress yesterday?

Are there any problems?

What should we do today?

Are we on track to deliver all the stories we thought in the sprint? If not, what should we do about it?

Do we need to regroup somehow?

Do we need to go back to the product owner to adjust the scope of the sprint?

Most of the above points is feedback base on which we have adjust our plan.