Software Requirements & Organizational Culture:
10 Lessons Learned
Posted by
EdmontonPM
Oct 13
Live Webinar October 19th, 2017 1:00 pm – 2:00 pm EDT
Activity Type: Education – Course or Training 1 Hour 1 PDU free
Provider: Modern Analyst
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.
Learn:
- 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
We hope that you will register today and we look forward to having you join us for this event!
Presenter: Karl E. Wiegers (LinkedIn profile) Principal Consultant Process Impact has provided training and consulting services worldwide on many aspects of software development, management and process improvement.
Karl is the author of many books including:
- Practical Project Initiation: A Handbook with Tools (Best Practices)
- Creating a Software Engineering Culture,
- Peer Reviews in Software: A Practical Guide
- Software Requirements
- More About Software Requirements: Thorny Issues and Practical Advice
Click to register for:
Software Requirements & Organizational Culture: 10 Lessons Learned
1.0 | 0 | 0 |
Technical Project Management | Leadership | Strategic & Business Management |
NOTE: For PMI® Audit Purposes – Print Out This Post! Take notes on this page during the presentation and also indicate the Date & Time you attended. Note any information from the presentation you found useful to your professional development and place it in your audit folder.
Leave a Reply