Business Story Method - Overview

1,246 views

Published on

This talk sets out the thinking behind the Gerrard Consulting Business Story Method. The slides present background, an overview of the method and introduces the Testela Business tool that supports Gerrard Consulting services.

Published in: Technology, Business
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
1,246
On SlideShare
0
From Embeds
0
Number of Embeds
165
Actions
Shares
0
Downloads
21
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • The index box sits alone here, looks odd!
  • Business Story Method - Overview

    1. 1. OverviewBusiness Story Method<br />Gerrard Consulting Limited<br />PO Box 347<br />Maidenhead<br />Berkshire<br />SL6 2GU<br />Tel: +44 (0) 1628 639173<br />Fax: +44 (0) 1628 630398<br />Web: gerrardconsulting.com<br />Assurance<br />Improvement<br />Outsourcing<br />Slide 1<br />Intelligent Testing, Improvement and Assurance<br />© 2010 Gerrard Consulting<br />
    2. 2. Key challenges<br />Increasing Delivery Success<br />Reducing the Cost of Re-Work<br />Increasing Confidence in Timelines<br />Intelligent Testing, Improvement and Assurance<br />© 2010 Gerrard Consulting<br />Slide 2<br />
    3. 3. The delivery process <br />Business Domain<br />Training<br />Business Goals<br />Acceptance<br />Acceptance Tests<br />Requirements<br />IT Domain<br />Test<br />Specify<br />A mystery to the Business - <br />waterfall, agile or somewhere <br />in between?<br />Build<br />Design<br />Development Process<br />Communications <br />hot spots<br />Intelligent Testing, Improvement and Assurance<br />© 2010 Gerrard Consulting<br />Slide 3<br />
    4. 4. Business Domain<br />The delivery process <br />Training<br />Business Goals<br />Acceptance<br />Acceptance Tests<br />Requirements<br />Extended Timeline? - Some re-work inevitable as change is constant<br />IT Domain<br />Test<br />Specify<br />Build<br />Design<br />Development Process<br />Intelligent Testing, Improvement and Assurance<br />© 2010 Gerrard Consulting<br />Slide 4<br />
    5. 5. Story Management challenge in Agile <br />Requirements are captured as stories, implemented into development “sprints” <br />Test Driven development (TDD) essentially documents the requirements as unit tests<br />But, many “agile” teams don’t use TDD and throw stories away, so where is the traceability and documentation?<br />Many teams don’t have sufficient user involvement to drive the stories through to representative development<br />Typically, there is no record of how decisions were made<br />Slide 5<br />Intelligent Testing, Improvement and Assurance<br />© 2010 Gerrard Consulting<br />Existing tools don’t help with these management challenges<br />
    6. 6. Range of development approaches<br />Most projects fit somewhere in between<br />Waterfall<br />Agile<br />Where Stories Are Meaningful<br /><ul><li>Stories have universal value as examples of features in use; regardless of the development approach
    7. 7. Stories won’t work where they are regarded as ‘throwaway’ in Agile projects (or anywhere)</li></ul>Intelligent Testing, Improvement and Assurance<br />© 2010 Gerrard Consulting<br />Slide 6<br />
    8. 8. Bridging the Communications Gap <br />We take your requirements; expand into Stories (identify features); and illustrate by Scenarios (real life examples)<br />We bring these to life via workshop prototyping sessions which ensures the requirements are complete and that the scenarios are fully representative and are signed off<br />The Scenarios become test scripts to determine that the requirements have been met<br />The test scripts will last the life of the system, not just one project<br />Delivered via our structured Business Story Method supported by our hosted service Business Story Manager<br />Intelligent Testing, Improvement and Assurance<br />© 2010 Gerrard Consulting<br />Slide 7<br />
    9. 9. Story Management for Agile <br />Same structured English language for Stories and Scenarios<br />Manages which Stories/Scenarios are included within each Sprint<br />Supported by our hosted service Maelscrum<br />Intelligent Testing, Improvement and Assurance<br />© 2010 Gerrard Consulting<br />Slide 8<br />
    10. 10. Business Story Method - Overview<br />Execution<br />Planning<br />Analysis<br />Test the Requirements<br />Refine<br />Requirements<br />Collate Requirements<br />Processes, Stories, Scenarios<br />Procedures from Scenarios<br />Test Detailing<br />Execution Management<br /><ul><li>Dictionary of business terms and data items
    11. 11. Approved Business Stories
    12. 12. Approved Acceptance Criteria
    13. 13. Approved Stories and Scenarios
    14. 14. Procedures map to business processes
    15. 15. Assured process and feature coverage
    16. 16. Test data requirements
    17. 17. Test scripts from procedures
    18. 18. Test schedule
    19. 19. Test team management
    20. 20. Incident Management
    21. 21. Reporting</li></ul>Scope of Maelscrum<br />Scope of Business Story Manager<br />Services to deliver content<br />Scope of Most Test Mgt Tools<br />Intelligent Testing, Improvement and Assurance<br />© 2010 Gerrard Consulting<br />Slide 9<br />
    22. 22. Business Story Manager Reduces Ambiguity<br />Traceability<br />The Dictionary <br />Use of English language<br />Prototyping workshops for review and sign-off<br />Project implementation<br />Intelligent Testing, Improvement and Assurance<br />© 2010 Gerrard Consulting<br />Slide 10<br />
    23. 23. Business Story Method - Traceability<br />Planning<br />Analysis<br />Execution<br />Dictionary<br />Glossary<br />Data Item Register<br />Index<br />Stories /Features<br />Requirements<br />(Business) Scenarios<br />(Test) Scenarios<br />Process Paths<br />Execution Management<br />Processes<br />Test Procedures<br />Test Schedule<br />Intelligent Testing, Improvement and Assurance<br />© 2010 Gerrard Consulting<br />Slide 11<br />
    24. 24. The ‘Dictionary’<br /><ul><li>Requirements and stories are scanned and terms indexed
    25. 25. Undefined (candidate) terms in stories can be identified and are loaded in the index
    26. 26. Business users provide definitions and approve new terms
    27. 27. Scenarios that have data items (parameters) defined are scanned, indexed and entered into the data item register
    28. 28. Data item properties (type, size, validation rules) can be edited</li></ul>Dictionary<br />Glossary<br />of Business Terms<br />Data Item Register<br />The INDEX<br />(references to all usage in requirements and Stories)<br />Requirements<br />Stories<br />Intelligent Testing, Improvement and Assurance<br />© 2010 Gerrard Consulting<br />Slide 12<br />
    29. 29. Structured language of stories helps bridge communications gaps<br />Feature:<br />As a orders clerk<br />I want to acknowledge and ship the order<br />So thatwe fulfil a book order<br />Scenario: ship a single book from stock<br />Given I select a valid order<br /> And the ordered book is in stock<br />When I choose ‘acknowledge and ship’<br />Then order status is changed to ‘shipped’<br /> And an address label is printed<br />Key word<br />Story text<br />Each Story has multiple Scenarios<br />Scenarios can be data driven<br />Intelligent Testing, Improvement and Assurance<br />© 2010 Gerrard Consulting<br />Slide 13<br />
    30. 30. Business Story Method - Governance<br />Planning<br />Analysis<br />Execution<br />Dictionary<br />Prototyping workshops<br />Glossary<br />Data Item Register<br />Index<br />Auto Generated<br />Review and Sign-Off<br />Stories /Features<br />Requirements<br />(Business) Scenarios<br />(Test) Scenarios<br />Process Paths<br />Execution Management<br />Processes<br />Test Procedures<br />Test Schedule<br />Intelligent Testing, Improvement and Assurance<br />© 2010 Gerrard Consulting<br />Slide 14<br />
    31. 31. Analysis<br />Business Story Method and Projects<br />Evolving requirements, incremental story development, requirements testing, fortnightly updates etc.<br />Requirements<br />Build Stories<br />Test Reqs.<br />Design, Build System<br />Functional System Test<br />System Integration<br />Non-Functional Testing<br />Test Design<br />Key:<br />Acceptance Test Prep.<br />Client<br />Execution<br />BSM Scope<br />Acceptance Test Execution<br />Intelligent Testing, Improvement and Assurance<br />© 2010 Gerrard Consulting<br />Slide 15<br />
    32. 32. Scope of our new services<br />Business Story Method<br />Confidence in testing coverage without bureaucratic paper mountains<br />Reduced re-work in development and test effort by eliminating inconsistencies and omissions in requirements<br />Automated support for functional and acceptance testing<br />Ultimately, improved quality and trustworthiness of requirements<br />Business Story Manager (hosted service)<br />Our purpose built tool that supports our methodology<br />Provides a repository for requirements, stories, scenarios business processes, glossary and test scripts<br />Is easy to use and supports the system life not just one project <br />Maelscrum (hosted service)<br />Provides story management support for Agile projects <br />Slide 16<br />Intelligent Testing, Improvement and Assurance<br />© 2010 Gerrard Consulting<br />
    33. 33. Benefits <br />Increased Delivery Success<br />Business language ensures consistency throughout development and testing<br />Reducing the Cost of Re-Work<br />Increased confidence in validity and coverage of your requirements<br />Scenarios provide unambiguous examples for development<br />Increasing Confidence in Timelines<br />Scenarios aid production of training materials and support requirements and improve business acceptance<br />Slide 17<br />Intelligent Testing, Improvement and Assurance<br />© 2010 Gerrard Consulting<br />
    34. 34. Thank-you.<br />Slide 18<br />

    ×