As a new PM/PO I need to do Sprint Planning. As I understand, Sprint
Planning is also known as Sprint 0 as nothing is delivered for
customers or for internal teams to test/look into.
This is not correct.
Sprint Planning is a regularly occurring event. It happens once per Sprint and involves the entire Scrum Team. The purpose is to review the Product Backlog, determine what Product Backlog Items can be completed in the Sprint (basing this on a forecast of the team's capacity and any kind of prior performance data - this gets better over time), and starting to further decompose the work and develop a plan for achieving it. The outcome of a Sprint Planning is a Sprint Goal and a Sprint Backlog.
Sprint 0 is not an official part of Scrum, but it roughly correlates to what other models call, among other things, inception. This includes work such as forming the team, defining the initial scope, identifying an initial architectural strategy, developing release strategies and plans, aligning on a common vision, and related activities to align the team with the product, a portfolio that the product is a part of, and the broader organization. Unfortunately, Scrum does not have an explicit way to handle these activities.
As a PM, during sprint planning, I need to do the following: 1.
Business requirements 2. Come with product backlog and user stories 3.
High level vision and outcome we except 4. DoD for each story 5. Other
Some of these things should be done well before a Sprint Planning.
The definition of requirements and capturing them as Product Backlog Items (in an appropriate format, which may or may not be User Stories) is an ongoing activity. The refinement of the Product Backlog is also an ongoing activity for the development team and the Scrum Guide recommends allocating about 10% of the Development Team's capacity for refinement. This type of work is probably a full-time job for the Product Owner.
The Definition of Done is not typically defined for each story, but rather a set of criteria that is applied to each Product Backlog Item, plus the Sprint's Increment as a whole.
I was told that Sprint planning can take 4-8 weeks. Is this true? If
yes, during this time, what would the development team do? Create
frameworks, checklist and so on? or can they be pulled into other
A Sprint Planning event is defined as being "time-boxed to a maximum of eight hours for a one-month Sprint" and "the event is usually shorter" for shorter Sprints.
However, with respect to inception activities, a survey from 2013 ran by Scott Ambler found that the average agile team spent about 4.6 weeks in inception activities. I would say that 8 weeks would probably be pretty excessive, but roughly a month wouldn't raise any serious concerns. It would depend a lot on the environment and contextual information, though.
Does scrum master, PO, Dev team get into sprint planning?
Yes - Sprint Planning involves the entire Scrum Team.
We work in distributed teams how does one carry out the sprint
planning given the time zone difference. Should everyone (scrum
master, PO, dev team) get into a call (audio or video) to discuss
product backlog and perform product grooming? OR can this be done via
google docs where I throw in all the info and the dev and other
stakeholders look into all this and make changes or leave comments. I
feel latter (google docs) system would be inefficient.
Having people be online and having discussions is the preferred option, not only for Sprint Planning, but all of the Scrum events.