|
|
Core Competency Workshops -- Level 1
| 1-10: |
How to Gather, Analyze, and Define Business System Requirements |
3 days |
|
This set of modules concentrates on delivering the core competencies that every business systems analyst should possess. These are skills in defining problems, analyzing processes, defining requirements, identifying possible solutions and communicating to all levels of the business withiin the project structure. This course teaches your how to interview subject matter experts, recognize business problems, extrapolate business needs, and document the business requirements for a business solution. |
|
| 1-11: |
How to Capture and Tame Business Requirements |
1 day |
|
This training workshop offers techniques for determining how to gather, capture, or elicit business requirements from subject matter experts. Whether you are preparing for a 1-on-1 interview or creating an email survey to get requirements, you will find a useful, proven set of techniques and tricks for identifying problems and gathering requirements, organizing the answers and checking the completeness of the results. |
|
| 1-12: |
How to Write Effective Business Requirements for IT Projects |
1.5 days |
|
Writing effective business requirements is the critical skill for subject matter experts who represent the business interests on an IT project. The challenge lies in defining what the business needs in requirements that the IT professionals can understand and use to design the solution. |
|
| 1-13: |
How to Prepare and Facilitate Requirements Gathering Workshops |
1.5 days |
|
Gathering business requirements from subject matter experts is the single most important activity in any project. This course presents a set of techniques that are designed to help the business systems analyst ask the right questions at the beginning of the project and effectively structure the requirements gathering meetings with the subject matter experts. |
|
| 1-20: |
How to Model, Analyze and Improve Business Processes |
2.5 days |
|
Process models help both business and technical people understand how things work. A work flow diagram makes problem areas visible and shows the impact of proposed changes. The diagram can be modified and tested without affecting the real world. Used effectively, it will reduce the probability of omitting critical aspects of your solution. To be effective, all involved parties have to understand what the model represents and what it ignores. |
|
| 1-40: |
How to Manage Changing Business Requirements |
0.5-1 day |
|
This course presents state-of-the-practice techniques essential to the management of changing requirements from project initiation through system deployment. The program includes a demonstration of an automated tool that supports requirements management best practices. |
|
|
|
|