It depends a lot on the project. Usually it starts with a team standup and walking the physical wall. The usual one minute status on the story, and in case of any impediments, a call out. Regular checks on emails, chats etc. may follow.

Most of the day goes into pair programming on the planned stories for the sprint. Usually TDD is preferred, but the pair decides their style of working. Tests are a must. Usually there's a build monitor to track test failures.

Tech huddles are called in case of important technical decisions or if there are hurdles. Stories start with a Kick-off to dissect all aspects of it in detail. These are attended by business analyst, quality analyst, tech lead and the pair.

Dev box testing helps catch defects early. So on and so forth. There are sometimes evening meetings with clients depending on time zones, availability etc. Features are demoed in this meeting to get feedback even before they are deployed to Dev or Staging.

Overall the org is unstructured but empowering. There's very little hierarchy.