Related Content
 |
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. |
|
 |
The Importance of Diverse, Inclusive Software Conferences By making a software conference inclusive, you avoid perpetuating the stereotypes that only certain people are good at technology. You're also helping to grow the pool of people who see a career in the computer industry as a possibility. Rick Scott looks at why diversity is beneficial for everyone. |
|
 |
First Things First: Get the Business Analysis Basics in Place While we can debate about best and better practices for eliciting, analyzing, and documenting requirements, many organizations have yet to adopt a requirements practice at all. When they do so, they will have the opportunity to realize significant benefits. |
