Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • TALK THROUGH Bas have to challenge and test everything. Nothing must be ambiguous, so….. WHAT DO WE MEAN BY SUFFICIENT?
  • This is based on a study by Staffordshire University – figures are based on amount of actual effort rather than what is actually needed to get it right. Our experience is that requirements take about twice as long as the design and about the same amount of time/effort as Coding (not testing). What it should be: 30% reqs 15% design 40% code 15% test
  • You can see from the shape of this graph that most errors originate during analysis.
  • Now look at the shape of this graph. It’s going in the other direction. The relative cost of correcting reqs is 1 in 100 in comparison to correcting after go live. The numbers don’t matter too much – the fact the costs of correction rise exponentially does.
  • Half of errors are requirement errors costing ¾ o project rework costs – leading to… Late projects costing nearly double their budget – no wonder 30% just get canned. Contributing to…. Back to original slide figures
  • case_for_business_analysis_V04.ppt

    1. 1. Making the case for doing Business Analysis
    2. 2. This presentation will… … introduce you to the ‘what’, ‘when’ and ‘why’ of Business Analysis … outline the value of Business Analysis
    3. 3. POST-IMPLEMENTATION Business Analysts feed back to the Owner how well their measure of success has been achieved Owners defines measures of success and £ targets … Business Analysts confirm & document Strategists determine the strategy to hit the targets … Business Analysts help do market research, create strategy, challenge & document Sponsors establish a Programme that delivers the strategy … Business Analysts document Programme TOR and build the Business Case Programme Managers Institute Projects that implement the programme … Business Analysts document the Project TOR Project Stakeholders … Business Analysts specify requirements for Projects (in the Business Model) Design Analysts design solution that satisfies the requirements … Business Analysts protect requirements & document compromises <ul><li>Project managers </li></ul><ul><li>Implement solution </li></ul><ul><li>… Business Analysts help with </li></ul><ul><li>Process and data migration </li></ul><ul><li>Cutover planning </li></ul><ul><li>Rollout </li></ul>Solution Builders & Business test solution … Business Analysts ensure tested against requirements Solution Builders build solution … Business Analysts protect requirements & document compromises <ul><li>Users </li></ul><ul><li>Accept solution </li></ul><ul><li>… Business Analysts help with </li></ul><ul><li>£MEASURING £BENEFITS £REALISATION </li></ul>When & Where are Business Analysts involved and What do they do? There is a chain of reasoning that leads from the statement of a problem to the implementation of solutions… … involving up to 10 groups of people… £Money!
    4. 4. Business Analysis Proverbs <ul><li>Delivery is not the best time to analyse requirements </li></ul><ul><li>Urban Wisdom </li></ul><ul><li>A factor present in every successful project and absent in every unsuccessful project is sufficient attention to requirements. </li></ul><ul><ul><ul><ul><ul><li>Suzanne & James Robertson </li></ul></ul></ul></ul></ul><ul><ul><ul><ul><ul><li>Requirements-Led Project Management </li></ul></ul></ul></ul></ul>
    5. 5. Requirements Analysis Design Code/test 0 10 20 30 40 50 60 70 Average actual effort spent on each stage of the development cycle* *based on a study by Staffordshire University What is “sufficient attention to requirements”? (I)
    6. 6. Requirements Analysis Design Code/test 0 10 20 30 40 50 60 70 80 90 Average Proportion of Errors Built in During Development* *based on a study by James Martin What is “sufficient attention to requirements”? (II)
    7. 7. Relative Cost of Correcting Requirements Errors* *sourced from Barry Boehm What is “sufficient attention to requirements”? (III)
    8. 8. How Much Poor Analysis can £ Cost* <ul><li>Half of all bugs can be traced to requirement errors </li></ul><ul><li>fixing these errors consumes 75% of project rework costs </li></ul><ul><li>Maybe that’s why: </li></ul><ul><li>The average project exceeds its planned schedule by 120% </li></ul><ul><li>52.7% of projects will cost 189% of their original estimate </li></ul><ul><li>Only 16.2% of projects will be completed on time & on budget </li></ul><ul><li>30% of projects are cancelled before completion </li></ul>*Source: Calculating your return on investment from more effective requirements management IBM article Dec 2003
    9. 9. The Standish Group “Chaos Report” (1995) The landmark study of project failure covering 365 executive managers and 8,380 applications in all major industry segments including: banking, retail and wholesale. Analysis will help mitigate over 60% of factors that cause project failure How Analysis Helps Some of the contents of this slide were taken from
    10. 10. -end-