Related Content
 |
User Participation Is Essential to Diagnosis and Problem Solving The role of IT professionals is to help users get the most value from their systems. If IT systems aren’t working efficiently or correctly, it isn’t just an “IT Problem” and the nice folks in IT can’t solve it effectively without user participation. |
|
 |
API Security, PII, and Healthcare In this article, we examine the importance of API security in the healthcare sector, sharing best practices to ensure personally identifiable information (PII) of users and patients is protected. |
|
 |
Why You Should Automate Compliance Compliance policy is one of those things most employees find boring and useless. However, for employers, staying compliant is one of the most crucial tasks and can have serious legal and financial repercussions if not done properly. But how can you make following compliance policy easier for your employees? |
|
 |
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. |
|
 |
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. |
|
 |
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. |
