Why Your Team Never Finishes Products

Teams often focus on Acceptance Criteria as a means to gain common understanding.

Good stories have Acceptance Criteria, but we often focus so much on writing those criteria that we forget to tell stories. And the best way to gain a common understanding? Telling stories.

If your team doesn’t have a common understanding you’re usually getting the wrong things done, leading to incomplete products.

The Ideal Size For Product Stories

Jeff Patton has some great points about the ideal size for user stories in his book User Story Mapping.

A right-sized story from a development team’s perspective is one that takes just a few days to build and test.

That’s great for a development team, but what would the Stakeholders say?

A right-sized story from a business perspective is one that helps a business achieve a business outcome.

So is there a perfect size for stories?

The right size is the size that’s relevant to the conversation you’re having.

Don’t Forget To Prioritize

Like any growing company we put as many resources as we can towards reaching the goals we set. Our quarterly goals support our yearly goals and so on.

But like any fast growing company, priorities change to take advantage of new opportunities, many of which seem to appear out of nowhere.

This week I was reminded of the importance of reprioritizing. Already half way through this quarter I’m amazed by how fast important objectives just six weeks ago have already fallen in relation to more important things that have come up. If I had carried on to reach the goals we laid out last month our team would have missed some great opportunities.

Now that I have these listed by priority, how do I get them all done?

  • User sharding
  • Load videos/emails quickly
  • Load lists quickly
  • Load group account data quickly
  • Salesforce
  • 1:1 deliverability
  • Bugs
  • Analytics
  • Mobile
  • Gmail
  • Automatic user onboard (training)
  • Relationship scoring
  • Composer improvements
  • Improve integrations (Zillow, etc.) Q1