I know Agile process is more towards giving features and making product robust than supporting documentation for everything.. But for tracking, in Scrum, do project managers need to maintain project plan and keep updating them?
Agile folks plan continuously, which is sometimes surprising to some folks who don't recognize the planning activities and artifacts.
The "product backlog" defining what will be in the next release is the big plan. The product or release manager can revise this plan beyond the current or next iteration any time he wants. It might literally be a stack of index cards.
The "iteration backlog" of what we plan to build in the next week or two is the small plan. We try to lock into that and avoid turbulence for the week or two. But we make a new one every iteration.
Tracking these plans is often as simple as a burn down chart. There are lots of other interesting metrics, but that's a pretty core measure of what we can expect to be done when.
And you're allowed to do any additional planning that's required. My work has always depended on numerous external partners, some of whom have long lead times (several iterations or even months) for delivering services. I don't find agile folks talking about this kind of dependency management often, but it can constrain how you move things about in the backlogs and can require another level of planning.
A good question is never answered. It is not a bolt to be tightened into place but a seed to be planted and to bear more seed toward the hope of greening the landscape of the idea. John Ciardi
The soul is dyed the color of its thoughts. Think only on those things that are in line with your principles and can bear the light of day. The content of your character is your choice. Day by day, what you do is who you become. Your integrity is your destiny - it is the light that guides your way. - Heraclitus