0
Business Story MethodTechnical Overview and StatusSeptember 2011<br />Gerrard Consulting Limited<br />PO Box 347<br />Maid...
Agenda<br />The Business Story Method™<br />The Story Platform<br />Business Story Manager<br />Maelscrum<br />A Walkthrou...
Business Story Method™<br />
Execution<br />Planning<br />Analysis<br />Process Flow Introduction<br />Test the Requirements<br />Refine<br />Requireme...
Approved Business Stories
Approved Acceptance Criteria
Approved Stories and Scenarios
Procedures map to business processes
Assured process and feature coverage
Test data requirements
Test scripts from procedures
Test schedule
Test team management
Incident Management
Reporting</li></ul>Scope of Maelscrum<br />Maelscrum<br />Scope of Business Story Manager<br />Scope of Business Story Met...
Analysis<br />Business Story Method and Projects<br />Evolving requirements, incremental story development, requirements t...
Story Header<br />Feature:	ship orders<br />As a 	orders clerk<br />I want 	to acknowledge and ship the order<br />  So th...
Anatomy of a business story header<br /><ul><li>The story brings together these aspects so we can view the feature from di...
Note that roles can sometimes vary, but it is often better to reference ‘personas’ that have multiple roles.
Personas could be “18 year old male gamer” or “65 year old female retired nursery school teacher” for example.</li></ul>In...
Anatomy of a scenario<br /><ul><li>The parallel with test cases is obvious:
given=precondition(s), when=steps, then=outcome/post condition(s)
A scenario maps directly to a test case – but we haven’t used the word test yet.
If I do – stop me.</li></ul>Intelligent Testing, Improvement and Assurance<br />Slide 8<br />
Stories may have many scenarios<br />Feature: Ship an Order<br />In order to fulfil a book order<br />As a orders clerk<br...
Scenario outlines allow scenarios to be data-driven<br />Intelligent Testing, Improvement and Assurance<br />Slide 10<br />
Planning<br />Analysis<br />Execution<br />Dictionary<br />Business Story Method - Traceability<br />Glossary<br />Data It...
Dictionary<br />Business Story Method - Agile<br />Glossary<br />Data Item Register<br />Index<br />Stories /Features<br /...
The Story Platform<br />
Business Story Manager<br />Intelligent Testing, Improvement and Assurance<br />Slide 14<br />
Maelscrum<br />Intelligent Testing, Improvement and Assurance<br />Slide 15<br />
A Walkthrough of the Main Functionality<br />
Upcoming SlideShare
Loading in...5
×

Maelscrum / Business Story Manager Overview

1,411

Published on

Overview of the Gerrard Consulting Story Platform including Maelscrum and Business Story Manager.

Published in: Technology, Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,411
On Slideshare
0
From Embeds
0
Number of Embeds
4
Actions
Shares
0
Downloads
13
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide
  • The index box sits alone here, looks odd!
  • The index box sits alone here, looks odd!
  • Transcript of "Maelscrum / Business Story Manager Overview"

    1. 1. Business Story MethodTechnical Overview and StatusSeptember 2011<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 />Intelligent Testing, Improvement and Assurance<br />Slide 1<br />
    2. 2. Agenda<br />The Business Story Method™<br />The Story Platform<br />Business Story Manager<br />Maelscrum<br />A Walkthrough of the Functionality<br />Intelligent Testing, Improvement and Assurance<br />Slide 2<br />
    3. 3. Business Story Method™<br />
    4. 4. Execution<br />Planning<br />Analysis<br />Process Flow Introduction<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
    5. 5. Approved Business Stories
    6. 6. Approved Acceptance Criteria
    7. 7. Approved Stories and Scenarios
    8. 8. Procedures map to business processes
    9. 9. Assured process and feature coverage
    10. 10. Test data requirements
    11. 11. Test scripts from procedures
    12. 12. Test schedule
    13. 13. Test team management
    14. 14. Incident Management
    15. 15. Reporting</li></ul>Scope of Maelscrum<br />Maelscrum<br />Scope of Business Story Manager<br />Scope of Business Story Method<br />Scope of Most Test Mgt Tools<br />Intelligent Testing, Improvement and Assurance<br />Slide 4<br />
    16. 16. 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 />Slide 5<br />
    17. 17. Story Header<br />Feature: ship orders<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 />Structured stories (other variations exist)<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 />Slide 6<br />
    18. 18. Anatomy of a business story header<br /><ul><li>The story brings together these aspects so we can view the feature from different viewpoint to explore it
    19. 19. Note that roles can sometimes vary, but it is often better to reference ‘personas’ that have multiple roles.
    20. 20. Personas could be “18 year old male gamer” or “65 year old female retired nursery school teacher” for example.</li></ul>Intelligent Testing, Improvement and Assurance<br />Slide 7<br />
    21. 21. Anatomy of a scenario<br /><ul><li>The parallel with test cases is obvious:
    22. 22. given=precondition(s), when=steps, then=outcome/post condition(s)
    23. 23. A scenario maps directly to a test case – but we haven’t used the word test yet.
    24. 24. If I do – stop me.</li></ul>Intelligent Testing, Improvement and Assurance<br />Slide 8<br />
    25. 25. Stories may have many scenarios<br />Feature: Ship an Order<br />In order to fulfil a book order<br />As a orders clerk<br />I want to acknowledge and ship the 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 />Scenario: advise a book is out of stock<br />Given I select a valid order<br />And the ordered book is out of stock<br />When I choose ‘message the purchaser’<br />Then Enter message to purchaser advising the order status<br />And an email is sent to the purchasers email address<br />Scenario: advise an item is discontinued<br />Given I select a valid order<br />And the ordered book is discontinued<br />Etc. etc.<br />Intelligent Testing, Improvement and Assurance<br />Slide 9<br />
    26. 26. Scenario outlines allow scenarios to be data-driven<br />Intelligent Testing, Improvement and Assurance<br />Slide 10<br />
    27. 27. Planning<br />Analysis<br />Execution<br />Dictionary<br />Business Story Method - Traceability<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 />Slide 11<br />
    28. 28. Dictionary<br />Business Story Method - Agile<br />Glossary<br />Data Item Register<br />Index<br />Stories /Features<br />Requirements<br />Automated<br />Or<br />Manual<br />(Business) Scenarios<br />(Test) Scenarios<br />Task Workflows developed in parallel<br />Intelligent Testing, Improvement and Assurance<br />Slide 12<br />
    29. 29. The Story Platform<br />
    30. 30. Business Story Manager<br />Intelligent Testing, Improvement and Assurance<br />Slide 14<br />
    31. 31. Maelscrum<br />Intelligent Testing, Improvement and Assurance<br />Slide 15<br />
    32. 32. A Walkthrough of the Main Functionality<br />
    33. 33. https://maelscrum.com<br />user999@demo.com<br />password ‘password’<br />Change your email address…<br />Slide 17<br />Intelligent Testing, Improvement and Assurance<br />
    34. 34. User Interface<br />Tabs and ribbons<br />Dashboard and gadgets<br />Announcements, Cases, Scratchpad<br />Fast Access<br />Settings<br />License, default project, sprint, preferences<br />Help<br />Printing<br />Intelligent Testing, Improvement and Assurance<br />Slide 18<br />
    35. 35. Cases and Notifications<br />Cases<br />Adding a case<br />Finding cases<br />Case/64<br />Status<br />Attachments<br />Notifications<br />Same for requirements, stories, processes etc.<br />When you test, we’d like you to log a case to record the incident<br />Assign these cases to me (Paul Gerrard)<br />Intelligent Testing, Improvement and Assurance<br />Slide 19<br />
    36. 36. Dictionary<br />The Dictionary<br />Proposed ‘Business Terms’<br />Glossary of terms<br />Data Item Register<br />The Index<br />The index is like ‘Google for…’<br />Requirements<br />Stories<br />Scenarios<br />We will see the dictionary in action…<br />Intelligent Testing, Improvement and Assurance<br />Slide 20<br />
    37. 37. Requirements<br />Find Requirements<br />requirement/999<br />Mostly green references to words in the Glossary<br />url<br />Ownership<br />Document library<br />Stories – how many?<br />Dictionary scans after every update<br />Index for requirement/999<br />Create a business term, look at a definition<br />Intelligent Testing, Improvement and Assurance<br />Slide 21<br />
    38. 38. Stories<br />View requirement/999<br />View stories<br />Add a story<br />story/999<br />Extract scenarios for story/999<br />Business terms, Glossary entries, Data items and index<br />Track down a data item and edit<br />Terms to define<br />Intelligent Testing, Improvement and Assurance<br />Slide 22<br />
    39. 39. (Business) Scenarios<br />A story can have none, one or many scenarios<br />Scenarios can be simple<br />Scenarios can have embedded data items and a table of example data<br />Data items denoted by <…> <this is a data item><br />Example data created in parallel to match<br />Stories can be locked, you can access the test scenarios for a story<br />Test scenarios are copes that you can edit separately from business scenarios.<br />Slide 23<br />Intelligent Testing, Improvement and Assurance<br />
    40. 40. Process Path/Procedure<br />Intelligent Testing, Improvement and Assurance<br />Slide 24<br />
    41. 41. Processes, Process Paths<br />Processes consist of a header and process elements<br />You can also add references that are images<br />Process paths consist of a path header and process path steps<br />Manual or system steps<br />A process element is referenced (the activity)<br />A story feature and scenario may be referenced<br />Intelligent Testing, Improvement and Assurance<br />Slide 25<br />
    42. 42. Exploration<br />
    43. 43. Choosing what to test<br />We’d like you to pair up<br />As a pair discuss:<br />What would you like to test?<br />Pick 3 areas, not necessarily an area of functionality<br />Don’t pick cases (yet) – we’ll be using them for real<br />As a group, we’ll agree areas for each group to test in session 1 (so we get some variety)<br />Session protocol…<br />Slide 27<br />Intelligent Testing, Improvement and Assurance<br />
    44. 44. Ideas for testing<br />Obvious functional areas: requirements, stories, dictionary, process, paths, procedures etc. etc.<br />Boundaries, extreme values, repeated tests, <br />E2E flows: requirements thru procedures<br />Navigation, usability, consistency<br />Settings and preferences do what they say?<br />Can you break it?<br />Do browsers behave differently?<br />Does help help?<br />Slide 28<br />Intelligent Testing, Improvement and Assurance<br />
    45. 45. Session Protocol (45 minutes)<br />As a pair, chat for a few minutes, explore the product, decide on your goal for the next 40 minutes<br />Jot down your goals for this session<br />Make a start, as a pair, or as individuals - it’s up to you<br />If you see an anomaly, ask us for help<br />Real problem? Log a case in the system.<br />Slide 29<br />Intelligent Testing, Improvement and Assurance<br />
    46. 46. Session 1 feedback<br />What is your overall impression?<br />Did you find some bugs<br />Program crashes<br />Functional failures<br />Usability problems?<br />Other????<br />What areas do you think need more testing?<br />Let’s make a list of areas to be tested in session 2 and choose who does what.<br />Slide 30<br />Intelligent Testing, Improvement and Assurance<br />
    47. 47. Session 2 feedback<br />What is your overall impression?<br />Did you find some bugs<br />Program crashes<br />Functional failures<br />Usability problems?<br />Other????<br />Which team logged the most problems?<br />What areas do you think need more testing?<br />How usable is the tool?<br />Could you work with it on a real project?<br />Slide 31<br />Intelligent Testing, Improvement and Assurance<br />
    48. 48. Business Story MethodTechnical Overview and StatusSeptember 2011<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 />Intelligent Testing, Improvement and Assurance<br />Slide 32<br />
    1. A particular slide catching your eye?

      Clipping is a handy way to collect important slides you want to go back to later.

    ×