For Agile, any information on having a Scrum Master and Project Administartor, and not have a Project Manager?

Interesting concept, there are prior posts asking if the Scrum Master and PM were one and the same. Assuming they are definitely not, here is my response. The Scrum Master's job is to execute according to the agile methodology and help guide and direct the team as they progress through sprints. They have a role that in my view equates to only a small portion of what a traditional PM would have. Taking that into account, if the assumption is that the Project Administrator would take on ALL the other tasks that a typical Project Manager would: managing budget, scope, communication with stakeholders etc. then it may work. If there is no Project Administrator or they're role is relegated to only the internal "admin" tasks of the project, then the project would be in jeopardy no matter what the size. You may be able to get away with it on very small efforts, but to be truly successful you must have the Scrum Master and the Project Administrator both working their role, and then some, to achieve the same success because neither role in and of itself carries the weight of burden for project execution like a PM does.

Are you talking about the roles of a project manager on a traditional project and how they apply to agile? They all still apply, they are just performed by different people. Here is a short article that explains it well.

https://www.mountaingoatsoftware.com/agile...ject-management

I think I've seen at least one flavor of agile that named the role of project manager, but I don't recall which. You are more likely to see a project manager on a hybrid project, where development is done iteratively, but there are a lot of other parts of the project that need a more traditional approach. In cases like this, the Scrum Master and Project Manager can be two different people.

Agile or not, I have seen the number of hours a project is expected to carry as a basis for the requirement of an official PM. Haven't really seen that work out, but those criteria were set as the model to follow.

You ever, ever have a project manager assigned to an initiative no mattter the approach. But you have to remember that project manager is a role and because of that you can name the role with other name. Regarding to methods belonging to Agile you can find some with project manager role with a different name and others (like DSDM) where the role name is project manager. But you ever, ever has one.