Related Content
3 Critical Considerations for Technical Due Diligence Technical due diligence is the process of verifying a company’s technical capabilities, quality, and processes. It is typically performed by investors or buyers before a contract. There are many aspects you can investigate, but three are crucial: a code review, security evaluation, and open source components compliance. |
||
What’s the Problem with User Stories? Agile projects focus on very lightweight, simple requirements embodied in user stories. However, there are some problems with relying solely on user stories. They often don't contain enough accuracy for development, testing, or industry regulations. There's a better way to write detailed requirements that are still agile. |
||
How to Make a Fixed-Scope Contract More Agile Establishing a contract that genuinely supports agile methods can be a significant challenge. By its very nature, a contract that specifies detailed, upfront deliverables contravenes the principles of flexibility and adaptation that are at the heart of agile. But it is possible—both parties just need to focus on results. |
||
Lessons the Software Community Must Take from the Pandemic Due to COVID-19, organizations of all types have had to implement continuity plans within an unreasonably short amount of time. These live experiments in agility have shaken up our industry, but it's also taught us a lot of invaluable lessons about digital transformation, cybersecurity, performance engineering, and more. |
||
Why UX Is More Important Than Coding When it comes to your project succeeding, the quality of the code is secondary to user experience. That's because software is all about making users' jobs easier. If you start coding in a vacuum without understanding what your users need to do, you can't be sure you’re making the right thing. You need UX research. |
||
Aging Gracefully in QA Employee churn is inevitable in every industry, and positions are being filled by fresh young faces all the time. Instead of becoming worried or insecure, senior team members should embrace their new status as someone to be looked up to for experience, lessons, and mentoring abilities. Here's how to do that in QA. |
||
Making (and Keeping) Project Risk Visible Project managers recommend how much should be invested to address various risks based on their understanding of project context, but the final decision about what to do and when those efforts are sufficient belongs to the sponsor. Risk management requires executive input, so sponsors need to see all risk data you have. |
||
To Be a Better Tester, Ask the Right Questions Critical thinking is a core trait a software tester needs to succeed, and asking questions is a great skill to help. Questioning brings out the required information, breaks assumptions, and enables everyone on the team to give their perspectives. But there's an art to asking the right question at the right time. |