经济分析师培训-PPT精品.pptVIP

For Business Analysts Craig Brown Business Analyst Training My agenda To explain the role of the business analyst, To discuss the methodology described in the BABOK To discuss practical tips and techniques for doing the job well To review sample requirements specifications to get an appreciation of what goes into them To provide a list of further resources analysts can call upon for help Your agenda The Business Analyst Context Role Skills Context Projects and SDLC Why projects go wrong Project team roles 8.15-9.45 What BA’s do Requirements Management Business Processes Human change management Project Portfolio Planning 10.00-11.00 Projects and the SDLC Projects and the SDLC Projects and the SDLC Projects and the SDLC Projects and the SDLC Business Analysisand the BABOK Projects and the SDLC Project Failures There are many reasons why projects fail. The cost of bad requirements The following are a few key findings and data from the study: Companies with poor business analysis capability will have three times as many project failures as successes. 68% of companies are more likely to have a marginal project or outright failure than a success due to the way they approach business analysis. In fact, 50% of this group’s projects were “runaways” which had any 2 of: Taking over 180% of target time to deliver. Consuming in excess of 160% of estimated budget. Delivering under 70% of the target required functionality. Companies pay a premium of as much as 60% on time and budget when they use poor requirements practices on their projects. Over 41% of the IT development budget for software, staff and external professional services will be consumed by poor requirements at the average company using average analysts versus the optimal organization. The vast majority of projects surveyed did not utilize sufficient business analysis skill to consistently bring projects in on time and budget. The level of competency required is higher than that employed within