CORE+ Competency Workshops -- Level 2
| 2-05: |
How to Model and Analyze Business System Data |
2 days |
|
With or without computers, you can't do a good jobs if you don't know what you need to know. Data describes everything in a company from the initial customer order to the final invoice and beyond. Getting correct data when you need it lets you meet or exceed your customers' expectations. Inaccurate, late and missing data causes expensive rework and delays. As a business analyst, you have to understand the role of data. |
|
| 2-20: |
How to Jump-Start Requirements Gathering with User Stories |
1 day |
|
It is very early in your project; maybe as early as concept. How will you know what the system is supposed to do? There are many people with many different expectations and needs, and you may have not even decided how you will develop the system. How can you deal with these difficulties, gather reasonable, early "requirements," and not waste the effort? This workshop teaches a technique referred to as User Stories (not to be confused with use case) that offers a tried and tested solution. It focuses on the business need or goals for the system and avoids the trap of trying to capture the system and technical specifications too early. |
|
| 2-30: |
How to Develop Business Use Cases |
2 days |
|
The critical success factor for any solution is whether or not the end users will be able to use it to do what they need to do. The concept of using use cases to define end-user interaction with a proposed information documentation and use case diagrams as tools for business systems analysts. |
|
| 2-40: |
How to Manage Small Projects |
2 days |
|
The techniques presented in this course will allow you to define and manage projects from 4 days to 4 months in duration. It offers a complete set of techniques for defining business requirements on a small scale. All of the techniques are scalable to larger, more sophisticated projects. It forms the perfect basis for those who do not have project management experience but have to get the job done quickly. |
|
| 2-50: |
How to Estimate Early in a Project |
1 day |
|
Early project estimating: every client wants it, most information system professionals can't do it, and everyone is suspect of it. Our experience tells us that whatever value we come up with probably be a poor estimate, leading to a missed due date and unhappy customers. Yet, we must march boldly forward and estimate. This course introduces methods that yield reasonable early estimates and improve the communication of the factors that affect them. |
|