The PM Journal | Log 03
As I said in my previous post, we have a significant feature of delivery in the next two sprints for a huge client. Today we had to refine a critical and big story to see if we would be able to prioritize for Planning.
The team estimated it as 13 story points due to complexities, which might be pretty big for one sprint, I’m calling this as option one. Then we discussed ways to split it, and that was none. So I asked if we could simplify the increment but still — of course — delivery value to our end-users, and gave them a second option. Which they all agree that it would be less complex to develop.
So far, so good. What happened is, as this feature is part of another team’s priority and we’re helping them with this deadline, I had to double-check with their PO — as he has more contact with the client’s requirements — and he gave me a third option to raise with our team the complexity.
Which in terms of value, I still believe with the second option, we would have a more valuable piece that relies on every requirement from the client. But, as the other PO is responsible for this account and agreements with his client, I trust that his third option can also provide value.
I came back to our team and asked which of these options would be less complicated. Of course, the group raised many questions, and we won’t be able to clarify all we need by the time we have planning.
It’s hard enough to work with client’s deadlines, the team is in a considerable pressure, I am in significant demand. We all get a sense of urgency.
After all these discussions, I had to reorder the priorities to set both expectations (client and company). So I got the most valuable product possible that the client would still agree with and also the PO from the team we’re helping, and I set the next two sprints expectations with the team during planning.
Now we have a feature in which the user will need to do more clicks, but it is a workaround for the first deadline until we finish the rest of the requirements. What’s vital for you to consider is always think outside the box and which work-around the user has to will not limit the usability either the functionality and still has value.
Nothing new here, everyday scenario. But it’s good to share different ways to think of solutions. This was one that worked for now.
About the 13 points story, we will refine again and have more technical discussions. But we’re all set for the delivery either way.
(Please notice that I’m not native in English and I apologize for mistakes)