|
Ever wonder why more than 25.4 percent of proprietary software fails? The answer is that defects and cost-overruns are a result of poorly defined requirements. If you calculated this percent of the project's cost, how much could have been avoided if your staff were trained on what information needs to be captured and how to engage the business community in developing better requirements. This program concentrates on the real front-end of any project
talking with business personnel to get the information needed to define the results you want. Save time and money on your project but most important is to get the output your business needs in the time frame you need it.
| Topics include: |
• Your attitude & energy
• How to validate what you learned and what is being built
• Know what Information you need & when |
• Listen to learn something new
• Make and keep your business contacts alive
• New skills for your toolkit |
| Benefits of attendance: |
• Find gaps in knowledge to develop better questions
• Explore and understand how to use the soft skills of working with the business community
• Learn new ways to engage the business and keep them engaged throughout the development cycle |
• Identify new skills to add to your toolbox
• Review ways to reduce the percentage of failures associated to requirements
• Understand the different types of requirements |
| Staff from the following areas should attend: |
• Business Analysts
• Business Process Architects
• Data Analysts
• Enterprise Architects
• Project Managers |
• Process Improvement Specialists
• Requirement Engineers
• Software Development Managers
• Systems Engineers
• Technical Writers |
|
