Ten Tips to Get Requirements Right and Make Stakeholders Happy
Have you ever delivered an application with functionality that was not what the stakeholders really wanted-or needed? Have you ever discovered that you were listening to the wrong people? Has your team ever developed a really beautiful application that no one uses? A truly successful project delivers what is most important to the business, the sponsor, and the key stakeholders. Carol Askew shares ten requirement-related tips she uses at her large healthcare organization. For example, to keep her projects on track, Carol developed specific requirements checkpoints to review throughout the software development lifecycle. She describes what to look for in project initiation documents, requirements elicitation sessions, user stories, scope issues, and project schedules. Take back ideas that you can use right away to help achieve success in your own projects. Although you probably won’t save the world, you will end up with very happy customers!
Recommended Web Seminars
|The Testing Practices Fueling High-Performing Software Teams
|Building Confidence in Your Automation
|Leveraging Open Source Tools for DevSecOps
|Five Reasons Why Agile Isn't Working
|Building a Stellar Team