Related Content
Why You Should Focus On What Automation Does Not Do Often, what automation “does” directly relates to the bottom line. This has loosely been interpreted as the misconception that the more automation you have, the fewer people you will need on your payroll. Melissa Tondi focuses on what automation does not do to give a more accurate idea. |
||
Maintaining Testable Requirements and Acceptance Criteria Once a testable requirement or acceptance criteria have been “created,” there is a tendency to assume that the task can be considered completed. Because that may or may not be true, it is better to continue to pay attention to testability. Here are four ways to maintain testable requirements. |
||
When Big Data Is a Big Waste One of the biggest fallacies surrounding big data is that it will always lead to valuable information. Big data can be not only a big waste of time, but also a big detriment to your organization. Read on to see if you are making these big data mistakes. |
||
Building Discoverability into Our Daily Information Consumption If we look at keywords essential to information processing, searchability and discoverability are critical. Any piece of information an organization has access to needs to become searchable and discoverable to the relevant end-users when they need it. This is presenting new business opportunities. |
||
Cassandra’s Curse: You Can’t Make Clients Take Action According to Greek myth, Cassandra's curse was that she could predict the future but no one would believe her prophecies. Sometimes the same can be said for project proposals. You can give the best assessment possible, but that doesn't mean the client will heed your words. Read on for encouragement. |
||
Successful Performance Testing Begins at Requirements Discovering performance issues in early builds allows more time to correct the design. By including critical performance-related features and elements earlier, we can take advantage of the incremental nature of the development process to avoid creating engineering in potential performance issues. |
||
Tools—Some Assembly Required A tool architecture is simply a picture of all your development, testing, and deployment tools and how they fit together. Creating a "current state" diagram and then looking forward and creating a "future state" diagram helps you understand where tool integrations would be beneficial. |
||
The Resurgence of Enterprise Software Enterprise software has long existed and grown with changes in technology. During a shift in focus to mobile computing, mobile app development, and enterprises working to embrace the cloud, it would not be unfair to say that enterprise software was briefly sidelined―but it's making a resurgence. |