Related Content
 |
How to Write Good Software Requirements Even in 2013 software professionals are still having difficulties getting good software requirements. Joe Townsend lists several handy resources on how to finally start writing quality software requirements. |
|
 |
The Importance of Consistent Business Rules Often organizations have multiple information systems with different systems performing different functions. Adrian Reed highlights the importance and benefits of applying common business rules where there are multiple systems. |
|
 |
Become a Better Product Manager: Your Project Deserves It Becoming a better product manager is something you never stop doing. As you get better, your work will improve, your satisfaction with your work will increase, and opportunities to do even better work will come. Scott Sehlhorst sums up how to invest in becoming a better product manager. |
|
 |
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. |
