The Scrum Master focuses on the development process and mentors the Scrum team. The key responsibilities of the scrum master are:
Maintains and removes impediments Manages the Scrum process, making the process work Plans the release Plans the Sprints Shields the team from external interfaces Facilitates Scrum meetings as requested Ensures crystal clear communication among everyone involved in the project
Project managers are responsible for the overall communication regarding the project (not just the development portion of the product). They’re the primary single authoritative source of information to ensure a shared understanding of all parameters: Scope Cost management Timing Assumptions / constraints Risks / issues Resources Quality Special considerations / exceptions Development methodology considerations Team members and associated roles and responsibilities Policies and procedures
Alexandre HerrmannIT Director| Computer OptionsCorona, Ca, United States
In a simple way: Scrum Masters focus on the product and process to "make" de product.
Project Managers focus to ensure that all products are delivered on time, budget, quality, scope and also manage resources, risks, contracts and stakeholders to maximize the result of the project. Saving Changes...
Sergio Luis ConteHelping to create solutions for everyone| Worldwide based OrganizationsBuenos Aires, Argentina
Read the definition of both roles. Scrum Master are in fact Project Manger with other role name. Saving Changes...
Jerry DolvinManager Program Manager| FlightSafety InternationalSaint Peters, Mo, United States
A Scrum Master leads his team to complete a detailed requirement and its verification in a fixed amount of time and cost. The SM does this repetitively every few weeks or so until told to stop. This level of development is very akin to a WBS work package for EVM, short in duration and well defined.
A Project Manager leads the team to ensure ALL the project requirements are verified to the customer's expectations within the time and budget available.
For most projects, that include more than just software elements, satisfying all customer requirements can only be achieved with a overarching WBS-based project Waterfall plan that may include nested Agile software development activities. Even if Agile is employed for software development, a customer may still have a minimum set of system-level software requirements (aka Software Requirements Specification) that Agile must complete while still satisfying other project activity dependencies, such as system level test events. Managing these overarching customer system requirements and dependencies is best served with a PM's Waterfall plan. Saving Changes...
