Live Webinar November 9th, 2012 12:00 pm – 1:00 pm EST
Duration: 1 hour webinar Credits: 1 PDU Category A – $15 USD PDU
Presented by: Solutions Cube Group (REP 2451)

In many companies, the Requirements Definition process fails to define the “real” business need for a project and solutions are often defined before knowing what they need to satisfy.

On some projects, solutions may have already been defined and the team is just looking for “the right” project to implement them on.

Only Project Solutions with clear ties to documented business requirements are in scope for a project.

Project failure increases when teams spend resources on developing and implementing solutions that are out of scope for a project or address the project needs in unexpected or undesired ways.

Solutions Cube Group’s Defining Technical Requirements webinar will enable participants to learn techniques for creating traceable project solutions to meet the true business needs of the project..

Atendees will learn how to define the architectural framework for the project solution first and then use this knowledge to draw out detail technical statements.

Participants will also learn how to ensure the solutions they intend to build are clear and understood by both business and technical stakeholders and are not just “great ideas” that may be out of scope for the project.

In this 1 hour in-depth webinar participants learn:

• Techniques for defining Technical Approaches at the beginning of the solutions activity
• Assessment techniques to select the appropriate Technical Approach for the project
• How to create traceability between technical requirement statements and business requirements
• How to use a Systems list to ensure important technical requirements are documented for the project
• How to ensure the business project stakeholders are aligned on the solution being proposed prior to starting lower level detail design work
• Specific techniques that can be immediately applied in their work environment

EARN 1 PDU after viewing this webinar

Click to purchase Defining Technical Requirements: Requirements Series 3 of 3