Article Sponsored By

by Vinod Rajan

In this week’s article Vinod Rajan examines what the Business Analyst must be prepared to do in order to communicate change requests to their development team effectively. The Business Analyst needs to “Convey & Convince” each and every aspect of a change request to the entire team. In order to do that she/he must clearly understand and address: the questions that will be asked, how the BA can prepare themselves to face these questions, and the best ways to address the development team questions.

Article Sponsored By

by Chris Rupp

The systems development industry is frequently shaken by negative reports, such as the mishaps and delays that plagued the Toll Collect system in Germany or cars that break down due to software defects. Many people wonder what it is that ails modern systems development. Why is it so hard to build systems that realize user requirements when our technology allows us to do almost anything? Are systems engineers losers when it comes to communicating about the requirements? Can the problem be solved by an agile process and direct communication between system users and developers? If so, which fields of knowledge must be added to an agile process in order to ensure that knowledge transfer works?

Article Sponsored By

by John Simpson and Eric Winquist

In the world of product development and specifically in requirements management, you hear a lot about building a "central repository" or a "single system of record". But, why does that matter? What’s the real value in creating a central hub of product intelligence?

It all comes down to productivity. Without a solution that keeps everyone and everything connected, your organization is vulnerable to the common issues that plague product development teams.