Related Content
 |
Why Documentation Is Important in Agile, Too Should agile teams relax the requirement that user documentation be updated during each sprint? After all, the Agile Manifesto prefers working software over comprehensive documentation, so shouldn’t we be able to relax that requirement? Scott Sehlhorst explains why his response is "absolutely not." |
|
 |
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. |
|
 |
How to Ask for a Raise We’re trained from childhood not to discuss money. Still, if you don't ask for a raise, you could be cheating yourself out of a bigger paycheck. So, if you’re doing your job and believe you deserve more, the smart thing is to ask. |
|
 |
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. |
|
 |
Seven Mistakes Managers Make Naomi Karten did a web search of “mistakes managers make” and received 262,200 hits. Although many of the unique articles highlight the same or similar mistakes, Naomi found that certain mistakes kept surfacing. Here are the seven most common managerial mistakes. |
|
 |
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. |
