Related Content
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. |
||
It's Time to Wake Up the Tester in You While test teams still primarily own product quality, quality is evolving to be an overall team responsibility. Every discipline—design, development, business, marketing, and operations—has its own role to play in shipping a user-ready, competitive, and quality product. |
||
Cast a Wider Net to Get the Best Software Requirements Stakeholders often have different views about a software project—the scope, what requirements to include and their priority, and possible solutions. To get the best requirements, you need to talk with and understand the worries, fears, challenges, and ideas of as many stakeholders as possbile. |
||
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. |
||
Internal Social Media and the Business Analyst Adrian Reed looks at the use of internal/corporate social media and networks by business analysts for overall process improvement. Key benefits include locating stakeholders, engaging stakeholders, understanding process faults, and finding incremental ways to improve processes. |
||
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? |
||
Need Another Reason to Consider DevOps? Automation is a critical component of eliminating waste. A large part of the DevOps movement is centered on automating the infrastructure tasks that take away from delivering value. In addition to the obvious cost savings of automation, it can also breed innovation. |