stakeholders
 |
A Good User Experience Starts with Excellent Requirements Adrian Reed highlights the importance of creating solid requirements in order to create a good user experience. Techniques discussed include engaging users early in the requirements cycle; stakeholder identification, categorization, and management; and process identification and modeling. |
|
 |
Why Cultural Differences Matter to Project Stakeholders In a time when many projects span organizations, countries, and time zones, an appreciation of culture—including national culture—is of paramount importance. Adrian Reed explains how cultural guides, comparisons, and observations can be extremely useful for your projects. |
|
 |
There's No Such Thing as an IT Project Adrian Reed makes the case that there is no such thing as an IT project—there are only business projects that implement, impact, change, or interface with IT. This sounds like a subtle distinction, but it’s deceptively important. |
|
 |
Do Too Many Business Analyst Cooks Spoil the Soup? Adrian Reed looks at common challenges related to stakeholder engagement and answers the question: How can a business analyst best operate when it doesn’t seem possible to get direct access to stakeholders and when there are multiple BAs from different organizations or different teams in the mix? |
|
 |
Why the Product Owner's Role Is Evolving Due to the popularity of Scrum, the idea of having a product owner has taken hold of development professionals and is used by teams that are not even using Scrum. With this industry-wide adoption, the definition of product ownership and the product owner's role has evolved. |
|
 |
How to Help Project Stakeholders Avoid the Aspirin When we first speak to project stakeholders, they talk about all of the problematic symptoms—as this is the day-to-day pain that they feel. Developing requirements and solutions around these symptoms might be the equivalent of taking aspirin because the root cause will still be there. |
|
 |
What Jobs Do Your Stakeholders Want Done? The jobs-to-be-done (JTBD) theory is intended to help stakeholders think about their products and services by considering how their customers like to use them. Kent McDonald delves into the JTBD theory and its benefits to a product delivery team. |
|
 |
Story Roadmaps—Product Vision That Paints a Picture A product roadmap tells the story of what you’re going to do with your product. It is a manifestation of the vision of what you’re trying to do and why. Scott Sehlhorst explains how best to communicate the product roadmap with your team and the product's stakeholders. |
