Requirements
 |
How to Make Products People Love Scott Sehlhorst explores how to make products people love and focuses on Marty Cagan's ten tips presentation at MindTheProduct 2012, London's first conference for product teams. Key points include product discovery, not building what customers want, and building what customers need. |
|
 |
Look at Everyday Products to Improve Software Designers are always looking at ways to improve software by making it fun and engaging to visitors. However, to reach the next level, we need to slightly change our focus. We need to look not just at other pieces of software but also at everyday products—like doors and the signs that go on them. |
|
 |
Three Ways to Talk When You Are Listening We know listening is important. Typically, it’s what our stakeholders have to share that we most need to hear when eliciting and validating scope or requirements. At the same time, as business analysts, we cannot be passive flies on the wall. |
|
 |
Taking Time Off to Benefit Innovation What a great idea it would be to be able to spend 10 percent of your time—or 15 or even 20 percent—away from your projects developing new ideas and focusing on projects of personal interest. It turns out that the idea is hardly new. Naomi Karten writes how taking time off can benefit innovation. |
|
 |
Tips for Keeping Pace with New Technology Keeping pace with new technologies is challenging—especially if you've fallen behind. However, continuous learning is a critical component of agile practices. A few simple steps will not only help you get back to the forefront of technology but also will revitalize your thirst for knowledge. |
|
 |
Cultivating a Great Workplace The prevailing way of justifying workplace benefits is to paint them as a vital tool to attract and retain staff in a competitive marketplace. If we look at things more holistically though, we can view these benefits as one component of building a company where people actually like to work. |
|
 |
Avoiding the Security Black Hole with Non-Functional Requirements Security vulnerabilities highlight the importance of the non-functional side of systems. Creating confident security starts by spending sufficient time eliciting and analyzing non-functional requirements. Adrian Reed explains how to avoid the security black hole with non-functional requirements. |
|
 |
Why Experimentation Should Be Required for Initiating Projects Sameh Zeid writes that experimentation should be required for initiating projects—no matter the organization’s size—for the simple reason that product features will more than likely be discovered incrementally and iteratively during the project's lifespan. |
