I have a team of developers who are relatively new to Agile and sprints (approx. 5 months now).
Every time I walk into their sprint planning session, I do not like what I see. It's absolute silence and we can practically hear ourselves breathing. The SM is the only person talking and tries to create tasks, one-by-one, for each story.
I try to encourage the PO and developers to ask questions, but I have developers who are very "passive" (not pro-active). No developer will voluntarily request to be assigned a task (like I use to do and have seen done by so many of my peers). They sit and almost wait to be assigned tasks (which was how it was before I introduced Agile).
Our sprint planning sessions are WAY too long (almost a full day) for a two week sprint. There is a lot of wasted time discussing things that should probably have been ironed out before the session by the PO.
My questions are as follows:
Other than a backlog grooming session, is there a formal meeting where the SM, PO, and I can pre-populate the tasks for each story?
We know we will need certain tasks, such as:
- unit tests
- functional tests
- load tests
- test strategy meetings
If such a meeting exists, what is it called?
If not, would this, in any way, go against the Agile methodology?
How can I get developers more involved?
I want them to be pro-active, ask questions, give opinions, to fight for tasks.
What can I do for motivation?
Any recommendations on what the PO could do prior to a sprint planning session?
I just want all the boilerplate work to be done before developers and others join the session. Having everyone sit through several minutes per story watching the SM create and name tasks, set the JIRA fields, etc. is entirely counter-productive.