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

1. Business Story MethodTechnical Overview and StatusSeptember 2011 Gerrard Consulting Limited PO Box 347 Maidenhead Berkshire SL6 2GU Tel: +44 (0) 1628 639173 Fax: +44 (0) 1628 630398 Web: gerrardconsulting.com Intelligent Testing, Improvement and Assurance Slide 1

2. Agenda The Business Story Method™ The Story Platform Business Story Manager Maelscrum A Walkthrough of the Functionality Intelligent Testing, Improvement and Assurance Slide 2

3. Business Story Method™

5. Approved Business Stories

6. Approved Acceptance Criteria

7. Approved Stories and Scenarios

8. Procedures map to business processes

9. Assured process and feature coverage

10. Test data requirements

11. Test scripts from procedures

12. Test schedule

13. Test team management

14. Incident Management

15. ReportingScope of Maelscrum Maelscrum Scope of Business Story Manager Scope of Business Story Method Scope of Most Test Mgt Tools Intelligent Testing, Improvement and Assurance Slide 4

16. Analysis Business Story Method and Projects Evolving requirements, incremental story development, requirements testing, fortnightly updates etc. Requirements Build Stories Test Reqs. Design, Build System Functional System Test System Integration Non-Functional Testing Test Design Key: Acceptance Test Prep. Client Execution BSM Scope Acceptance Test Execution Intelligent Testing, Improvement and Assurance Slide 5

17. Story Header Feature: ship orders As a orders clerk I want to acknowledge and ship the order So thatwe fulfil a book order Scenario: ship a single book from stock Given I select a valid order And the ordered book is in stock When I choose ‘acknowledge and ship’ Then order status is changed to ‘shipped’ And an address label is printed Structured stories (other variations exist) Key word Story text Each Story has multiple Scenarios Scenarios can be data driven Intelligent Testing, Improvement and Assurance Slide 6

19. Note that roles can sometimes vary, but it is often better to reference ‘personas’ that have multiple roles.

20. Personas could be “18 year old male gamer” or “65 year old female retired nursery school teacher” for example.Intelligent Testing, Improvement and Assurance Slide 7

22. given=precondition(s), when=steps, then=outcome/post condition(s)

23. A scenario maps directly to a test case – but we haven’t used the word test yet.

24. If I do – stop me.Intelligent Testing, Improvement and Assurance Slide 8

25. Stories may have many scenarios Feature: Ship an Order In order to fulfil a book order As a orders clerk I want to acknowledge and ship the order Scenario: ship a single book from stock Given I select a valid order And the ordered book is in stock When I choose ‘acknowledge and ship’ Then order status is changed to ‘shipped’ And an address label is printed Scenario: advise a book is out of stock Given I select a valid order And the ordered book is out of stock When I choose ‘message the purchaser’ Then Enter message to purchaser advising the order status And an email is sent to the purchasers email address Scenario: advise an item is discontinued Given I select a valid order And the ordered book is discontinued Etc. etc. Intelligent Testing, Improvement and Assurance Slide 9

26. Scenario outlines allow scenarios to be data-driven Intelligent Testing, Improvement and Assurance Slide 10

27. Planning Analysis Execution Dictionary Business Story Method - Traceability Glossary Data Item Register Index Stories /Features Requirements (Business) Scenarios (Test) Scenarios Process Paths Execution Management Processes Test Procedures Test Schedule Intelligent Testing, Improvement and Assurance Slide 11

28. Dictionary Business Story Method - Agile Glossary Data Item Register Index Stories /Features Requirements Automated Or Manual (Business) Scenarios (Test) Scenarios Task Workflows developed in parallel Intelligent Testing, Improvement and Assurance Slide 12

29. The Story Platform

30. Business Story Manager Intelligent Testing, Improvement and Assurance Slide 14

31. Maelscrum Intelligent Testing, Improvement and Assurance Slide 15

32. A Walkthrough of the Main Functionality

33. https://maelscrum.com user999@demo.com password ‘password’ Change your email address… Slide 17 Intelligent Testing, Improvement and Assurance

34. User Interface Tabs and ribbons Dashboard and gadgets Announcements, Cases, Scratchpad Fast Access Settings License, default project, sprint, preferences Help Printing Intelligent Testing, Improvement and Assurance Slide 18

35. Cases and Notifications Cases Adding a case Finding cases Case/64 Status Attachments Notifications Same for requirements, stories, processes etc. When you test, we’d like you to log a case to record the incident Assign these cases to me (Paul Gerrard) Intelligent Testing, Improvement and Assurance Slide 19

36. Dictionary The Dictionary Proposed ‘Business Terms’ Glossary of terms Data Item Register The Index The index is like ‘Google for…’ Requirements Stories Scenarios We will see the dictionary in action… Intelligent Testing, Improvement and Assurance Slide 20

37. Requirements Find Requirements requirement/999 Mostly green references to words in the Glossary url Ownership Document library Stories – how many? Dictionary scans after every update Index for requirement/999 Create a business term, look at a definition Intelligent Testing, Improvement and Assurance Slide 21

38. Stories View requirement/999 View stories Add a story story/999 Extract scenarios for story/999 Business terms, Glossary entries, Data items and index Track down a data item and edit Terms to define Intelligent Testing, Improvement and Assurance Slide 22

39. (Business) Scenarios A story can have none, one or many scenarios Scenarios can be simple Scenarios can have embedded data items and a table of example data Data items denoted by <…> <this is a data item> Example data created in parallel to match Stories can be locked, you can access the test scenarios for a story Test scenarios are copes that you can edit separately from business scenarios. Slide 23 Intelligent Testing, Improvement and Assurance

40. Process Path/Procedure Intelligent Testing, Improvement and Assurance Slide 24

41. Processes, Process Paths Processes consist of a header and process elements You can also add references that are images Process paths consist of a path header and process path steps Manual or system steps A process element is referenced (the activity) A story feature and scenario may be referenced Intelligent Testing, Improvement and Assurance Slide 25

42. Exploration

43. Choosing what to test We’d like you to pair up As a pair discuss: What would you like to test? Pick 3 areas, not necessarily an area of functionality Don’t pick cases (yet) – we’ll be using them for real As a group, we’ll agree areas for each group to test in session 1 (so we get some variety) Session protocol… Slide 27 Intelligent Testing, Improvement and Assurance

44. Ideas for testing Obvious functional areas: requirements, stories, dictionary, process, paths, procedures etc. etc. Boundaries, extreme values, repeated tests, E2E flows: requirements thru procedures Navigation, usability, consistency Settings and preferences do what they say? Can you break it? Do browsers behave differently? Does help help? Slide 28 Intelligent Testing, Improvement and Assurance

45. Session Protocol (45 minutes) As a pair, chat for a few minutes, explore the product, decide on your goal for the next 40 minutes Jot down your goals for this session Make a start, as a pair, or as individuals - it’s up to you If you see an anomaly, ask us for help Real problem? Log a case in the system. Slide 29 Intelligent Testing, Improvement and Assurance

46. Session 1 feedback What is your overall impression? Did you find some bugs Program crashes Functional failures Usability problems? Other???? What areas do you think need more testing? Let’s make a list of areas to be tested in session 2 and choose who does what. Slide 30 Intelligent Testing, Improvement and Assurance

47. Session 2 feedback What is your overall impression? Did you find some bugs Program crashes Functional failures Usability problems? Other???? Which team logged the most problems? What areas do you think need more testing? How usable is the tool? Could you work with it on a real project? Slide 31 Intelligent Testing, Improvement and Assurance

48. Business Story MethodTechnical Overview and StatusSeptember 2011 Gerrard Consulting Limited PO Box 347 Maidenhead Berkshire SL6 2GU Tel: +44 (0) 1628 639173 Fax: +44 (0) 1628 630398 Web: gerrardconsulting.com Intelligent Testing, Improvement and Assurance Slide 32