How to formulate good/proper sprint goal ?
Hi,
another question for you, today.
Let assume that we have 1 month spint. It's one of the begining sprints, so the project isn't advanced. In next sprint PO decided to take some tasks, which creates database connections. Other tasks are for very initial user interface, which isn't connected with data yet. PO and team members saw that there is some "time space" for maybe service preparation. At present "products" of those tasks isn't strong related and dependent each other.
And now, the main question.
How to formulate good/proper spirnt goal for this spirnt ? Should it "contains" all tasks ?
A good Sprint Goal makes the selection of work coherent. That means it gives team members something valuable to commit to. It also means it gives the whole team something to focus on, and a reason to work together as a team so an increment is delivered which is fit for release.
Considering the selection of work, will a potentially releasable increment of value be delivered by the end of this Sprint?
Ian, thank your for you time and patience:)
In this case (which is actually very close to some sprints where I’ve been as a developer) probably we can’t release whole increment. Maybe only that piece related to UI - as client demo.
Hmm but now I’m seeing that maybe tasks wasn’t properly choosen.
But, of course if I can ask, what you’ll do in that case ? On sprint planning SM should suggests other tasks ?
The SM needs to make sure that the rules of Scrum are understood and properly applied. This includes explaining to the team that each Sprint must create an increment of release quality, and the plan of work (i.e. the Sprint Backlog) should satisfy that purpose.
Big thanks for you for that explanation. It’s so easy and obvious, but still I have some doubts in that cases. I’ll remember your answer.