Business Analyst Community & Resources | Modern Analyst

Webinars - Business/Systems Analysis

Webinar: Software Requirements and Organizational Culture: 10 Lessons Learned

Statistics:

(11574 Views) (0 Comments)

ABOUT THE WEBINAR

When a software development organization wants to improve the way it works, it’s not enough to write a bunch of procedures, buy some tools, and run your staff through some training. The manager leading a change initiative also must consider the organization’s culture. A software engineering culture is a set of beliefs, behaviors, and technical practices that define an environment in which all team members are committed to building quality software products through effective and appropriate software processes. As requirements form the foundation of all the software work that follows, it’s especially important to instill a set of effective values, principles, and practices around requirements practices.

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. **

FEATURED SPEAKER:
Karl E. Wiegers, Principal Consultant
Process Impact

Karl E. Wiegers has provided training and consulting services worldwide on many aspects of software development, management and process improvement. Prior to starting Process Impact in 1997, Karl spent 18 years at Eastman Kodak Company in a variety of roles. Karl is the author of many books including: Software Requirements & More About Software Requirements.

FEATURED SPONSOR: IREB - International Requirements Engineering Board

Download slides -> Slides Software Requirements and Organizational Culture: 10 Lessons Learned

Download video -> Software Requirements and Organizational Culture: 10 Lessons Learned