Testing world seen through the thick lens of a business analyst
-
Upload
testcampro -
Category
Technology
-
view
710 -
download
0
description
Transcript of Testing world seen through the thick lens of a business analyst
Iasi, November 16th 2013
Testing world seen through the thick lensof a business analyst
Test Camp
Anca Gafiteanu
Gabi Rotaru
4
Agenda
Unicredit Business Integrated Solutions
Testing department in my eyes
IT factory
Road Map
Project challenges
Functional specifications
Presentation meetings
Contact the business analyst
Summary
5
AUSTRIA
ROMANIA
POLAND
HUNGARY
UK
SLOVAKIA
GERMANYCZECH REPUBLIC
UniCredit Business Integrated Solutions
A community of 11 000 colleagues
11 Countries*
*UniCredit Business Integrated Solutions operates also in 2 additional branches, New York and Singapore
respectively.
ITALY
IASI300 peopleIASI300 people
OUR TEAM
40 people
sustaining front-end solutions for the
eBanking platform for 7 UniCredit banks;
managing the integration of applications;
redesigning the corporate and retail
components of the eBanking platform.
6
Testing department in my eyes
peaceful and quiet working place
taking one task after another
time and material activity
why is this guy bothering me with questions while I’m working on my task?
having difficulties passing through people on the way to the bathroom
taking the time to plan a barbecue in weekend
party in clubs on weekdays is always a good idea
7
IT factory
How do you feel at work?
Groundbreaking haute couture designer
Flash news: IT industry is all about designing!
Third employee on the second row
OR
8
IT factory (cont.)
if you feel like in a factory, you’d better look around;
exciting new things are flying all around your working place;
if you’re not feeling yourself as a part of it, maybe you should update your CV.
9
Road map
Building the product road map
The business analyst often finds himself in the damage control area.
Almighty business department Customizations and nice-to-have items
10
Road map (cont.)
apply latest market trends;
use current projects to drive to a better product;
harmonize road map with the current features.
11
Project challenges
I bet you know this joke!
Have you ever wondered why is it happening so often?
12
Project challenges (cont.)
communication
personal touch
devil is in the details
customer product knowledge
handle all case scenarios
13
Functional specifications
How do you look at the functional specifications document?
There is no such thing as perfect functional specification document!
Believe and don’t doubt! Good foundation, let’s build on top of it!
OR
14
Functional specifications (cont.)
translate customer requirements to product terminology;
make sure the related current status is deeply analyzed and understood;
expose the proposed changes into easy-to-understand phrases.
15
Presentation meetings
Why do we need presentation meetings?
Put your mark on the product!
Brainstorming on the proposed solution It’s easier to pass the information
OR
16
Presentation meetings (cont.)
the business analyst is mainly a meeting mediator;
the idea is to gather (almost) immediate feedback from all the participants;
you are there to offer suggestions and remarks;
“we already thought about it, but…” answer is not a failure;
large number of action items makes the business analyst happy
insist on receiving a proper explanation for turning down your suggestion;
you should broadcast to others where needed.
17
Contact the business analyst
Not my favorite email layout
18
Contact the business analyst
Checklist:
ID and description of your current task;
if first contact, state your name / department / area;
state high importance and/or urgency;
always quote the functional specifications document;
high level presentation of the problem;
case scenario steps;
avoid sending log files and/or audit logs;
avoid idle times.
19
Summary
Approach the business analyst if:
you do not understand the business model / customer requirements;
some related current status functionalities are not present in the document;
the proposed change does not fit the customer requirements;
it will be very difficult for the operator to use the new features;
it will be very difficult for the customer’s end-users to understand the new features.
20
Thank you!