Three Pillars of Scrum

So, I've been observing Daily Stand-up meetings of other teams. (guilty as charged!) in my defence I did it out of concern because my peers from other teams have been unpacking their frustrations to me about the miscommunication between developers, testers and business analysts. (Sub-teams within a scrum team. That's a topic for another day) I immediately got the sense there was no common understanding. I noticed behaviours that do not align with the empirical process control:transparency, inspection, and adaptation.

Transparency:

All the items or work must be visible to those responsible for the outcome and by this I mean the cross-functional team (consisting of developer, tester, business analyst). Transparency requires those aspects be defined by a common standard so observers share a common understanding of what is being seen, so those performing the work ( The Team ) and those accepting the product ( Product Owner / Lead Business Analyst / Business Stakeholders) must share a common definition of “Done”. Everyone is on the same page.

Inspection:

This basically means the use of a common Scrum board for the team ( I've seen stand-ups where team members just do a status update and there's no board in sight... ) Product Backlog Items are updated with more information during grooming as more information is arises from the product owner/lead business analyst and other stakeholders. This will lead to new better/more accurate effort estimations. Inspection and approval of the Deliverable by the Product Owner and the Stakeholder during the DEMO/Sprint Review and Validate Sprint process.

Adaptation:

If a Product Owner/Lead Business Analyst determines that one or more aspects of a process deviate outside "conditions of acceptance", and that the resulting item will be unacceptable, the work item must be adjusted. An adjustment must be made as soon as possible to minimise further deviation. This requires good working relationship between team and product owner.

Scrum prescribes four formal events for inspection and adaptation:

Sprint Planning Daily Scrum Sprint Review Sprint Retrospective

When reading this you will notice I tend to refer Lead Business Analyst / Product Owner. I know Scrum only recognises only 3 roles - Product Owner, ScrumMaster and The Team. However, there are some companies that do not want to take the plunge and fully adopt, they would rather keep their fancy titles and top-down structure and use scrummish lingo.

My only question is have the people who are playing those roles read The Scrum Guide?