Software Requirements and Organizational Culture: 10 Lessons Learned Webinar Oct. 10 2017

This presentation describes 10 lessons learned from leading requirements improvement initiatives, including the following:
• A commitment to effective requirements engineering is a hallmark of a healthy software engineering culture.
• Clearly defined business requirements are the foundation of a successful project.
• Taking a usage-centric approach instead of a feature-centric approach during elicitation better meets user needs.
• Customer engagement is a vital contributor to building high-quality software.
• The business analyst plays a central role in understanding and communicating a project’s requirements.
• No single view of the requirements shows you everything you need to know.
• A guiding principle of requirements development is “iterative refinement of detail.”
• Addressing nonfunctional requirements contributes significantly to user satisfaction.

We hope that you will register today and we look forward to having you join us for this event!

** Eligible for PDUs, CDUs. **

Karl E. Wiegers, Principal Consultant
Process Impact

Competency Based Training is Critical to Productivty

API quota exceeded. You can make 500 requests per day.

How Email Can Increase Internal Office Productivity – Yes, We Said Increase Productivity!

Strategies For Maximizing Your Productivity

Effective Brainstorming

Does Flexible Working Hours Really Work?

You May Also Like