When Product Increment comes into existence...Before Sprint Review meeting or after. Moreover, should peoduct can be release before Sprint Retrospective???
Hi, the video is great and shows the 'happy path'. What are the anti-patterns around PBI's that impact on the increment not being an increment? I am thinking around PBI's that cannot form a Product increment on their own, low level horizontally sliced stories which mean working software cannot be shown in the Sprint Review, just a database etc. Bought your book earlier this week btw, it is awesome!
The DoD should span across the lifecycle of the team and becomes more strict over time. Therefore, it us universally applicable to all PBIs that the team works on. It is not specific to a single PBI.
is it safe to say the developers must produce useful ASPECTS of a useful increment THROUGHOUT the sprint whereas the scrum team must produce a useful increment at the end of the sprint?
I love this format a lot, helps me visualize how it’s done! Thanks R&T!
Love the session, I learnt something today 😁
Glad you enjoyed it!
Love this format!
Thank you! We will keep trying new things like this.
Question: Shouldn't we have a DOD or some acceptance criteria for a Sprint Goal or it just relies on DOD of each PBI?
this video was really helpfull
When Product Increment comes into existence...Before Sprint Review meeting or after. Moreover, should peoduct can be release before Sprint Retrospective???
Question: each pbi that meets the DOD should be deployed to be consider part of an increment?
Nice session! What board are you using?
Thanks! We are using mural.co/
Hi, the video is great and shows the 'happy path'. What are the anti-patterns around PBI's that impact on the increment not being an increment? I am thinking around PBI's that cannot form a Product increment on their own, low level horizontally sliced stories which mean working software cannot be shown in the Sprint Review, just a database etc. Bought your book earlier this week btw, it is awesome!
Can we have a DoD for the Sprint, not just a PBI?
The DoD should span across the lifecycle of the team and becomes more strict over time. Therefore, it us universally applicable to all PBIs that the team works on. It is not specific to a single PBI.
Is it mandatory that the product owner release the increment of working product at the end of every sprint?
It is not mandatory.
Individual pieces of puzzle that makes up the whole puzzle slowly
is it safe to say the developers must produce useful ASPECTS of a useful increment THROUGHOUT the sprint whereas the scrum team must produce a useful increment at the end of the sprint?