In order to provide clarity about agile techniques and practices, here are 7 things product people need to know about agile.
I decided to do a little bit of research to find out what this technical product manager role is all about and if it is a bit better description of the type of work I find myself drawn toward. Included in this post are some of the resources I came across to get a better understanding.
Wait… what? That seems like an odd question to ask on a site for product people, after all some of the people reading this are product owners and the fact you are reading this is a pretty good indication that you are probably engaged. Stick with me for a second…. Product Ownership in Internal Products …
Some criteria to keep in mind when deciding how to communicate with stakeholders, as well as helpful techniques you can use at different levels of detail.
I often suggest that you focus on outcomes over output, but never explained why. Here's a look at the benefits and pitfalls of a focus on outcomes.
A review of 4 different product owner assessments you can use to determine areas where you can focus your learning efforts and find just-in-time resources.
An epic post exploring what the terms theme, epic, feature, and user stories mean when it comes to product backlogs and how I tend to use those terms.
Business analysis skills help effective product owners focus on outcomes, build shared understanding, and make sure decisions get made.
When you develop products, you have to interact with customers, users, and stakeholders. To be effective, you need to understand the different perspectives.
You can get a lot of value out of having big items on your backlog (ie features) because you can get a broad view of the overall output you might need to deliver without having to dive into detail on any one particular item too soon.
At some point, though you do need to dive into detail on something in order to start delivery. Feature refinement provides a way to do that in a way that allows you consider options and focus on the essential aspects of the feature and discard the aspects that aren’t completely necessary.
Some techniques you can use to describe user stories help you build shared understanding of your product and the outcomes you seek.