Questions on SCRUM guide
I am new to SCRUM and just started reading SCRUM guide. Here I have 2 questions to clarify.
In Spring Planning section, it says:
... The Development Team usually starts by designing the system and the work needed to convert the Product Backlog into a working product Increment....
Q1. Does this mean Development team does designing work on Spring planning meeting ? If not, would you explain?
In Sprint Review, it says
... The Product Owner explains what Product Backlog items have been “Done” and what has not been “Done”; ....
Q2. According to the reading up to Spring review, Product Owner won't have formal meeting with Development team as only Dev.team is having Daily Scrum meetings. This above sentence is somehow conflicting or confusing to me. I am wondering how will Product Owner have clear info about what has "Done" or what has not?
Q1
Yes, the Sprint Planning Meeting contains 2 topics : What will be done ? How will we build it ?
The "How section" is a good place to have high-level design work with the full Dev Team.
Q2
The PO should work with the Dev Team during the Sprint, as required. Generally speaking, when the Dev Team feel that an item is done, the Dev Team should ask a feed-back from the PO as soon as posible.
The PO mut not "discover" the increment during the Sprint Review. The PO is part of the Scrum Team, not a distante stake-holder.
I agree with Oliver.
Regarding with the second question, I would also like to add that,
"The PO is the sole person responsible for managing the Product Backlog", and as PBI's are selected for the sprint by the dev team, they still belong to the product backlog (is not like the items move from the PB to the sprint backlog). The PO as responsible of the PB should always inspect it by performing refinement activities of PBIs and if necessary add or remove work without altering the sprint goal. All this by providing transparency and in accordance to the definition of done.
The PO should collaborate constantly with the DT and vice versa. When the DT is "done" with a PBI, the PO should know it and performs a verification of that individual PBI. This is where user stories prove very useful as they can have acceptance conditions that should be written by the PO and be transparent in addition to the sprint definition of done. If the PO consider a item not done by its acceptance condition then rework can be performed before reaching the the sprint review.
hope it helps.
Thanks guys!