Maelscrum / Business Story Manager Overview

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

Agenda
The Business Story Method™
The Story Platform
Business Story Manager
Maelscrum
A Walkthrough of the Functionality
Slide 2

Business Story Method™

Execution
Planning
Analysis
Process Flow Introduction
Test the Requirements
Refine
Requirements
Collate Requirements
Processes, Stories, Scenarios
Procedures from Scenarios
Test Detailing
Execution Management
Dictionary of business terms and data items
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
Scope of Maelscrum
Maelscrum
Scope of Business Story Manager
Scope of Business Story Method
Scope of Most Test Mgt Tools
Slide 4

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
Slide 5

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
Slide 6

Anatomy of a business story header
The story brings together these aspects so we can view the feature from different viewpoint to explore it
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.
Slide 7

Anatomy of a scenario
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.
Slide 8

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
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
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
And the ordered book is discontinued
Etc. etc.
Slide 9

Scenario outlines allow scenarios to be data-driven
Slide 10

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
Slide 11

Dictionary
Business Story Method - Agile
Glossary
Data Item Register
Index
Stories /Features
Requirements
Automated
Or
Manual
(Test) Scenarios
Task Workflows developed in parallel
Slide 12

The Story Platform

Business Story Manager
Slide 14

Maelscrum
Slide 15

A Walkthrough of the Main Functionality

https://maelscrum.com
user999@demo.com
password ‘password’
Change your email address…
Slide 17

User Interface
Tabs and ribbons
Dashboard and gadgets
Announcements, Cases, Scratchpad
Fast Access
Settings
License, default project, sprint, preferences
Help
Printing
Slide 18

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)
Slide 19

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…
Slide 20

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
Slide 21

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
Slide 22

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

Process Path/Procedure
Slide 24

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
Slide 25

Exploration

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

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

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

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

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

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
Slide 32

http://uktmf.com	47
http://testela.com	30
http://dev.maelscrum.com	17
https://maelscrum.com	17
https://dev.maelscrum.com	16
https://businessstorymanager.com	15
https://dev.businessstorymanager.com	12
http://www.uktmf.com	11
http://www.testela.com	7
http://dev.businessstorymanager.com	3
https://testela.com	2
http://maelscrum.com	2
http://test.testela.com	2
https://www.maelscrum.com	1
http://webcache.googleusercontent.com	1
http://www.linkedin.com	1

Maelscrum / Business Story Manager Overview

by Paul Gerrard

Accessibility

Categories

Upload Details

Usage Rights

16 Embeds 184

Statistics