Related Content
 |
2 Ways to Know Your Work Is Actually Done Some people think a good indication that a piece of work is done is if it's been tested. But by whom, and how? Testing alone doesn’t specifically determine whether you are done—especially when we probably don’t mean the same thing when we all talk about testing. Here are two ways to know when your work is truly done. |
|
 |
Continuous Automation, from Source Code to Production Automation is necessary to achieve the benefits of DevOps principles, so teams may use automation at every step of software development. Depending on how frequently and confidently a team deploys code, they can use automation to enable continuous integration, continuous delivery, and, finally, continuous deployment. |
|
 |
Trusting Your Data: Garbage In, Garbage Out Poor quality input will always produce faulty output. Improper validation of data input can affect more than just security; it can also affect your ability to make effective business decisions. Bad data can have impacts on how you make quantitative decisions or create reports, if you can’t trust the data you receive. |
|
 |
Migrating a Database? Consider These Factors First Database migration is usually performed with a migration tool or service. Migrating one database to another actually involves migrating the schemas, tables, and data; the software itself is not migrated. Whatever the reason for migration, before you start, explore the options and take these considerations into account. |
|
 |
Building Good Scrum Habits Building good habits is an important part of an effective Scrum team. Habits are a form of automation: The more basic processes we can automate, the more we can focus our energy on hard things. The Scrum process, with its focus on rituals, helps us by providing a framework for collaboration and making it second nature. |
|
 |
Tips for Getting an Agile Transformation Off the Ground Many agile transformations are doomed before they even begin. Organizations focus on the wrong things up front, resulting in a poorly planned effort that doesn’t deliver business value. Here are some tips to get things started the right way, including how to communicate well, define roles, and change your culture. |
|
 |
2 Ways to Standardize QA Practices Testing can get complicated when each project is using a completely different toolset, language, and reporting status, with different measurements and formats. Testing is a reaction to context and what we encounter, so how we test cannot be standardized. What we can standardize is the stuff that surrounds the testing. |
|
 |
Getting Support for the Tests You Need Done It’s often hard for teams to get sufficient time and resources for the amount and quality of tests they think are needed. It’s like management wants testing done but at the same time doesn’t want to commit what’s needed to do it. If that's your case, look at the business side, rank priorities, and negotiate resources. |
