The project is defined in PMBOK as part of a fixed volume, duration and budget. A project abandonment is defined as a violation outside one of the three sides of this “iron triangle”. Scrum is a set of principles and several specific practices designed to work with all kinds of knowledge based on Agile values ​​and specifically designed for development efforts that may not be projects, or may have a flexible scope, duration or budget.
You are right that Scrum deals with only a few aspects of the software development process, such as planning. It defines only a few roles, meetings, and artifacts to keep it as flexible as possible. Scrum can and should handle parts of the value stream outside of software development itself. However, as you mentioned, this does not apply to many things, such as software development practices and case studies.
Often the standard Scrum solution is to “let the team decide” on issues that are not directly specified by Scrum. Often the guidelines for dealing with such issues come from other cultures and values ​​or systems of principle in the Agile world, such as XP or lean software. Other cultures providing useful materials for Scrum teams include Real Options, Inmentment Funding Method, Evo.
Some of the PMBOK materials may be useful to the “project manager” or software in the Scrum team, but care must be taken as the PMBOK material implies a completely different value system than the one on which Scrum is based. It's usually best to look for solutions in an Agile culture. Some of the PMBOK materials are still used in a flexible context.
If you are looking for “flexible project management” mailing lists, you will find many thriving communities discussing such topics.
Kurt
source share