Does scrum forbids project plan?

The Scrum Guide says that "Each Sprint may be considered a project", and that "The Sprint Backlog is a plan".

There can be many kinds of planning in Scrum, including product planning which the Product Owner may manage using the Product Backlog.

I believe that the Product Owner can use the Product Backlog (with other elements) to make a forecast about the future. We could consider this forecast as a plan as long as we know that it can change.

I agree with Jose. The key differences between plans in waterfall and plans in agile development are these:

1.) In agile development, we understand that a plan is not a commitment. Plans have to be adapted continuously in order to keep up with reality

2.) We only do as much planning as is needed in any current stage, so as to prevent waste. It is an illusion to believe that now (January 2018) we can plan what's happening in December 2018 on a week-level. Thus, the further into the future a plan goess, the less detail it should have, so as to not imply a certainty that isn't there.

If your scrum development is part of a project, then you need a plan - not for the scrum itself, but for the project.  That plan should have a set amount of time and budget for scrum development.  Developing that estimate should be done in collaboration with the scrum team.  The business case determines how much you can afford and how much time you have.  Scrum will get you the most it can within those constraints.  MVP definition is crucial.  A self-directed scrum teams handles the PM essentials at the level of development - risk, communication, schedule, cost, stakeholder management - it is awesome at that level.  But it does not manage these for the overall project - how could it?  

There are also many aspects of the project that are not development- initial business case creation, market analysis, marketing plans, roll-out plans, organizational change management plans and activities, project (not scrum,not development) risk identification and management, training plans, vendor selection and management, contract negotiations, etc.  People often try to scrumify these other activities. If it works and adds value, fine, if it doesn't then why are you doing it.  Scrum is not a silver bullet.

If scrum exists apart from a project, then a project plan makes no sense. If you have a scrum team that is supporting an existing system, your product owner can set the priorities and the team can just chug away scrum after scrum delivering the most important next set of features.  You don't need a PM to do that and you don't need a project plan.  Many organizations try to projectize everything.  It often just add unnecessary overhead and frustration. PM is not a silver bullet. 

I am a certified PM professional and Scrum professional.  They are tools that should be serving you to achieve your organizational goals.  Use them when they provide benefit.  

Hello All,

How do we consider Risk plan, BCP , resource plan, estimates for the scrum projects. does this required in the Scrum plan ?

Thanks in advacne

What is "the Scrum plan" you mentioned?