Every project falls somewhere on a spectrum between extremes of short-term, get-it-done-ism and eternal, future-proofed longevity. Unfortunately, while you may have a ballpark sense for where a project fits on this spectrum at the outset, each user story needs its own consideration. Working out the right tradeoffs for each of these stories is the project.
Every Agile project needs user stories. But where do stories come from? I’m not asking who types the description into your backlog, I’m really asking how a team works together to create the definition of features that developers should complete.
These days, most companies are expected to have some sort of digital or connected solution. Even industries that have been paper-based or seem removed from connected solutions are feeling pressure. Their executives may think they need a solution, but what should it be? And how do you determine if software is the right solution?
One sure test of any product manager’s resiliency is how she manages unplanned service outages and other types of incidents. I’m referring to events that can risk a company’s reputation, increase costs, and erode client confidence.