It varies from team to team, org to org. My experience is atypical since the scope of the project is large and I take on work from several teams that work on it. Budget determines what features are worked on and when. The orders will come from up above saying we want X feature. The system engineers and architects will (usually) analyze and come up with some design. Those get put into user story format and leading up to a new development cycle there will be user story reviews. My calendar will generally be packed with meetings for 3-5 hours per day, 4 days a week, for several weeks. Not all meetings I need to be at but sometimes it's good to see how people with experience operate in those meetings. Once story points are recorded and the cycle starts you work on your stuff.
During the cycle there's status meetings multiple times per week. There's also some miscellaneous meetings here and there. Between meetings and programming I'm usually fixing issues with my development environment because dependencies changed and this breaks my builds. Sometimes I get handed a higher priority task that draws my attention away for a few hours. But like I said, my experience is atypical. I have to have my hands in a lot of parts of the project just by the nature of my role and the team. We don't practice agile correctly so that leaves us wider development iterations, but also the tasks are generally more complex.
