Related Content
 |
UAT Entrance Criteria: Don’t Negotiate Against Yourself An important component of any User Acceptance Testing (UAT) plan are the entry criteria. No complex data system will ever be perfect, but starting with lax entrance criteria puts the UAT team in a weak position. |
|
 |
7 Things to Know In 2021 about the New Privacy Laws Changing the Web In the past few years, we’ve experienced rapid changes in the online privacy landscape. Here are 7 key things everyone should know today regarding privacy on the Web.
|
|
 |
How COVID-19 Accelerated Digital Maturity Explore how COVID-19 has revolutionized the IT industry through opportunities similar to those experienced during the Internet, mobile, social, and cloud revolutions.
|
|
 |
Requirements Discipline: Avoiding “Death by a Thousand Paper Cuts" Absent an effective requirements baseline it is difficult to distinguish clarifications and error correction from enhancements and changes to the original ask. |
|
 |
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. |
|
 |
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. |
|
 |
The Curse of Rushed Requirements When development is outsourced, a documented baseline of expected functionality sets expectations for both the client and developer. Acknowledging that agile practices are flexible, beware the trap of rushing requirements just because you know they are going to change. It's still essential to be as accurate as you can. |
