Sprint review today. I want to talk about it.
The client is the PO. Technically.
But not really. The PO position is broken into three groups:
1. The client, who provides specs and knows what we are building. Really do.
2. Management, who pushes the team like management should.
3. Functional design, who takes the requirements from the client and turns then into useful user stories and acceptance criteria.
What this means: we first do a design demo, to tell the client about items designed in the last two weeks. We do an estimation session (planning poker) away from the client. This time, I asked the functional to be there and that was very helpful.
So, today, we did:
1. Design review
2. Dev review
3. Planning session with client.
4. Retro.
The first was at 11 AM. The retro ended at five. Between noon and two, I wasn't in ceremonies.
I have essentially been talking in front of the client, or getting others to do so, for most of the day.
I am tired. And that's ok: it's a big thing and we do it every other week. Tomorrow should be easy.
Not sure if there is a better way to structure this. Having so many ceremonies at once gets them done, but dang am I tired.
Subscribe to:
Post Comments (Atom)
The sheer quantity of Product input makes me wanna weep tho.
ReplyDeleteI'm feeling confused by the amount of design it seems like you do. Is there really a substantial amount of new design every two weeks? How is that sustainable?
ReplyDelete"3. Functional design, who takes the requirements from the client and turns then into useful user stories and acceptance criteria." -- this sounds like the closest to a traditional product owner, with a soupçon of Account Manager thrown in. How many clients are in the mix here?
ReplyDeleteSean Leventhal "Design" in this case means user stories, acceptance criteria, and some nonesense. Not, like, designing designing.
ReplyDeleteRabbit Stoddard The Client is very large, and represents an important part of the goverment. From them, we have a PO, several SMEs, and a bunch of others. The Functional design folks are employees like the rest of us.
William Nichols traditionally, the PO does all the user story and AC writing. I can't imagine having backlog refinement without that person in there owning it- they're the ones who are presenting what they've written, after all. In our org, they own that (we do a SAFE Agile thing).
ReplyDeleteOk. It might feel less agile... But... Could you do more of 1 and 2 offline in a slack channel or through code review tools or even in some shared document? Not omit a conversation, but make everyone do homework and get to the decision points faster?
ReplyDeleteI've been talking about doing the Design Review without it being a meeting, yeah. We're not there yet, but I hope we get there.
ReplyDelete